| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>Scrum&#92;guidances&#92;concepts&#92;&#92;velocity.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: velocity.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_ZoVtEUSNEdyDx7cbCULuLg CRC: 1202631935 -->Velocity<!-- END:presentationName,_ZoVtEUSNEdyDx7cbCULuLg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_ZoVtEUSNEdyDx7cbCULuLg CRC: 387737401 -->Velocity is the rate of delivery for a team.<!-- END:briefDescription,_ZoVtEUSNEdyDx7cbCULuLg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: mainDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:mainDescription,-Juyx9-ueXCZ9LpMR7tYkHw CRC: 4241176794 --><h3> |
| Overview |
| </h3>An agile team is able to declare some level of capacity for doing work each iteration. This capacity is used when the |
| team goes to a planning session and elects to take on work. The hope is that they only take on what is achievable by the |
| team. This metric that provides this determination is called the team velocity.<br /> |
| <br /> |
| |
| <h3> |
| How Is It Calculated? |
| </h3>The velocity is based on the amount of completed features from past, or historic, sprints. Each feature that is |
| accepted into a sprint has gone through some level of team estimation. That estimation is stipulated with <a class="elementLinkWithUserText" href="./../../../Scrum/guidances/termdefinitions/story_point_65CC5BB6.html" guid="_ZoVtE0SNEdyDx7cbCULuLg">Story points</a>. |
| <p> |
| It will take 2-3 iterations before a team can get a somewhat accurate velocity determination. Though as teams go from |
| iteration to iteration, it is worth noting for observers changes in practices, or maturation in estimation that will |
| lead to the refinement of their velocity. |
| </p><br /> |
| |
| <h3> |
| What Does It Measure? |
| </h3>As stated in the overview, the velocity metric measures a particular teams capability to work through stories that |
| they have estimated. An example is for a team that for the last 3 sprints has got to a point of producing 20 story points |
| worth of features every sprint. That velocity is only useful when the team performs estimates on future features, so that |
| they know how much of that work they can pull into a sprint. It is also useful to the product owner to aid in their |
| assessment of the remaining work that has been identified for a release.<br /> |
| <br /> |
| |
| <h3> |
| How Is It Used? |
| </h3>Velocity is used as a way to measure a teams output of sustainable effort. It will be used by the team at planning |
| sessions as a <em>tide</em> mark to ensure they do not take on more work than they can actually perform. It can also be |
| used by the team and interested parties to indicate any improvements in the teams performance, or declines in a teams |
| performance. In this respect, it should be used as a team management aid to help warn or confirm the changes in working |
| practices for a team during a sprint. |
| <p> |
| An example might be that a team takes on some process changes. By reviewing the teams velocity after these changes, it |
| will be one of many indicators to help the team understand the impact that the change has caused. |
| </p><br /> |
| |
| <h3> |
| Can Team Velocities Be Compared? |
| </h3>Since each team will estimate work in slightly different ways, based on their own working experiences and knowledge, |
| the estimates that they create for new features are only <em>accurate</em> for that team. Thus, relying on estimates that |
| the team did not actually make, will not be a true measure of how much work they can take on based on their |
| <strong>own</strong> experiences. |
| <p> |
| In short, velocities cannot be used as a way to compare teams.<br /> |
| </p> |
| <p> |
| <br /> |
| </p><!-- END:mainDescription,-Juyx9-ueXCZ9LpMR7tYkHw --> |
| </body> |
| </html> |
