what is velocity in scrum with example

What is Velocity in Scrum?

By Michael Rodriguez
AD

Velocity in Scrum, an agile project management framework, is a critical metric that helps teams estimate the amount of work they can complete in a single sprint. It's not a measure of how hard the team is working, but rather a gauge of how much value the team can deliver consistently over time. Understanding velocity is key to planning future sprints and releases, and it's calculated by measuring the total number of points completed in a sprint.

Before diving into the details of what velocity is and how it's calculated, let's consider a practical example. Imagine a software development team using Scrum. At the end of their first sprint, they've completed features that totaled 30 story points. If they can consistently complete this amount of work each sprint, their velocity would be 30. This doesn't mean they have to complete exactly 30 points every sprint, but it gives them a baseline for planning future work.

Understanding Velocity in Scrum

Velocity is a relative measure that compares the rate of work done with the rate of work planned. It's not an absolute measure of productivity, but rather a tool for teams to understand their capacity and predict their output. Velocity is typically measured in story points, a unit of measure used to estimate effort, complexity, and uncertainty in software development.

AD
How to measure Velocity in Scrum?
How to measure Velocity in Scrum?
Agile Velocity – Can Training Offer Sufficient Return On Investment?
Agile Velocity – Can Training Offer Sufficient Return On Investment?
a bar chart showing the number of teams in each team and how they use it
a bar chart showing the number of teams in each team and how they use it

It's essential to note that velocity isn't a fixed number. It can change over time as teams get more familiar with their sprint goals, improve their estimation skills, or encounter unexpected obstacles. Therefore, it's crucial to continually monitor and adjust velocity to ensure accurate planning.

Calculating Velocity

Calculating velocity is straightforward. At the end of each sprint, add up the story points of all the work completed and divide by the number of sprints. For example, if a team completes 40 story points in a two-week sprint, their velocity would be 20 points per sprint.

Sprint Velocity - FourWeekMBA
Sprint Velocity - FourWeekMBA
Velocity vs Speed in 4 Simple Examples (With Real Math)
Velocity vs Speed in 4 Simple Examples (With Real Math)
What is Velocity
What is Velocity

However, it's not just about the total points. A good Scrum team also considers the complexity and risk of the work. For instance, a team might complete 20 points of simple, low-risk tasks in one sprint and 10 points of complex, high-risk tasks in another. In this case, their velocity might still be considered 15 points per sprint, as the latter sprint was more challenging.

Using Velocity for Planning

Once a team has established a consistent velocity, they can use it to plan upcoming sprints and releases. They can estimate how long it will take to complete a specific backlog of work by dividing the total story points by their velocity. For example, if a team has a backlog of 100 story points and their velocity is 20 points per sprint, they can estimate that it will take five sprints to complete the work.

AD

Velocity planning isn't about rigidly adhering to a number. It's about understanding a team's capacity and using that information to make informed decisions about what can be accomplished in a given timeframe. It's also about continuous improvement. As the team's capabilities change, so should their velocity.

Scrum Velocity - FourWeekMBA
Scrum Velocity - FourWeekMBA
the agiler and scrum guide is shown in this graphic diagram, which shows how to
the agiler and scrum guide is shown in this graphic diagram, which shows how to
a white spiral notebook with words and pictures on the page, which are labeled swiff 101
a white spiral notebook with words and pictures on the page, which are labeled swiff 101
Speed vs Velocity Difference, Formula & Examples
Speed vs Velocity Difference, Formula & Examples
What is Scrum?
What is Scrum?
the diagram shows how to use it in different ways, including text and images on each side
the diagram shows how to use it in different ways, including text and images on each side

Common Myths About Velocity

Despite its widespread use, velocity has its share of myths and misconceptions. One common myth is that increasing velocity means a team is working harder. This isn't true. Velocity isn't a measure of a team's effort or hours worked; it's a measure of the value delivered. A team could increase its velocity by improving its processes, not necessarily by working more hours.

Another myth is that a team's velocity should be constant. As mentioned earlier, velocity can and should fluctuate over time. A static velocity could indicate that the team isn't challenging itself or that it's not adapting to changes in its environment. A good Scrum team should continually strive to improve its processes and its velocity.

AD

Velocity and Team Morale

While velocity is a useful planning tool, it's essential to consider its impact on team morale. Focusing too much on velocity can create pressure to complete work artificially, leading to burnout and low morale. It's crucial to strike a balance between using velocity as a planning tool and fostering a culture of sustainable, healthy work practices.

the scrum explanation is shown in this graphic
the scrum explanation is shown in this graphic

Moreover, velocity should never be used as a measure of a team's performance or worth. A high velocity doesn't automatically mean a team is doing well, and a low velocity doesn't mean a team is failing. Each team has its unique context, and what matters most is whether they're delivering value and improving in line with their goals.

In the dynamic world of software development, velocity is a powerful tool for planning and continuous improvement. It's not about working harder, but about working smarter. By understanding velocity, Scrum teams can set realistic goals, predict their output, and make informed decisions about their work. But it's not just about the numbers. It's about the people behind them, their skills, their motivations, and their capacity for growth. So, grab your story points, estimate your work, and start planning your next sprint. Your velocity awaits.

AD
AD