Easy Story Estimation
Easy Estimation in Agile
Story Point Estimation Easy Methods
In Story sizing, team
does a comparative analysis between all of the stories for the project. Let’s see
the Generic story sizing steps.
For each story to be
sized, do the following as a team (Product Owner, Scrum Team, Architect (if require
by Team) scrum master).
Identify Base stories.
It is very important to identify one or multiple base or
reference story against which you would do relative sizing of the backlog. This
story is picked from current product backlog or a different story which we have
done earlier. Team can select in size complexity like low, medium and high ,But
what is important is the understanding of this story is same among everyone on
the team. Team should be confident of this base story.
Discuss the
requirements of the story.
Product Owner/Product Manager, will answer questions and provide
explanation about what exactly this story entails.
Discuss and list
down things In Story which you require to know at time of implementing story.
These can be bullet points on the story card or text in the
“notes” section of a tool. This is best done by Scrum Master who can add these
details as and when discussions are on.
Questions team
ask themselves when they start sizing.
1. Design: What will
we have to learn before we can start work on this story?
2. Coding: How
much code will need to be written for this story? Have we written similar
code before?
3. Unit Testing: Will any special setup (e.g., mock objects)
be required to unit test this story?
4. Acceptance Testing: How much work is involved in helping the
customer to automate the acceptance tests for this story?
5. Integration Points:
Does this story have external dependencies?
6. Expertise: Does
anyone of us have done similar story before?
Some point of relative comparison.
If this story
is about the same amount of work as one you have already sized, give it the
same number of points. If it is more difficult, give it a proportionally higher
value. If this story is similar to another but less work in some way, give it a
lower value.
Reach a consensus among entire team present as to the
size of the story as per definition of done.
Validate that your estimates are internally consistent
among stories as you go along.
Periodically ensure that all of the 1’s are about the
same, all of the 2’s match, etc.
Likewise, the team
should agree that a four-point story is roughly twice as much work as a
two-point story.
Comments
Post a Comment