Velocity

Velocity is a measure of done Backlog Items delivered per Timebox (Iteration or Cycle). It is used to provide a forecast of future done work. Conditions are that the team and the timebox are stable over time.

Calculating Velocity

It is possible to calculate the Velocity of a Team for a single Iteration or Cycle. For better results we sum ip all “done” work of all timeboxes, measured in Story Points  (SP), and divide them by the number of timeboxes. This results in the mean Velocity over time.

 

Application of Velocity

  • Working Teams use it to calculate how much work to pull into the Iteration Backlog within Iteration Planning meetings. For better results it is typically normalized by non-regular absences like holidays and planned absences.
  • Product Owners use it to predict milestones and release dates of products.

\r\n


Further suitable links:

Events Roles Groups Artifacts
Team Planning

Team Sync

Team Backlog Refinement

Team Review

Team Retrospective

.

Cluster Planning

Cluster Sync

Cluster Backlog Refinement

Cluster Review

Cluster Retrospective

.

Portfolio Planning

Organisation Sync

Portfolio Refinement

Portfolio Review

Organisation Retrospective

Team Product Owner

Team System Engineer

Team Scrum Master

.

Cluster Product Owner

Cluster System Engineer

Cluster Scrum Master

.

Portfolio Owner

Portfolio Architect

Organisation Scrum Master

Working Team

Community of Practice

.

Team Product Owner Group

Team System Engineer Group

Team Scrum Master Group

Cluster Management Circle

.

Cluster Product Owner Group

Cluster System Engineer Group

Cluster Scrum Master Group

Organisation Management Circle

Team Backlog

Inspectable Results

Team DoD

Team Improvement Backlog

.

Cluster Backlog

Usable Knowledge & System Increment

Cluster DoD

Cluster Improvement Backlog

.

Portfolio Backlog

Systems & Applications

System Platforms & Variants

Organisation DoD

Organisation Improvement Backlog

Team Calendar

The Team Calendar shows the availability of the Nucleus and Extended Team members for an Iteration. Each Team Member enters planned absences in order to determine the gross capacity of the team before (or at the latest in) the Iteration Planning. The gros capacity is used to adjust the  work forecast by relating it to the team’s Velocity, which significantly improves predictability.

Example of a Team Calendar

The concept of a calendar to determine the gros capacity can also be used for Clusters and cycles, ideally based on public holidays and the longer-term vacation planning of the team members .

If the team does not work with iterations but continuously by means of Kanban, the team calendar is maintained for several weeks in advance on a weekly basis.