<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
    Course September 17, 2025

    DX NetOps: Harness Syslog for Operational Visibility

    Learn how to configure DX NetOps for robust syslog ingestion, gaining comprehensive operational visibility by displaying all external syslog messages directly within DX NetOps Portal.

    icon
    Office Hours September 17, 2025

    Rally Office Hours: September 4, 2025

    In the latest edition of Rally office hours, learn how to view filter substitutions and then follow the weekly Q&A session with Rally product experts.

    icon
    Office Hours September 17, 2025

    Rally Office Hours: September 11, 2025

    Hear about recruiting MCP Server early adopters and ancestor filtering in Rally's Custom Lists, then follow the weekly Q&A session with Rally product experts.

    icon
    Blog September 16, 2025

    Powering RAG Pipelines With Automic Automation

    See how Automic Automation optimally equips you for the AI revolution, combining proven enterprise capabilities with the potential of generative AI.

    icon
    Blog September 16, 2025

    Unlock Real-Time AWS Observability With Streaming Ingestion in DX Operational Observability

    With streaming ingestion capabilities, DX Operational Observability offers visibility into your AWS telemetry, enhancing insights and incident response.

    icon
    Blog September 16, 2025

    Observability and IT Monitoring Governance: Establishing Order (Part 3 of 4)

    Find out how DX Unified Infrastructure Management (DX UIM) supports monitoring governance, enabling teams to manage configurations and track alarm policies.

    icon
    Blog September 16, 2025

    Observability and IT Monitoring Governance (Part 4 of 4)

    This post shows how baselines, KPIs, and thresholds are essential for monitoring governance. See how IT can shift from reactive to proactive IT management.

    icon
    Blog September 12, 2025

    What's Really Happening in Your Branch Office Network?

    Fragmented monitoring tools create critical visibility gaps in branch networks. Find out why you need network observability to pinpoint the cause of issues.

    icon
    Office Hours September 12, 2025

    Rally Office Hours: August 28, 2025

    Learn about the general availability of the AI writing assistant in Rally, then follow the weekly Q&A session with Rally product experts.