<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=1110556&amp;fmt=gif">
Skip to content
    August 1, 2022

    Agile Velocity

    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

    Tag(s): ValueOps , Rally

    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

    icon
    Blog September 9, 2025

    Observability and Monitoring Governance (Part 1 of 4)

    Find out how strong monitoring governance can help IT teams cut through the noise, see what truly matters, and act with precision.

    icon
    Blog September 9, 2025

    Observability and Monitoring Governance (Part 2 of 4)

    Read this post and discover some of the top downstream benefits of establishing strong monitoring governance. Gain best practices on how and where to start.

    icon
    Blog September 9, 2025

    DX UIM Hub Interconnectivity and the Benefits of Static Hubs

    Find out how using static hubs is a powerful way to enhance observability. Discover when and how to use static hubs, and the benefits they can provide.

    icon
    Blog September 8, 2025

    Broadcom Recognized as a Leader: Engineering the Future of Service Orchestration

    Read this post and see why Broadcom was named a Leader in the 2025 Gartner® Magic Quadrant™ for Service Orchestration and Automation Platforms.

    icon
    Video September 8, 2025

    Customer Spotlight: Global Bank MUFG Saves Millions of Dollars

    MUFG’s Bruce Frank discusses how the global bank invokes Broadcom's Automated Analytics & Intelligence (AAI) to manage SLAs and ensure regulatory compliance, saving millions of dollars annually.

    icon
    Blog September 8, 2025

    The "Lighthouse" of Strategy: Guiding Your Organization Through Decision Chaos

    Strategic clarity is key. See how strategic portfolio management (SPM) helps align resources and decisions for better business outcomes and ROI.

    icon
    Blog September 8, 2025

    4 Ways AppNeta Enhances Cost-Focused Cloud Planning

    See how AppNeta delivers insights that enable cloud architects to correlate wasted spending with performance degradation and proactively relocate resources.

    icon
    Video September 5, 2025

    Automic Automation Cloud Integrations: Azure Functions Agent Integration

    Broadcom's Azure Functions Automation Agent lets you easily execute Azure Functions, monitor and manage them with your existing enterprise workload automation, as well as other cloud-native...

    icon
    Blog September 4, 2025

    The Public Internet Is Not Your WAN

    Moving beyond MPLS was a strategic necessity. To succeed in modern environments, you need to stop guessing about internet performance and start measuring it.