...
The development team estimates project points for components by assigning achieving consensus on a single value to for each component through discussion that reaches consensus [3]. The team does NOT assign multiple point values, each of which depends upon who will complete the work. Instead, the team works to identify a reasonable project point value regardless of who is eventually tasked with a given component.
The strategy the team uses is called Planning Poker [1]. Participants in planning poker include all developers on the team. The goal in estimating each component is a valuable estimate good approximation that can be arrived at cheaply. In order to estimate component sizes using planning poker, proceed through the following sequence of steps.
...
2. Usually for the first three iterations or until the team feels comfortable with their estimates for project components.
3. If at some any point further on in a project, estimates seem to be systematically inaccurate. If such a situation arises, it is necessary for the team to revisit its estimates and the rationale underlying those estimates.
...
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|