Purpose
When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.
Agile Decision method
Bucket System
The bucket system places work in fixed size ranges so relative estimates emerge quickly and disputed items remain visible.
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.
Which relative size bucket fits each item when the team places in parallel, corrects once, and separates genuine conflicts?
- Participants
- 3-12
- Time
- 30–60 minutes for 20–50 comparable items.
The practice is repeated across comparable work items.
Buckets
Size lane
Explain the ordered bucket scale and shared meaning of relative size.
Anchors
Bucket anchors
Place two known items together and calibrate remaining buckets relatively.
Place
First placement
Distribute items; team members silently place one item at a time in a bucket.
Correct
Conflict pile
Others may move an item once; a second move request sends it to conflict.
Close
Bucket estimate
Resolve conflicts, split oversized items, and save anchors and assumptions.
Add new evidence at review and version estimates with the prior state.
A good fit when
Wenn eine größere Menge Arbeit schnell grob geschätzt werden soll, verteilt sie Items in vorgegebene Größenräume. Sie spart Diskussion, ohne die Vergleichbarkeit ganz aufzugeben.
Ideal for
- Large backlogs
- Release planning
- Relative sizing
Not good for
- Single high-risk items
- Fine-grained cost calculation
- Unclear backlog items
Outputs
Bucket estimate
Rapidly calibrated backlog in relative buckets with anchors, conflict items, assumptions, and split/clarification actions.
Bucket System · working structure
Fictional example
Fictional values show the actual method fields.
| Item | Included | Anchor | First bucket | Move | Final | Follow-up |
|---|---|---|---|---|---|---|
| Delete tokenAdd evidence and rationale. | Build, test, rollout | Validation rule=3 | 3 | None | 3 | Ready |
| Save cardAdd evidence and rationale. | Build, test, security, rollout | Between 3 and 13 | 5 | 5→8; guest scope disputed | 5 without guests | Scope recorded |
| Provider migrationAdd evidence and rationale. | Auth, migration, fallback | Larger than 13 | 40 | None | 40 | Split into three items |
1. Included
- Delete token
- Build, test, rollout
- Save card
- Build, test, security, rollout
- Provider migration
- Auth, migration, fallback
2. Anchor
- Delete token
- Validation rule=3
- Save card
- Between 3 and 13
- Provider migration
- Larger than 13
3. First bucket
- Delete token
- 3
- Save card
- 5
- Provider migration
- 40
4. Move
- Delete token
- None
- Save card
- 5→8; guest scope disputed
- Provider migration
- None
5. Final
- Delete token
- 3
- Save card
- 5 without guests
- Provider migration
- 40
6. Follow-up
- Delete token
- Ready
- Save card
- Scope recorded
- Provider migration
- Split into three items
All values are fictional.
First step
Set a comparable item set and included work; prepare buckets 1, 2, 3, 5, 8, 13, 20, 40, 100 and two known anchors.
Deep dive
How it works
It uses fixed buckets as a shared grid and places tasks relative to each other first. A large volume is sorted quickly, while only the contested or borderline items need to be discussed in more detail.
In detail
The Bucket System uses fixed size buckets, such as Fibonacci numbers or T-shirt sizes. After calibration with a few reference items, many more items are quickly placed into the appropriate buckets. Discussion focuses on items that are disputed between buckets or seem too large. The result is a broad, consistent estimate for many items with less fatigue than item-by-item estimation.
Facilitation
Prepare the buckets and a few reference items in advance. Prevent in-between values so the group stays deliberately coarse. Mark large-bucket items for splitting or further discovery.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Artifact templates
Bucket System: WorksheetSet subject, data, roles, flow, and review.markdown
Bucket System: WorksheetSet subject, data, roles, flow, and review.
markdownbucket-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
| Item | Included | Anchor | First bucket | Move | Final | Follow-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
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
Agile
Planning Poker
Instead of Bucket System, choose Planning Poker when you want to calibrate estimates relative to each other and surface shared assumptions.
Agile
Story Points
Instead of Bucket System, choose Story Points when individual backlog items should be deliberately rated relative to each other instead of just falling into size classes.
Agile
Affinity Estimation
Has the team group items silently, discusses deviations, and produces consistent relative size pictures.
Agile
T-Shirt Sizing
Sorts backlog items roughly by reference sizes and flags early on which items will later need splitting or clarification.
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".
Agile
Scrum
Product Backlog, Sprint Goal, Increment, and retrospective loops create a repeatable cadence for complex product work.
Constraints and origin
MediumWorkshop30-90 min
Profile
- Method form
- Decision method
- Participants
- 3-12
- Time
- 30-90 min
- Maturity
- Established
- Origin
- Agile Community
Next up: Story Splitting