Agile Scrum: Velocity
Scrum does not define techniques for expressing or prioritizing items in the Product Backlog
and it does not define an estimation technique. A common technique is to estimate in terms
of relative size (factoring in effort, complexity, and uncertainty) using a unit of “story points”
or simply “points”.
Over time, a Team tracks how much work it can do each Sprint; for example, averaging 26
points per Sprint. With this information they can project a release date to complete all features,
or how many features can be completed by a fixed date, if the average continues and nothing
changes. This average is called the “velocity” of the team. Velocity is expressed in the same
units as the Product Backlog item size estimates.
Ref from: Pete Deemer ScrumTI.com
Scrum does not define techniques for expressing or prioritizing items in the Product Backlog
and it does not define an estimation technique. A common technique is to estimate in terms
of relative size (factoring in effort, complexity, and uncertainty) using a unit of “story points”
or simply “points”.
Over time, a Team tracks how much work it can do each Sprint; for example, averaging 26
points per Sprint. With this information they can project a release date to complete all features,
or how many features can be completed by a fixed date, if the average continues and nothing
changes. This average is called the “velocity” of the team. Velocity is expressed in the same
units as the Product Backlog item size estimates.
Ref from: Pete Deemer ScrumTI.com
No comments:
Post a Comment