Top 10 Agile Estimation Practices on a Page
I am a real fan of one-pagers; there is special value in getting everything visible and presented on one page (okay, one page, two sides), that brings unique scope comprehension and clarity. Toyota and other lean organizations make use of “A3 Reports,” a one-page summary of an issue, its root causes, counter-measures and verification steps to summarize problems and planned solutions--they are powerful tools.
Incidentally, when I first started work I had a wise and cantankerous project manager who was full of oxymoronic proverbs. One I remember was: “If you cannot summarize it on only one page, you need to go off and learn more about it!” An astute paradox! Here is the summary.
Top 10 Agile Estimation Practices
1. Use more than one person. By engaging the team in the estimation process, we gain the benefits of additional insights and consensus building. Additional people bring different perspectives to estimating and spot things individuals may miss. Also, the involvement in the process generates better support and commitment for the estimates being produced.
2. Use more than one approach. Just as one person is likely to miss perspectives of estimating, so too are single approaches. Use multiple estimation approaches (comparison to similar projects, bottom up, user story points, etc.) and look for convergence between
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"Karate is a form of martial arts in which people who have had years and years of training can, using only their hands and feet, make some of the worst movies in the history of the world." - Dave Barry |




