<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 October 29, 2025

    Your Root Cause Analysis is Flawed by Design

    Discover the critical flaw in your troubleshooting approaches. Employ network observability to extend your visibility across the entire service delivery path.

    icon
    Blog October 29, 2025

    Whose Fault Is It When the Cloud Fails? Does It Matter?

    In today's interconnected environments, it is vital to gain visibility into networks you don't own, including internet and cloud provider infrastructures.

    icon
    Blog October 29, 2025

    The Future of Network Configuration Management is Unified, Not Uncertain

    Read this post and discover how Broadcom is breathing new life into the trusted Voyence NCM, making it a core part of its unified observability platform.

    icon
    Office Hours October 23, 2025

    Rally Office Hours: October 9, 2025

    Discover Rally's new AI-powered Team Health Widget for flow metrics and drill-downs on feature charts. Plus, get updates on WIP limits and future enhancements.

    icon
    Course October 23, 2025

    AAI - Navigating the Interface and Refining Data Views

    This course introduces you to AAI’s interface and shows you how to navigate efficiently, work with tables, and refine large datasets using search and filter tools.

    icon
    Office Hours October 23, 2025

    Rally Office Hours: October 16, 2025

    Rally's new AI-driven feature automates artifact breakdown - transforming features into stories or stories into tasks - saving time and ensuring consistency.

    icon
    Blog October 22, 2025

    What’s New in Network Observability for Fall 2025

    Discover how the Fall 2025 release of Network Observability by Broadcom introduces powerful new capabilities, elevating your insights and automation.

    icon
    eBook October 22, 2025

    Modernizing Monitoring in a Converged IT-OT Landscape

    The energy sector is shifting, driven by rapid grid modernization and the convergence of IT and OT networks. Traditional monitoring tools fall short.

    icon
    Blog October 22, 2025

    Your network isn't infrastructure anymore. It's a product.

    See why it’s time to stop managing infrastructure and start treating the network as your company's most critical product. Justify investments and prove ROI.