methodatlas
Agile

NoEstimates

Moves backlog, sprint work, and team flow toward a concrete result through "clarify the planning question", "slice work smaller", and "calibrate regularly with reality".

Core question
Which planning decision do we need to make, and which flow data or slicing rules answer it more cheaply than an estimation ritual?
MediumWorkshop + asynclaufend
Open runsheetPlan sessionStart comparison
Purpose

Helps clarify backlog, sprint work, and team flow in concrete terms. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules.

How it works

The team follows the steps "clarify the planning question", "slice work smaller", "measure throughput and cycle time", "derive the forecast from historical data", and "calibrate regularly with reality". Each step is made visible. At the end, Throughput Data, Flow Forecast, and Slicing Rules are available so decisions, tests, or actions can continue directly.

Visual orientation

Method sketch for a quick mental model.

NoEstimates · Flow statt AufwandsschätzungPlanungsfrage klären, Arbeit klein schneiden und Forecasts aus Durchsatz, Cycle Time sowie historischen Flow-Daten ableiten
NoEstimatesDas Visual zeigt NoEstimates als Flow-Ansatz mit Planungsfrage, kleinen Items, Durchsatzdaten und Forecast statt Aufwandspunkten.Planung über Flow-Daten statt über Aufwandspunkte steuernNoEstimates ersetzt unnötige Schätzrituale durch kleine Arbeitseinheiten, gemessenen Durchsatz und regelmäßige Kalibrierung.PlanungsfrageWelche Entscheidung braucht wirklicheine Schätzung?Kleine Itemsähnlich schneiden, zählen stattschätzenFlow-Daten statt Aufwandspunkte123456Throughput & Cycle Timehistorische Lieferung beobachtenFlow ForecastWahrscheinlichkeit statt EinzelzusageSchätzritual nur nutzen, wenn es Entscheidungswert hatArbeit klein haltenForecast regelmäßig kalibrieren

Flow

  1. 1Clarify the planning question
  2. 2Slice work smaller
  3. 3Measure throughput and cycle time
  4. 4Derive the forecast from historical data
  5. 5Calibrate regularly with reality

The runsheet guides execution with 4 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Flow-based teams
  • Kanban systems
  • Stable delivery data

Not good for

  • New teams without history
  • Large fuzzy initiatives
  • Budget processes with detailed estimates

Deep dive

In detail

NoEstimates is less a single technique than a counterposition to elaborate effort estimation. The approach asks which decision a estimate actually supports and whether that same decision can be made better through smaller items, historical throughput data, or continuous learning. Instead of producing story points, work is sliced as similarly small as possible and observed through flow metrics. Forecasts come from completed work and probabilities, not from estimated effort.

Facilitation

First clarify which planning decision needs to be answered. Invest in slicing, flow metrics, and transparent assumptions. Avoid dogmatic debates; sometimes a light estimate is cheaper than building a heavy data foundation.

Output artifacts
Throughput DataFlow ForecastSlicing Rules
Tags
estimationforecastingflow

Sources

Q&A with Vasco Duarte on the #NoEstimates Book - InfoQinfoq.com#NoEstimates: How to Measure Project Progress Without Estimating - Vasco Duarte - Google Booksbooks.google.de
Artifact templates
NoEstimates Working TemplateCompact working template for NoEstimates with context, input, output artifacts, and next step.
markdown

no-estimates-working-template.md

Compact working template for NoEstimates with context, input, output artifacts, and next step.

NoEstimates Working Template

Goal

Approach that reduces explicit effort estimation and instead uses small items, throughput, and forecasting.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Throughput Data:
  • Flow Forecast:
  • Slicing Rules:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

Story Points

Statt NoEstimates, wenn ihr relative Komplexität statt Kalenderzeit schätzen wollt und eure Schätzung im Team kalibrieren möchtet.

Planning Poker

Statt NoEstimates, wenn euer Umfeld weiterhin Schätzsignale braucht und relative Größen teamweit kalibriert werden müssen.

Similar methods

All methods
Agile
Scrum

Product Backlog, Sprint Goal, Increment, and retrospective loops create a repeatable cadence for complex product work.

Agile
Ideal Days

Moves backlog, sprint work, and team flow toward a concrete result through "explain the ideal day unit", "calibrate with a reference item", and "do not confuse it with calendar days".

Delivery
Monte Carlo Forecasting

Moves scope, sequence, and delivery flow toward a concrete result through "formulate the forecast question", "choose historical flow data", and "update the forecast regularly".

Agile
Planning Poker

Turns backlog, sprint work, and team flow into a tangible result by presenting the item, clarifying questions, and discussing deviations before estimating again.

Statt NoEstimates, wenn euer Umfeld weiterhin Schätzsignale braucht und relative Größen teamweit kalibriert werden müssen.

Agile
T-Shirt Sizing

Turns backlog, sprint work, and team flow into a tangible result by explaining the scale, choosing reference items, and marking large items.

Agile
Affinity Estimation

Turns backlog, sprint work, and team flow into a tangible result by preparing items as cards, building a relative size axis, and clarifying outliers and uncertainties.