methodatlas
Method guideFacilitation

Dot Estimation

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityLow
Time5-20 min
Participants3-20
FormatWorkshop
MaturityEmerging
Plan Dot Estimation
01

Prerequisite

What needs to be finished first

Complete firstComparable subject

Set comparable items, included work, and a relative S/M/L/XL or 1–13 lane; agree on exactly one dot per person and item.

Without a common frame, values are not comparable.
Complete firstEvidence access

Refined items, shared Definition of Done, relative size lane, one person-coloured dot per item, and clarification log

Missing data remains visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

Refined items, shared Definition of Done, relative size lane, one person-coloured dot per item, and clarification log

People / roles

Delivery team dots · product owner clarifies · facilitator reads dispersion

Pre-read

Set comparable items, included work, and a relative S/M/L/XL or 1–13 lane; agree on exactly one dot per person and item.

Time needed

20–45 minutes for 8–20 comparable items.

Setup

Prepare a workspace with Frame · Dot · Read · Clarify · Close; separate example from live data.

03

Core question

The one question this method answers

Where does each person independently place an item on the same relative size lane, and which dot spread reveals different models of the work?

04

Flow

Phases with goal, actions, output and pitfall

Dot estimation makes individual assessments visible at once, showing where experience converges and where perceptions diverge. The following discussion clarifies differences and produces a useful relative size for planning.

Dot Estimation · working structure

Fictional example

Fictional values show the actual method fields.

Dot Estimation · working structure
ItemScopeAnchorsDots R1SpreadClarificationDots R2Outcome
Save cardAdd evidence and rationale.Build, test, security, rolloutS=validation; L=new payment methodS, M, M, M, LBroad around MGuest/migration out; security staysM, M, M, M, MM
Provider migrationAdd evidence and rationale.Auth, migration, fallback, certificationL=new payment methodL, XL, XL, XL, XLHigh at XLSeveral outcomesNo new roundXL → split

  1. 1. Scope

    Save card
    Build, test, security, rollout
    Provider migration
    Auth, migration, fallback, certification

  2. 2. Anchors

    Save card
    S=validation; L=new payment method
    Provider migration
    L=new payment method

  3. 3. Dots R1

    Save card
    S, M, M, M, L
    Provider migration
    L, XL, XL, XL, XL

  4. 4. Spread

    Save card
    Broad around M
    Provider migration
    High at XL

  5. 5. Clarification

    Save card
    Guest/migration out; security stays
    Provider migration
    Several outcomes

  6. 6. Dots R2

    Save card
    M, M, M, M, M
    Provider migration
    No new round

  7. 7. Outcome

    Save card
    M
    Provider migration
    XL → split

All values are fictional.

Reference · original teaching example

  1. 1

    Frame

    Dotting basis

    Goal

    Dotting basis: Agree item set, meaning of size, Done, and reference anchors.

    Inputs for this step

    • Set comparable items, included work, and a relative S/M/L/XL or 1–13 lane; agree on exactly one dot per person and item.
    • Refined items, shared Definition of Done, relative size lane, one person-coloured dot per item, and clarification log

    Actions

    • Agree item set, meaning of size, Done, and reference anchors.

    Output

    Dotting basis

    Agree item set, meaning of size, Done, and reference anchors.

    Quality check

    Is everyone estimating the same scope on one scale?

    Pitfall

    Dots vote on priority, risk, and effort at once. Name one estimation dimension and prioritise separately.

    Timing: 5–8 minutes

  2. 2

    Dot

    Dot pattern

    Goal

    Dot pattern: Each person independently places exactly one dot per item on a hidden or simultaneously revealed lane.

    Inputs for this step

    • Dotting basis

    Actions

    • Each person independently places exactly one dot per item on a hidden or simultaneously revealed lane.

    Output

    Dot pattern

    Each person independently places exactly one dot per item on a hidden or simultaneously revealed lane.

    Quality check

    Were dots independent and voices equally weighted?

    Pitfall

    Early dots are visible and anchor later choices. Collect hidden dots or reveal together.

    Timing: 5–10 minutes

  3. 3

    Read

    Dispersion finding

    Goal

    Dispersion finding: Describe clusters, edge dots, and broad spread without averaging or immediately taking a majority.

    Inputs for this step

    • Dot pattern

    Actions

    • Describe clusters, edge dots, and broad spread without averaging or immediately taking a majority.

    Output

    Dispersion finding

    Describe clusters, edge dots, and broad spread without averaging or immediately taking a majority.

    Quality check

    Is disagreement preserved as information?

    Pitfall

    The modal dot is accepted without comment. Keep high/low perspectives and the distribution visible.

    Timing: 3–5 minutes

  4. 4

    Clarify

    Clarified scope

    Goal

    Clarified scope: Edge perspectives explain scope, risks, and existing components; update item or assumption.

    Inputs for this step

    • Dispersion finding

    Actions

    • Edge perspectives explain scope, risks, and existing components; update item or assumption.

    Output

    Clarified scope

    Edge perspectives explain scope, risks, and existing components; update item or assumption.

    Quality check

    Does clarification explain why work models differed?

    Pitfall

    People defend their dot rather than their work model. Discuss included work, then dot again.

    Timing: 5–10 minutes

  5. 5

    Close

    Dot estimate

    Goal

    Dot estimate: Re-dot, record a supportable size, and turn residual spread into a split or spike.

    Inputs for this step

    • Clarified scope

    Actions

    • Re-dot, record a supportable size, and turn residual spread into a split or spike.

    Output

    Dot estimate

    Re-dot, record a supportable size, and turn residual spread into a split or spike.

    Quality check

    Is outcome relative, justified, and assigned a next step?

    Pitfall

    Dots are converted to hours or statistical precision. Keep relative class and anchor; forecast separately from delivery data.

    Timing: 5–10 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Dot Estimation · Effort as HeatmapDistribute limited dots across items, read clusters as effort, risk, or uncertainty signals, and discuss them deliberately
Dot EstimationThe visual shows Dot Estimation as a board with items, dot clusters, heatmap signal, and next clarification steps.Create a fast group signal for effort or uncertaintyDots are not an exact estimate; they show which items feel large, risky, or in need of clarification.Dots meanclearly define effort, risk, oruncertainty5 dots per persondistribute silently, no discussionduring votingsilent votingclusters show need for discussionnot precise effortMake items visibleItem Aclear, smallItem Bunclear scopeItem Ctechnical riskItem Dmedium sizeHeatmap signaldiscuss clusters deliberately, donot calculate mechanicallyNext stepsplit, clarify, or check risk
Form

Dot distributions per item with relative location, spread, clarified assumptions, final size class, and split/spike actions.

Versioning / ownership

Record date, team, data state, and review date; preserve prior versions.

Tool alternatives
  • Relative size lane
  • Person-coloured dots
  • Dispersion and clarification log

dot-estimation-working-template.md

Set subject, data, roles, flow, and review.

Dot Estimation: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Practice run Time: 20–45 minutes for 8–20 comparable items.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Refined items, shared Definition of Done, relative size lane, one person-coloured dot per item, and clarification log
  • Roles: Delivery team dots · product owner clarifies · facilitator reads dispersion
  • Advance information: Set comparable items, included work, and a relative S/M/L/XL or 1–13 lane; agree on exactly one dot per person and item.
  • Overall time needed: 20–45 minutes for 8–20 comparable items.
  • Setup: Prepare a workspace with Frame · Dot · Read · Clarify · Close; separate example from live data.

Prepare for the work steps

Frame: Dotting basis

  • Set comparable items, included work, and a relative S/M/L/XL or 1–13 lane; agree on exactly one dot per person and item.
  • Refined items, shared Definition of Done, relative size lane, one person-coloured dot per item, and clarification log

Dot: Dot pattern

  • Dotting basis

Read: Dispersion finding

  • Dot pattern

Clarify: Clarified scope

  • Dispersion finding

Close: Dot estimate

  • Clarified scope

Dot Estimation · working structure

ItemScopeAnchorsDots R1SpreadClarificationDots R2Outcome
Save card
Provider migration
  • Save card: Add evidence and rationale.
  • Provider migration: Add evidence and rationale.

The blank worksheet contains prompts only.

Reference · original teaching example

Frame: Dotting basis

Expected artifact: Dotting basis

Agree item set, meaning of size, Done, and reference anchors.

Entry:

...

  • Is everyone estimating the same scope on one scale?

Dot: Dot pattern

Expected artifact: Dot pattern

Each person independently places exactly one dot per item on a hidden or simultaneously revealed lane.

Entry:

...

  • Were dots independent and voices equally weighted?

Read: Dispersion finding

Expected artifact: Dispersion finding

Describe clusters, edge dots, and broad spread without averaging or immediately taking a majority.

Entry:

...

  • Is disagreement preserved as information?

Clarify: Clarified scope

Expected artifact: Clarified scope

Edge perspectives explain scope, risks, and existing components; update item or assumption.

Entry:

...

  • Does clarification explain why work models differed?

Close: Dot estimate

Expected artifact: Dot estimate

Re-dot, record a supportable size, and turn residual spread into a split or spike.

Entry:

...

  • Is outcome relative, justified, and assigned a next step?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/dot-estimation/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

dot-estimation-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Dot Estimation · working structure

ItemScopeAnchorsDots R1SpreadClarificationDots R2Outcome
Save cardBuild, test, security, rolloutS=validation; L=new payment methodS, M, M, M, LBroad around MGuest/migration out; security staysM, M, M, M, MM
Provider migrationAuth, migration, fallback, certificationL=new payment methodL, XL, XL, XL, XLHigh at XLSeveral outcomesNo new roundXL → split
07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Dotting basisDots vote on priority, risk, and effort at once.View in phase
  2. Dot patternEarly dots are visible and anchor later choices.View in phase
  3. Dispersion findingThe modal dot is accepted without comment.View in phase
  4. Clarified scopePeople defend their dot rather than their work model.View in phase
  5. Dot estimateDots are converted to hours or statistical precision.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Frame: Is everyone estimating the same scope on one scale?
Stop Dot: Were dots independent and voices equally weighted?
Stop Read: Is disagreement preserved as information?
Stop Clarify: Does clarification explain why work models differed?
Stop Close: Is outcome relative, justified, and assigned a next step?

Method after Agile Community. The method emerged from, or was spread through, the agile community of practice. Curated with 1 sources.

Sources: Dot Estimation

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Story Splitting method illustration showing its working structure
Agile
Story Splitting

Breaks items with wide residual spread into smaller, more estimable slices.

Paper illustration for Affinity Estimation.
Agile
Affinity Estimation

Sorts the dotted sizes into a consistent relative size picture.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods