Your Scrum Team Might Be Excellent at Building the Wrong Thing

Useful takeaways from this story.

They have a stable Sprint cadence, a clear Definition of Done, and they deliver a usable Increment every Sprint.

A team can apply empiricism thoroughly to how it builds and hardly at all to what it builds.

When that happens, every gain in delivery speed multiplies work nobody needed.

Building the complete brief

The page is ready to read now. The fuller skim-friendly version will appear here automatically.

The useful part

They have a stable Sprint cadence, a clear Definition of Done, and they deliver a usable Increment every Sprint. A team can apply empiricism thoroughly to how it builds and hardly at all to what it builds. When that happens, every gain in delivery speed multiplies work nobody needed.

How it works

There's also a video walkthrough below if you'd rather score along while you watch.
Image Most Scrum Teams I work with are good at delivery.
To help teams see this gap, I built a free, 10-question Product Discovery Maturity Assessment.
This post explains what it measures, why it's structured the way it is, and what to do with your result.
Two diamonds, one Scrum Team The assessment uses the Double Diamond, introduced by the UK Design Council in 2005.

Details worth keeping

The Sprint Review runs on time and stakeholders nod along. Scrum is built on empiricism and lean thinking.

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app