Is there a point in Story point estimation?
4 views
Skip to first unread message
Krishna
Feb 4, 2011, 5:46:02 AM2/4/11
to Hallam Agile Community Sheffield
This is a relative size of the story compared to other story estimated
by the same team – it has nothing to do with who is implementing it
and how long it's going to take. Benefits are
- Team’s velocity can be measured
- Allows team to plan future sprint without over/under
committing and forecasting total number of sprints. As a result no
unrealistic expectations are placed on the team
- Helps team to focus on completing dev and testing in the
same sprint
- Helps teams reach a sustainable pace and due to this the
business starts to believe in the team
by the same team – it has nothing to do with who is implementing it
and how long it's going to take. Benefits are
- Team’s velocity can be measured
- Allows team to plan future sprint without over/under
committing and forecasting total number of sprints. As a result no
unrealistic expectations are placed on the team
- Helps team to focus on completing dev and testing in the
same sprint
- Helps teams reach a sustainable pace and due to this the
business starts to believe in the team
Krishna
Feb 7, 2011, 9:24:13 AM2/7/11
to Hallam Agile Community Sheffield
Story points is relative estimate, so that you know that 5 point story
will take approx. 5 times longer than 1 point story. Hours (or ideal
hours) are more about time estimation. It can lead to several
problems:
- your "hours" are not the same as mine. It can be harder to make team
estimate during release planning.
- it's easier to make relative estimates and then calculate team
velocity in points.
- stories are usually decomposed to tasks for the sprint. These tasks
can be implemented by different people. So total effort is not simply
calculated as sum of task estimates.
Usually it's recommended to make story estimation in points for
release backlogs and in hours for sprint backlog.
Posted by Yuri Lapitsky
will take approx. 5 times longer than 1 point story. Hours (or ideal
hours) are more about time estimation. It can lead to several
problems:
- your "hours" are not the same as mine. It can be harder to make team
estimate during release planning.
- it's easier to make relative estimates and then calculate team
velocity in points.
- stories are usually decomposed to tasks for the sprint. These tasks
can be implemented by different people. So total effort is not simply
calculated as sum of task estimates.
Usually it's recommended to make story estimation in points for
release backlogs and in hours for sprint backlog.
Posted by Yuri Lapitsky
Krishna
Feb 10, 2011, 8:54:03 AM2/10/11
to Hallam Agile Community Sheffield
1. Story points are a pure measure of size and complexity>
2. Story points are relative (say, with respect to the simplest story)
and so have a much longer shelf-life
3. Story points are usually independent of who gives the estimate (as
in, an experienced developer and an apprentice can usually agree on
something like complexity fairly quickly)
4. Story points avoid the need for discussions like “what are *ideal*
hours, really?” or “My ideal hours are different from your ideal
hours, stupid.” These add no value.
5. Story points don’t influence behavior (e.g. Parkinson’s Law)
6. Story points are easier to work with – especially when product
owners start to wonder why “3 ideal days take a week…”
7. Story points are more fun – especially when they’re in units like
gummy-bears, polar bears, or other endangered species.
Posted by Amit Rathore
> > business starts to believe in the team- Hide quoted text -
>
> - Show quoted text -
2. Story points are relative (say, with respect to the simplest story)
and so have a much longer shelf-life
3. Story points are usually independent of who gives the estimate (as
in, an experienced developer and an apprentice can usually agree on
something like complexity fairly quickly)
4. Story points avoid the need for discussions like “what are *ideal*
hours, really?” or “My ideal hours are different from your ideal
hours, stupid.” These add no value.
5. Story points don’t influence behavior (e.g. Parkinson’s Law)
6. Story points are easier to work with – especially when product
owners start to wonder why “3 ideal days take a week…”
7. Story points are more fun – especially when they’re in units like
gummy-bears, polar bears, or other endangered species.
Posted by Amit Rathore
>
> - Show quoted text -
Reply all
Reply to author
Forward
0 new messages