I l @ ve RuBoard |
Release planning is creating a game plan for your Web project outlining what you think you want your Web site to be. The plan is a guide for the content, design elements, and functionality of a Web site to be released to the public, to partners , or internally. It also estimates how long the project will take and how much it will cost. What the plan is not is a functional specification that defines the project in detail or that produces a budget you can take to the bank. Basically you use a Release Plan to do an initial sanity check of the project's feasibility and worthiness. Release Plans are useful road maps, but don't think of them as guides to the interstate road system. Instead, think of them as the maps used by early explorers ”half rumor and guess and half hope and expectation. It's always a good idea to have a map of where a project is headed.
Generating a Release Plan is as much an exercise in customer relations as it is the writing of a document. Web project requirements seem fairly loose to begin with, so simply spending a day with the customer usually isn't enough to get all the information you need. If you want a happy customer, you need to firm up information in at least four key areas:
There are no easy answers to writing the release plan, but here is the process we have found most effective in producing successful projects. Keep it short and cover only the important issues. XP is not about generating documents. |
I l @ ve RuBoard |