Estimate

Relative Estimation

Relative Estimation

Strive for normalized approach to story effort / size estimation. If you are not there yet, and you are the scrum master or release train engineer, then you will help your team(s) get to Normalized approach to estimation -- a common approach to estimation -- set only once at the beginning/starting point /re-set point when the teams/trains do not have yet a historical velocity, or, the teams on the train got various approaches to estimation creating a scenario wherein there are wild variations of estimates across the train (this scenario needs a re-set to a starting point with a common…
Read More

The Product Backlog Estimate

The estimate is in Points -- a measureless thingy to gauge the team's effort to define, build, test, and potentially deploy a thing of value. The estimate does not mean, 'it will take us this much time to build this thing.' The estimate is a starting point, a best guess, from which the Story -- even the Iteration and even the whole backlog for this matter -- can be empirically managed. The Scrum team selects the amount of backlog items (Stories) that it believes it can handle (the load vis-a-vis their capacity) in an Iteration based on these estimates. Load…
Read More
X

Forgot Password?

Join Us