Difference between revisions of "Relative estimation"
(Zeroth version.) |
(Velocity is the great equalizer.) |
||
| Line 7: | Line 7: | ||
|wish=Consistent estimation of effort makes planning a breeze. | |wish=Consistent estimation of effort makes planning a breeze. | ||
|background=The idea of relative estimating being better than absolute is not merely a premise. It has been shown by Lederer and Prasad in “A Causal Model for Software Cost Estimating Error” (1998) and Vicinanza et al. in “Software Effort Estimation: An Exploratory Study of Expert Performance” (1991). | |background=The idea of relative estimating being better than absolute is not merely a premise. It has been shown by Lederer and Prasad in “A Causal Model for Software Cost Estimating Error” (1998) and Vicinanza et al. in “Software Effort Estimation: An Exploratory Study of Expert Performance” (1991). | ||
Velocity is “the great equalizer”, according to {{author|Mike Cohn}}, because it is what lets a team be able to successfully plan a project as long as their estimates are consistent (even if there is systematic error in those estimates). Being consistent is much easier to achieve and this allows teams to create plans. | |||
|therefore=Always estimate relative. Establish a common base for estimation across teams to allow for planning on a larger scale. | |therefore=Always estimate relative. Establish a common base for estimation across teams to allow for planning on a larger scale. | ||
}} | }} | ||
Revision as of 13:18, 8 September 2012
…one or more development teams working on collaborative product discovery.
✣ ✣ ✣
{{{wish full}}}
The idea of relative estimating being better than absolute is not merely a premise. It has been shown by Lederer and Prasad in “A Causal Model for Software Cost Estimating Error” (1998) and Vicinanza et al. in “Software Effort Estimation: An Exploratory Study of Expert Performance” (1991).
Velocity is “the great equalizer”, according to Mike Cohn, because it is what lets a team be able to successfully plan a project as long as their estimates are consistent (even if there is systematic error in those estimates). Being consistent is much easier to achieve and this allows teams to create plans.
Therefore:
{{{therefore full}}}
✣ ✣ ✣
✣ ✣ ✣
Sources