30 Random Things About Software Project Estimates

by Utpal Vaishnav on August 19, 2009

  1. Check the history about how similar projects were estimated.
  2. Partial WBS is also an option.
  3. Sometimes Expert Opinion is the best answer.
  4. It should be based on the Solution Architecture.
  5. It should take bottom-up approach.
  6. Divide and rule. Make it modular.
  7. (Development) Language does matter.
  8. Offshore can reduce costs but not all the times.
  9. Make sure that what-if scenarios are identified
  10. Feature and price breakdown are necessary evils.
  11. Sometimes, phased estimation saves the project.
  12. Some of the following methods are good estimation-technique-candidates:
    1. Parametric,
    2. Educated assumptions,
    3. Delphi method,
    4. Dependencies identification,
    5. Previous history
    6. Task breakdown
  13. Assumption is the chair on which estimation sits sometimes.
  14. Distrust can undermine estimates.
  15. Padded estimate generate distrust
  16. Estimating techniques can help manage the risks
  17. Guesstimations can screw the projects.
  18. Use Case Metrics is also a possibility.
  19. Ranged estimations are the answer when you do not have precise information.
  20. Three Point Estimation technique is considered a reliable one.
  21. Ultimate destination of an estimate is Budget.
  22. Not all management knows the distinction between estimation and budget.
  23. Make sure to add estimates for User Acceptance Test (UAT) – it will save the project from being a failure.
  24. Variations with the actual and Ballpark estimations can be up to 300%
  25. Variations with the actual and Rough estimations can be up to 50% to 100%
  26. Variations with the actual and Fair estimations can be up to 25% to 50%
  27. Have you considered contingency plans in the estimate you just created?
  28. Those who do the actual work should be an integral part of estimation.
  29. Estimate of all 4 variables is must: time, people, and resources and the risks
  30. A good estimate does not need fancy tools – Ms-Excel or a pen and paper would suffice if it is executed nicely.
Utpal Vaishnav is a lifelong learner, entrepreneur and author. On PMCraft , Utpal writes about his experiences and learning on Project and Program Management. Interested in Agile? He also runs a Scrum focused blog. He is passionate about personal development and he shares his personal development experiences at Self Help Zen. Visit www.utpalvaishnav.com/about to know more about him or follow him on twitter @utpalvaishnav.

{ 0 comments… add one now }

Leave a Comment

CommentLuv badge

Previous post:

Next post: