About
Exploring Solution Spaces, Keith Ray's blog on Software development and other topics.
Send comments to:
keithray@mac.com
| For Agile Training, eLearning, or Coaching contact: |
| Industrial Logic, Inc. |
| 866-540-8336 (toll free) |
| 510-540-8336 (Berkeley, California) |
| Links |
| xpminifaq |
| Résumé |
| “Adopting XP” Article 2002 (pdf) |
| “ Refactoring” Article 2006 |
| AYE Conference |
| Lucien W. Dupont |
| Elisabeth Hendrickson |
| Johanna Rothman's Managing Product Development |
| Brian Marick's Exploration Through Example |
| Esther Derby's Insights You Can Use |
| Laurent Bossavit's Incipient(thoughts) |
| Dale Emery's Conversations with Dale |
| Martin Fowler's Bliki |
| Creating Passionate Users |
Archives
Subscribe
RSS Exploring Solution Spaces XML
2007.Mar.28 Wed
How to Estimate with Story Points
Pick a very small, easy, story "User can do X".
Set its story-point value to 1.
Compare that to another story "User can do Y"... is that just as difficult as the previous story? two times harder? three times harder? or easier than the 1-point story?
If 2-times harder then it's story point value is 2.
If 3-times harder, then its story point value is 3.
If it is easier, call it 1/2 a point or use the "Y" story as the new 1-point story and evaluate the "X" story against it.
If the "Y" story is more than 3 times harder, find a way to split the story into two or more smaller stories.
Story points are a relative measure used for estimation, and they are not based on line count.