What is velocity?
|
0
|
|
|
|
|
1
|
Velocity is not the number of Product Backlog Items (PBIs) a team can do in one iteration (this would only make sense if all PBIs had the same size which is very unlikely the case). Velocity is the quantity of work a team can achieve in one iteration and is thus expressed in the same unit you use to estimate your PBIs, usually points. Velocity is used as yesterday's weather method: "tomorrow will be like today". You measure the actual velocity (how much points did the team burn during the last iteration) and use this value to pick up and commit on as much PBIs (total size) for the next iteration. |
||
|
|
|
2
|
Take a look at this description for a somewhat more elaborate explanation. |
||
|
|
|
1
|
Velocity is the rate at which the team completes the work. Velocity can be measured in number of stories, number of story points, or quantity of ideal hours/days. By "completes the work", this means that the stories are "done" by the definition of the team - and should include QA. |
||
|
|
|
0
|
Velocity is the number or user stories a team can do in one iteration/sprint and is used to illustrate the rate of progress for a development team. |
||
|
|
