Agile Development (iii)-Estimating stories

The first two articles are about collecting stories and writing estimates, and this article goes on to the previous article, and then, with the story, if the story is estimated

The following are mainly estimates of the general checklists

The method of estimating a story should have the following characteristics
1. Operation Change estimate result
2. Applicable to all stories
3, it is easy to make a simple estimate, do not need to spend too much time
4. Provide main information on progress and remaining work
5, the calculation is not accurate also does not have the big problem
6. The estimated results can be used to specify the release plan
First, in the form of story points to estimate

Story-point estimation can be well satisfied with the above characteristics of the estimation method. The team can customize the appropriate story points, and our group prefers to take a perfect workday as a story point to estimate the story.
Perfect working day is the ideal working day, 8 hours a day has been coding no other situation. Of course, the reality may not be the same. So a perfect workday! = One day
Second, the team to estimate

The story point should be estimated by the entire team, the majority of the team will participate in the story of the story point estimation, everyone put their own estimates, and finally everyone agreed to a story point
Third, how to estimate

1. All participating customers and developers get together
2. Start with the first story and explain the story in detail until everyone knows the story.
3, each developer first write down their own estimated value, a story point for units, such as 2 perfect working day (2 days)
4, everyone shows their own estimates, and then everyone says why this value is estimated
5, finally through the demonstration team to estimate a value that everyone recognizes
6. Continue to estimate the next story

A friend who understands scrum should be able to feel that the process above is essentially the same as the process of scrum estimating a story.
Iv. triangulation of the results of the assessment

After making a few estimates, the results are measured in triangulation, as follows
When estimating a story, it is estimated by the relationship of the story to one or more of the other stories, assuming that a story is estimated to be 4 story points, the second story is 2 story points, and when the 2 stories are taken together, programmers should recognize that 4 story points are 2 times the story of twice story points.
The story of the other 3 story points should be between 4 story points and 2 story points.
If the results of the triangulation above are not correct, the team should re-estimate.
The influence of pairing programming on the story point

If pairing programming is used, the estimate of the story point should be a pair-by-pair estimate
Summary

Using story points to estimate stories, story points are relative estimates of story complexity, workload, or duration
The team should estimate the story and estimate that it belongs to the team rather than the individual
I've heard other estimates do a triangulation.
Whether the team uses pair programming has no effect on the story point estimation, and pair programming affects the team's rate, not their estimate
Responsibilities of the developer

Responsible for defining the story points in one way, and for the team to be available and relevant, to strive to ensure that this definition is consistent
Be responsible for giving an honest estimate, not yielding to the temptation to live under pressure and giving a low estimate
Responsible for team estimation
The responsible estimate should be consistent with other estimates, that is, all stories of the same story point are of the same size.
Customer Responsibilities

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

Agile Development (iii)-Estimating stories