In Agile software development, velocity is the first metric we learn and it’s the most widely used. When used appropriately, measuring velocity is a powerful way to improve the capacity planning of individual teams. When used for anything other than estimating an individual team's capacity, however, velocity measurement becomes dangerous.
In this post, I’ll share my opinions and lessons learned in the field using velocity. I’ll detail some landmines to watch out for, how to increase your chances of avoiding them, and what to do if something goes “boom.”
What is Agile Velocity?
First things first: Agile velocity is not a one-size-fits-all concept, and it is not a Swiss Army knife. Agile velocity is intended to serve a very specific function, and using it for anything else can be dangerous. Agile velocity enables a team to estimate their probable work output during a timebox, such as an iteration or program increment.
There are two forms of velocity: what a team thinks they can deliver in story points and what a team actually delivers. Only by measuring both can a team improve their ability to estimate and plan over time.
A team's velocity will differ from timebox to timebox, and that’s to be expected. As a team grows more proficient over time, their velocity should steadily trend upwards and stabilize into a predictable range. When this happens, velocity becomes a great metric for forecasting how many work items a team might complete in a given timebox. This metric can also form the basis for improving the accuracy and reliability of planning your agile work, not only within one team but across many teams.
Sometimes Things Go Wrong
Despite education, training, and the best intentions, even a simple and seemingly innocuous thing like Agile velocity can be misapplied. As the saying goes, “forewarned is forearmed.”
Ponder these common examples of misusing velocity so you can guard against them. If you’re currently doing any of these things, you should stop. If asked to do any of these things, don’t.
- Using velocity to measure value
- Using velocity to measure work output
- Using velocity to measure performance
- Using velocity to compare one team to another
- Using velocity to set delivery dates
Be Ready and Be a Team Player
If someone asks you to use velocity inappropriately, it’s not enough to say “that’s wrong” and refuse; be ready to provide alternatives. Take the initiative, reach out to your coach or the body within your organization responsible for Agile practices and ask them how to respond to these potential situations. Publish any standards you come up with so that your product owner and business stakeholders understand how to use—and not use—velocity.
Remember to be open-minded and give people the benefit of the doubt. Just because they ask to use velocity incorrectly doesn’t mean they don’t have a real need or the best of intentions. Engage them in a little discovery to make sure you both agree on what is really needed, then work together to devise a solution. By addressing the examples I shared earlier, you’ll likely be able to offer valid and pre-approved alternatives to meet their needs right away.
Tips from the Field
Jarrod Reed
Jarrod Reed is a ValueOps Domain Specialist with the Agile Operations Division of Broadcom Enterprise Software. He advocates for Lean, Agile, and Value Stream Management in that role. Merging theory with more than a quarter century of "hands-on" experience, he helps customers transform people, processes, and...
Other resources you might be interested in
Automic Automation: Getting Started with the Automic Web Interface Version 26
Get started with the v26 Automic Web Interface (AWI). Learn how to navigate the modernized UI, customize your workspace, and move between perspectives.
Automic Automation v26: Zero Downtime Upgrade (ZDU)
Learn how to employ the Zero Downtime Upgrade (ZDU) process. Transition from Automic v24 to v26 while your mission-critical workflows continue to execute.
ValueOps ConnectALL: Synchronize Jira and Rally for Frictionless Cost Accounting
This course teaches you how to integrate Jira data into Rally for the purpose of frictionless cost accounting in Clarity.
AppNeta: Introducing the Intelligent Alarms Experience
Learn how to use the new Intelligent Alarms experience in AppNeta, including new metrics, new user workflows, and the new thresholding, event, and alarm system.
Rally Office Hours: April 16, 2026
Join Rally Office Hours to get expert tips and the latest product news. Explore new AI controls, Monte Carlo simulation for milestones, and more.
Announcing AutoSys 24.2: Accelerating Operations with Self-Service Agility and Automated Security
Learn how AutoSys 24.2 helps reduce administrative bottlenecks, minimize security risks, and accelerate incident resolution.
The Next Chapter for AutoSys: Moving Toward the Intelligent Control Plane
Is Broadcom still investing in AutoSys? Yes! Learn about the V26 roadmap, which features MCP orchestration, AI job types, and AI-powered developer assistance.
Automic Automation: Upgrading to Version 26
This course guides you through and demonstrates the process to upgrade Automic Automation from version 24 to version 26 on a Windows platform. The Unix upgrade is virtually the same.
Automic Automation: Integrated Database Maintenance
See how Automic administrators can leverage the Integrated Database Maintenance suite to optimize their Automation Engine database for peak performance.