How can you measure the velocity of a technology consulting project team?

1 What is velocity?

Velocity is a measure of how much work a team can complete in a given time period, usually a sprint or an iteration. It is expressed as the number of story points, or units of value, that the team delivers in each sprint. Story points are assigned to each user story, or feature, based on the complexity, effort, and uncertainty involved in developing it. For example, a user story that requires a simple change in the user interface might be worth one story point, while a user story that involves integrating a new API might be worth five story points. The total number of story points that the team finishes in a sprint is the team's velocity.

2 Why does velocity matter?

Velocity matters because it helps you estimate how long it will take to complete the project, plan the scope and schedule of the project, and monitor the team's productivity and efficiency. By knowing the team's velocity, you can forecast how many sprints are needed to deliver the desired outcome to the client, and adjust the scope and schedule accordingly. You can also compare the team's actual velocity with the expected velocity, and identify any issues or risks that might affect the project delivery. Additionally, you can use velocity to motivate and empower the team, by setting realistic and achievable goals, celebrating successes, and providing feedback and support.

3 How to calculate velocity?

To calculate velocity, you need to track the number of story points that the team completes in each sprint. You can use tools like Jira, Trello, or Excel to create a backlog of user stories, assign story points to each one, and mark them as done when they are finished. You can also use a burndown chart, which shows the remaining work in each sprint, or a burnup chart, which shows the completed work in each sprint, to visualize the team's velocity. To get an accurate and consistent velocity, you need to use the same definition of done for each user story, and avoid changing the story points or scope during the sprint.

4 How to improve velocity?

To improve velocity, you need to focus on improving the value, speed, and quality of the work done by the team. Prioritize user stories that deliver the most value to the client and align with project objectives, and break down complex ones into smaller chunks. Refine and clarify user stories with the team and the client before beginning the sprint to avoid ambiguity and rework. Utilize agile practices such as daily stand-ups, sprint reviews, and retrospectives to communicate, collaborate, and learn from each other. Additionally, remove any impediments or dependencies that could slow down or block the team's work. Lastly, encourage experimentation, innovation, and learning from mistakes.

5 How to use velocity wisely?

Velocity is a useful metric, but it is not the only one that matters. You should not use velocity as a way to compare, judge, or pressure the team, as this might lead to unrealistic expectations, lower quality, and reduced morale. You should also not use velocity as a fixed and final target, as this might ignore the changing needs and feedback of the client. Instead, you should use velocity as a way to guide, inform, and improve the team's work, and as a starting point for a deeper conversation with the team and the client. You should also use other metrics, such as customer satisfaction, business value, and quality indicators, to measure the success of the project.

6 Here’s what else to consider

This is a space to share examples, stories, or insights that don’t fit into any of the previous sections. What else would you like to add?