Development Management checklists (13)-agile development-estimation story

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future.

The first two articles describe how to collect stories and compile estimates. This article goes on with the previous article to describe how to estimate a story with story.

The following describes the general checklists for estimation.

 

The estimation method for a story should have the following characteristics:
1. estimation results of Operation changes
2. Applicable to All stories
3. It is easy to make an estimation, and it does not take too much time.
4. Provide the main information about the progress and remaining work.
5. Inaccurate computing will not cause major problems.
6. The estimated results can be used to specify the release plan.

1. estimate data in the form of story points

The estimation method of story points can well meet the above characteristics. The team can customize appropriate story points. Our group preferences use a perfect workday as a story point for story estimation.
The perfect workday is the ideal workday. There are no other situations in coding for 8 hours a day. Of course, the actual situation may be different, so a perfect workday! = One day
2. Estimate by Team

The story point should be estimated by the entire team. Most of the team members should participate in the story point estimation. Everyone will come up with their own estimation results, finally, let's decide another story that everyone recognizes.
3. How to estimate

1. All participating customers and developers are together
2. From the first story, explain the story in detail until everyone knows the story clearly.
3. Each developer writes down their estimated values. The unit of a story is 2 perfect working days (2 days)
4. Everyone shows their estimation. Then everyone will explain why they have estimated this value.
5. Finally, the demonstrated team estimated a value that everyone recognizes.
6. Continue to estimate the next story

Those who know scrum should be able to feel that the above process is basically the same as the process of scrum estimation stories.
4. Perform triangle measurement on the evaluation results

After several estimates, perform a triangle measurement on the estimation results. The specific practices are as follows:
When estimating a story, it is estimated based on the relationship between the story and one or more other stories. Assume that a story is estimated to be four vertices, and the second story to two vertices, when we put these two stories together for consideration, programmers should recognize that the four stories are two times as many as the two.
The size of the other three vertices should be between the stories of the four vertices and those of the two vertices.
If the above triangle measurement results are incorrect, the team should re-estimate.
V. Impact of Pair Programming on story points

If you use Pair programming, the estimation of the story points should be the estimation after the pair.

Summary

Estimate a story with a story point. The story point is a relative estimation of the story complexity, workload, or duration.
The team should make estimation stories, and the estimation belongs to the team rather than the individual.
Have heard of other estimates for comparison and triangle Measurement
Whether the team uses Pair programming has no impact on the estimation of story points. The impact of Pair programming is the team's speed, not their estimation.
Responsibilities of developers

Defines the story points in one way, and works with teams to ensure consistency of the definition.
Responsible for giving honest estimates, giving low estimates without giving in to temptation
Estimate by Team
Estimates should be consistent with other estimates, that is, all stories of the same story point are of the same size.
Customer Responsibilities

Participate in estimation meetings, answer questions, and clarify story details.

<Development Management checklists> by dylove98 @ Development Management checklists