2 Responses to “Agile Estimation & Planning”
User Story Estimation Techniques
Estimating is really hard. But some following points are coming to my mind.
1: Why do we estimate?
2: How are estimate created
3: How should estimate be started?
4: When do we estimate?
5: Who Estimates?
How can we get the best estimates of story size? Now let’s break down the agile estimation.
Wideband Delphi is group of based estimation approach. Wideband Delphi did not estimate the whole project in one meeting; the group breaks down the project into manageable pieces. Then group based team creates a problem specification, identifies the assumptions. Before they begin creating estimates, participants read the problem specification. Wideband Delphi technique asks a panel of experts to submit estimates as anonymously, so no knows which estimates belong to whom. Then group based teams reviews the results to make sure everyone agrees on the final task list estimate.
Planning Poker is an agile estimating and planning technique that is agreement based. Most teams will hold a Planning Poker session shortly after an initial product backlog is written. This Planning Poker session is used to create initial estimates useful for sizing the project. To start a planning poker session, the product owner reads an agile user story or describes a feature. Planning poker uses playing cards with numbers on them. The numbers are often based on the Fibonacci sequence used as story points. The Planning Poker team discusses the feature, asking questions of the product owner as needed. When the feature has been fully discussed, each team member privately selects one card. All cards are then open at the same time. If all team selected the same value, that becomes the estimate. If not, the team discusses their estimates. After further discussion, each team reselects an estimate card, and all cards are again open at the same time.
If there is a group of four people, and three of them select the card number 5 and one person select the card number 3,the task is recorded as a “5”.
Affinity Estimating is the process of grouping requirements. This technique is often used to group of similar user stories. Affinity Estimating is a form of relative positions of points. it provides a comparative view of the estimates and gives the team an opportunity to do a reality check. By placing the user stories into size categories, it is easier to see whether user stories that are assigned similar estimates are in fact comparable in size.