methodatlas
Method guideAgile

Bucket System

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

ComplexityMedium
Time30-90 min
Participants3-12
FormatWorkshop
MaturityEstablished
Plan Bucket System
01

Prerequisite

What needs to be finished first

Complete firstComparable subject

Set a comparable item set and included work; prepare buckets 1, 2, 3, 5, 8, 13, 20, 40, 100 and two known anchors.

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

Refined items, shared Done definition, ordered 1–100 buckets, reference items, and conflict pile

Missing data remains visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

Refined items, shared Done definition, ordered 1–100 buckets, reference items, and conflict pile

People / roles

Delivery team places · product owner clarifies · facilitator manages conflict pile

Pre-read

Set a comparable item set and included work; prepare buckets 1, 2, 3, 5, 8, 13, 20, 40, 100 and two known anchors.

Time needed

30–60 minutes for 20–50 comparable items.

Setup

Prepare a workspace with Buckets · Anchors · Place · Correct · Close; separate example from live data.

03

Core question

The one question this method answers

Which relative size bucket fits each item when the team places in parallel, corrects once, and separates genuine conflicts?

04

Flow

Phases with goal, actions, output and pitfall

The bucket system uses fixed buckets as a shared scale and places tasks relative to one another. It sorts a large set quickly while reserving detailed discussion for disputed or marginal items.

Bucket System · working structure

Fictional example

Fictional values show the actual method fields.

Bucket System · working structure
ItemIncludedAnchorFirst bucketMoveFinalFollow-up
Delete tokenAdd evidence and rationale.Build, test, rolloutValidation rule=33None3Ready
Save cardAdd evidence and rationale.Build, test, security, rolloutBetween 3 and 1355→8; guest scope disputed5 without guestsScope recorded
Provider migrationAdd evidence and rationale.Auth, migration, fallbackLarger than 1340None40Split into three items

  1. 1. Included

    Delete token
    Build, test, rollout
    Save card
    Build, test, security, rollout
    Provider migration
    Auth, migration, fallback

  2. 2. Anchor

    Delete token
    Validation rule=3
    Save card
    Between 3 and 13
    Provider migration
    Larger than 13

  3. 3. First bucket

    Delete token
    3
    Save card
    5
    Provider migration
    40

  4. 4. Move

    Delete token
    None
    Save card
    5→8; guest scope disputed
    Provider migration
    None

  5. 5. Final

    Delete token
    3
    Save card
    5 without guests
    Provider migration
    40

  6. 6. Follow-up

    Delete token
    Ready
    Save card
    Scope recorded
    Provider migration
    Split into three items

All values are fictional.

Reference · original teaching example

  1. 1

    Buckets

    Size lane

    Goal

    Size lane: Explain the ordered bucket scale and shared meaning of relative size.

    Inputs for this step

    • Set a comparable item set and included work; prepare buckets 1, 2, 3, 5, 8, 13, 20, 40, 100 and two known anchors.
    • Refined items, shared Done definition, ordered 1–100 buckets, reference items, and conflict pile

    Actions

    • Explain the ordered bucket scale and shared meaning of relative size.

    Output

    Size lane

    Explain the ordered bucket scale and shared meaning of relative size.

    Quality check

    Are scale, Done, and included work identical for everyone?

    Pitfall

    Buckets are read as hours or person-days. Define the scale explicitly relative to team anchors.

    Timing: 5–10 minutes

  2. 2

    Anchors

    Bucket anchors

    Goal

    Bucket anchors: Place two known items together and calibrate remaining buckets relatively.

    Inputs for this step

    • Size lane

    Actions

    • Place two known items together and calibrate remaining buckets relatively.

    Output

    Bucket anchors

    Place two known items together and calibrate remaining buckets relatively.

    Quality check

    Are anchors completed, understood work?

    Pitfall

    A desired target item becomes the anchor. Use stable historical items with the same Done definition.

    Timing: 5–10 minutes

  3. 3

    Place

    First placement

    Goal

    First placement: Distribute items; team members silently place one item at a time in a bucket.

    Inputs for this step

    • Bucket anchors

    Actions

    • Distribute items; team members silently place one item at a time in a bucket.

    Output

    First placement

    Distribute items; team members silently place one item at a time in a bucket.

    Quality check

    Does the pass remain fast and free of early debate?

    Pitfall

    Every placement starts an immediate debate. Place all items first and mark questions.

    Timing: 10–20 minutes

  4. 4

    Correct

    Conflict pile

    Goal

    Conflict pile: Others may move an item once; a second move request sends it to conflict.

    Inputs for this step

    • First placement

    Actions

    • Others may move an item once; a second move request sends it to conflict.

    Output

    Conflict pile

    Others may move an item once; a second move request sends it to conflict.

    Quality check

    Do different work models become visible without ping-pong?

    Pitfall

    Items move repeatedly between buckets. Allow one move, then clarify deliberately.

    Timing: 5–10 minutes

  5. 5

    Close

    Bucket estimate

    Goal

    Bucket estimate: Resolve conflicts, split oversized items, and save anchors and assumptions.

    Inputs for this step

    • Conflict pile

    Actions

    • Resolve conflicts, split oversized items, and save anchors and assumptions.

    Output

    Bucket estimate

    Resolve conflicts, split oversized items, and save anchors and assumptions.

    Quality check

    Are 40/100 items split and unclear items owned?

    Pitfall

    Large buckets enter an iteration unchecked. Split large work and recalibrate references with actual data.

    Timing: 10–15 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

Bucket System · relative GrößenklassenViele Backlog Items schnell in vorbereitete Schätz-Buckets sortieren
Bucket SystemDie Skizze zeigt Backlog-Karten, vorbereitete Schätz-Buckets, Referenzitems und Split-Kandidaten.Viele Items relativ in feste Größen-Buckets sortierenReferenzen kalibrieren die Skala, große Buckets markieren Kandidaten für Splitting oder Discovery.Backlog Itemsviele Karten schnell sortierenStory AStory BBugfixEpic X1kleinUIText2leichtToggleFilter3mittelSSOReport5großAPIImport8+splittenEpicSpikeReferenzitems1 = Tooltip5 = API-EndpointSplit Candidateszu groß oder unklarEpic XSpike nötig
Form

Rapidly calibrated backlog in relative buckets with anchors, conflict items, assumptions, and split/clarification actions.

Versioning / ownership

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

Tool alternatives
  • 1–100 bucket lane
  • Reference items
  • Conflict and clarification pile

bucket-system-working-template.md

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

Bucket System: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Practice run Time: 30–60 minutes for 20–50 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 Done definition, ordered 1–100 buckets, reference items, and conflict pile
  • Roles: Delivery team places · product owner clarifies · facilitator manages conflict pile
  • Advance information: Set a comparable item set and included work; prepare buckets 1, 2, 3, 5, 8, 13, 20, 40, 100 and two known anchors.
  • Overall time needed: 30–60 minutes for 20–50 comparable items.
  • Setup: Prepare a workspace with Buckets · Anchors · Place · Correct · Close; separate example from live data.

Prepare for the work steps

Buckets: Size lane

  • Set a comparable item set and included work; prepare buckets 1, 2, 3, 5, 8, 13, 20, 40, 100 and two known anchors.
  • Refined items, shared Done definition, ordered 1–100 buckets, reference items, and conflict pile

Anchors: Bucket anchors

  • Size lane

Place: First placement

  • Bucket anchors

Correct: Conflict pile

  • First placement

Close: Bucket estimate

  • Conflict pile

Bucket System · working structure

ItemIncludedAnchorFirst bucketMoveFinalFollow-up
Delete token
Save card
Provider migration
  • Delete token: Add evidence and rationale.
  • Save card: Add evidence and rationale.
  • Provider migration: Add evidence and rationale.

The blank worksheet contains prompts only.

Reference · original teaching example

Buckets: Size lane

Expected artifact: Size lane

Explain the ordered bucket scale and shared meaning of relative size.

Entry:

...

  • Are scale, Done, and included work identical for everyone?

Anchors: Bucket anchors

Expected artifact: Bucket anchors

Place two known items together and calibrate remaining buckets relatively.

Entry:

...

  • Are anchors completed, understood work?

Place: First placement

Expected artifact: First placement

Distribute items; team members silently place one item at a time in a bucket.

Entry:

...

  • Does the pass remain fast and free of early debate?

Correct: Conflict pile

Expected artifact: Conflict pile

Others may move an item once; a second move request sends it to conflict.

Entry:

...

  • Do different work models become visible without ping-pong?

Close: Bucket estimate

Expected artifact: Bucket estimate

Resolve conflicts, split oversized items, and save anchors and assumptions.

Entry:

...

  • Are 40/100 items split and unclear items owned?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/bucket-system/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.

bucket-system-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: Bucket System · working structure

ItemIncludedAnchorFirst bucketMoveFinalFollow-up
Delete tokenBuild, test, rolloutValidation rule=33None3Ready
Save cardBuild, test, security, rolloutBetween 3 and 1355→8; guest scope disputed5 without guestsScope recorded
Provider migrationAuth, migration, fallbackLarger than 1340None40Split into three items
07

Pitfalls

Recognize symptoms and steer against them

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

  1. Size laneBuckets are read as hours or person-days.View in phase
  2. Bucket anchorsA desired target item becomes the anchor.View in phase
  3. First placementEvery placement starts an immediate debate.View in phase
  4. Conflict pileItems move repeatedly between buckets.View in phase
  5. Bucket estimateLarge buckets enter an iteration unchecked.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Buckets: Are scale, Done, and included work identical for everyone?
Stop Anchors: Are anchors completed, understood work?
Stop Place: Does the pass remain fast and free of early debate?
Stop Correct: Do different work models become visible without ping-pong?
Stop Close: Are 40/100 items split and unclear items owned?

Where to go next?

Story Splitting method illustration showing its working structure
Agile
Story Splitting

Splits oversized items flagged in the bucket system into smaller slices.

Paper illustration for Planning Poker.
Agile
Planning Poker

Later refines contested buckets with a more precise team estimate.

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