←Back to the Kraken The Kraken · Arm Nº 07 · Status overhead

Story Points vs. Time Metrics

A tool used for the wrong job
cannot do the right one.

The short answer

Story points show complexity. Time needs its own metrics.

Story points help one crew talk about how complex a piece of work is. They are not hours, and they do not travel between crews: when someone joins or leaves, the scale moves with them. Questions about time are answered by flow metrics: how many items finish per week, how long each one takes. They come straight from the board, without anyone turning points into days.

A catch of herring can be counted. Nobody needs to guess.

What an honest system shows by itself

Throughput

How many come aboard each week.

Cycle time

How long one takes from the net to the deck.

Work in progress

How many are in the net right now.

Work item age

The one that has been in the net too long.

Easy to count, right?

But …

Points measure the catch, not the clock

Find the smallest catch and the biggest, then place everything else between them. That is all story points were made for.

1
Herring
2
Lobster
3
Squid
5
Ray
8
Turtle
13
Shark
21
Whale
Every crew, its own scale

Gear, skills, room in the hold: a whale is one job for a whaler, another for a fishing boat.

The numbers grow fast on purpose: the bigger the catch, the more complex the hunt.

Kinds of status overhead

Five ways to count the wrong thing

Story points are a fine tool inside one crew. Trouble starts when they are asked to answer questions they were never made for.

Points become daysEight points of complexity turn into eight days of work.
One scale for every crewA five in one crew is a whale. In the next, it is five sardines.
A whale in the netOne huge piece counts as one, next to the small ones. Every count is wrong from then on.
New crew, old scaleSomeone joins, someone leaves. The points still pretend nothing has changed.
Always
more fish
Velocity always has to rise, when it was meant to stay steady and help the crew find its balance.

How status overhead shows

Typical indicators. Not a complete list, but the ones that show up most often.

Sign 1Points stay long after they stopped teaching anythingSign 2Velocity is compared between teamsSign 3A missed sprint goal is reported, not reflected onSign 4The board is altered to look on courseSign 5The working tool and its metrics disagreeSign 6The numbers are made for someone outside the crewSign 7Status is only known by asking someoneSign 8Estimates are defended, not discussedSign 9Points are counted per person

Let the flow tell the time

Every company needs to know when a voyage ends and how long one catch takes. Four charts that answer questions around time, and more.

Cumulative flow diagram
When do we arrive?
WEEKSITEMSTODAYBACKLOGDONE
Done, planned at 80 % of the usual paceArrival, where done meets the backlog
  • Will we make the date?
  • Where does work pile up?
  • Is the backlog growing faster than the catch?
Monte Carlo forecast
How sure can we be?
ARRIVAL WEEKRUNS
85 of 100 runs arrive by this week
  • How much fits before the date?
  • How likely is the date we promised?
  • What does more cargo do to the arrival?
Control chart
How long does one catch take?
FINISHEDDAYS
85 of 100 finish below this line
  • Which kind of work keeps landing above the line?
  • Is the crew getting more predictable?
  • How long is too long for one catch?
Work item age
Why is this catch taking longer than the rest?
DOINGREVIEWTESTINGAGE
85 of 100 finish below this line
  • Which catch will miss its usual time?
  • Where does work wait the longest?
  • Is it time to finish before starting more?
The golden rule

Metrics are there to steady the ship, not to compare or push the crew.

They belong to the crew that sails, not to every deck above it. Used to judge a crew, they soon show what the judges want to see.

Ready to let the log write itself?

A free discovery call, 30 minutes, remote. No slide deck, no obligation.

Send a signal
Talk with us in English · in German