why_do_we_use_story_points_instead_of_hours
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
why_do_we_use_story_points_instead_of_hours [2019/01/21 08:47] – Edited to fix English hpsamios | why_do_we_use_story_points_instead_of_hours [2020/07/13 06:51] (current) – hans | ||
---|---|---|---|
Line 19: | Line 19: | ||
To be clear, if the estimate is really just a proxy for time (hours or days), we should stop calling them Story Points. After all, they are just “ideal days” or "ideal hours" with all the inherent problems. [[http:// | To be clear, if the estimate is really just a proxy for time (hours or days), we should stop calling them Story Points. After all, they are just “ideal days” or "ideal hours" with all the inherent problems. [[http:// | ||
- | <WRAP box>If a development team is equating some number of hours to a storypoint, it is missing the point (pun intended). Saying, “Thirty hours equals one point” is ridiculous. If you’re doing that, just use hours for goodness sake. You haven’t gained anything from storypoints except to be able to claim to be doing “agile.”</ | + | > If a development team is equating some number of hours to a storypoint, it is missing the point (pun intended). Saying, “Thirty hours equals one point” is ridiculous. If you’re doing that, just use hours for goodness sake. You haven’t gained anything from storypoints except to be able to claim to be doing “agile.” |
Here are some things to understand when using Story Points instead of a more traditional approach to estimating. | Here are some things to understand when using Story Points instead of a more traditional approach to estimating. |
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/why_do_we_use_story_points_instead_of_hours.1548089259.txt.gz · Last modified: 2020/06/02 14:23 (external edit)