This document discusses agile estimation and planning. It defines an estimate as an unbiased process to predict duration or cost, and notes that estimates become more accurate over time as uncertainty decreases. It recommends using story points for estimating, which are relative units based on size, complexity and unknowns. The document also describes planning poker, an iterative group estimation technique where estimators assign cards to stories until estimates converge.
The vertical axis contains the degree of error that has been found in estimates created by skilled estimators at various points in the project. Estimates created very early in the project are subject to a high degree of error. Estimates created at Initial Concept time can be inaccurate by a factor of 4x on the high side or 4x on the low side (also expressed as 0.25x, which is just 1 divided by 4). The total range from high estimate to low estimate is 4x divided by 0.25x, or 16x.
http://zuulcat.com/tag/agile/
http://zuulcat.com/tag/agile/
http://zuulcat.com/tag/agile/
http://zuulcat.com/tag/agile/
http://www.crisp.se/planningpoker
http://www.crisp.se/planningpoker
They thought they has 780 hrs of work . It went up as we figured out something's are more tough and discovered some new stuff . Team discovered they cant deliver on time . The product owner dropped some portions of it
On this burndown chart, the team started a project that was planned to be eleven two-week sprints. They began with 200 story points of work. The first sprint went well and from the chart you can infer that they had around 180 story points of work remaining after the first sprint. During the second sprint, however, the estimated work remaining actually burned up. This could have been because work was added to the project or because the team changed some estimates of the remaining work. From there the project continued well. Progress slowed during sprint 7 but then quickly resumed.