Deciphering the Enigma of Story Points Across Teams

Over the past decade, a recurring query has been echoing in my ears: “How can we normalise Story Points across teams so that we can look across and maybe compare teams?” It’s high time we address this.

TLDR;

Story Points, while subjective, can be a valuable tool for team discussions and understanding. However, they shouldn’t be the primary metric for comparing teams or predicting future deliverables. Instead, focus on objective metrics like throughput, to gauge and optimise team performance.

These are not the metrics that you are looking for!

First and foremost, Story Points are inherently subjective. They’re influenced by individual perceptions, making them unsuitable for broad comparisons or future projections. While they might offer a vague direction, they’re often misused in planning and measuring.

The essence of agile frameworks like Scrum is value delivery, and the correlation between the subjective nature of story points and their velocity doesn’t necessarily equate to the value delivered. There are better choices for teams aiming to optimise their value delivery than relying solely on Story Points and Velocity.

But is there any value in Story Points?

Aye, there is. In my experience, Story Points can be a great tool during backlog item refinement. They foster discussions, highlighting what’s known and, more importantly, what’s not: Outliers during planning poker often signal gaps in understanding.

Tools like Story Points and Planning Poker can be invaluable in understanding when to dissect items further and spark discussions during refinement. I would expect teams to shift more towards right-sizing, ensuring that backlog items are feasible within a Sprint, as they gain more experience and understanding of the product, its domain, and the technology used.

A Story of Flow and Value

The crux of this discourse lies in two vectors: throughput and value.

Throughput is a tangible measure of items delivered over time.
Value, on the other hand, is a more elusive measure of the anticipated benefits from system changes.

It’s straightforward to gauge the throughput of backlog items and their flow. By noting when work enters and exits the system, we can derive the four pivotal flow metrics:

Throughput
Cycle Time
Work Item Age
Work In Process

Such metrics empower us to make informed decisions rooted in tangible data. They allow us to pinpoint potential issues, identify items needing further breakdown, and employ probabilistic forecasting for future projections.

Simultaneously, to truly maximise team output, we must also focus on the value of the work. Given its subjective nature, defining value can be multifaceted. A practical approach is to examine the four primary value areas from evidence-based management practices:

Current Value - Evaluating the existing product’s value. Is it meeting customer expectations?
Unrealised Value - Identifying gaps in your product that could be filled.
Time to Market - Assessing the speed from ideation to user engagement. Dormant value is essentially no value.
Ability to Innovate - Determining the balance between maintenance and innovation.

The ultimate goal is to enhance both throughput and value concurrently. Striking a balance is crucial; we neither want sluggish excellence nor a barrage of mediocrity.

TLDR;

These are not the metrics that you are looking for!

A Story of Flow and Value

What to read next

Story Points: A Ghost of Agile Past

Ditching Agile Banditry: Why Story Points and Velocity Metrics Are Undermining Your Team's Success

Avoiding Agile Banditry: Why Story Points and Velocity Are Misleading Metrics

Scrum is like communism, it doesn't work. Myth 2

Story Points & Velocity are a sign of an unsuccessful team

Rethinking Agile: Why Story Points, Team Sizes, and Emergent Architecture Need a Fresh Perspective

Detecting agile theatre with real delivery signals

Why Most Companies Operating Models Fail in Dynamic Markets

Don’t Manage Dependencies, Remove Them

The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery

Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?

Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team

Why Most Companies Operating Models Fail in Dynamic Markets

Don’t Manage Dependencies, Remove Them

The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery

Kendall Guide - A System of Work for AI Adoption

Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?

Estimating Better in an Overloaded System Is a Poor Man’s Strategy

Why Most Companies Operating Models Fail in Dynamic Markets

The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery

Getting Started with Objectives & Key Results

OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning

A certification proves you’ve passed a test

Most companies still get Product Ownership wrong

Detecting agile theatre with real delivery signals

Don’t Manage Dependencies, Remove Them

The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery

Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?

Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team

Estimating Better in an Overloaded System Is a Poor Man’s Strategy

Deciphering the Enigma of Story Points Across Teams

Table of Contents

TLDR;

These are not the metrics that you are looking for!

A Story of Flow and Value

Smart Classifications

Table of Contents

What to read next