Re: Estimating a Project

[Beth Agnew <Beth -dot- Agnew -at- senecac -dot- on -dot- ca>]

And as Chief Dan George said in _Little Big Man_: "Sometimes the magic 
works, and sometimes it doesn't."

Unfortunately, there is no formula that works in all cases, every time. 
Documentation projects are filled with so many variables, that even the 
best estimate is only an educated, qualified guess. And as every project 
manager knows, stuff happens. However, there are a number of things you 
can do to make your estimates more accurate:
1. Look at the history of similar projects -- how much did they cost, 
and to what extent is your project the same/different?
2. Consider the skill levels of the team members -- how quickly can they 
be productive?
3. As best you can, identify the work breakdown structure or all of the 
tasks involved in the project, and estimate how long each will take. 
Don't forget things such as learning the product, layout, reviews and 
revisions.
4. Include a contingency factor -- make sure there is some leeway in 
case of unforeseen circumstances.
5. When any of the parameters of the project change, re-evaluate your 
estimate. Don't expect the estimate to be accurate if you have more work 
or fewer resources than you anticpated.
6. Maintain a project log so that you know what factors have affected 
the progress of work on your documentation. This will help you make a 
better estimate next time.
7. Follow good project management practices. Documentation is just like 
any other project -- diligence in monitoring progress and evaluating 
results will help you achieve a successful outcome.

Bill Swallow wrote: