Session Brief: Bucket System

Goal

Artifact: Bucketed Backlog

Working Question

Which bucket does each item belong to relative to our references, and which items are so large or unclear that they need to be sliced or clarified before planning?

Context

List of items to sort (typically 30-150); acceptance criteria per item; reference items with assigned bucket values; known dependencies or risks.

Setup

• Format: Method session
• Duration: 30-90 min
• Mode: Workshop
• Participants: One facilitator for process and timeboxes; one product owner for item context; the delivery team (4-12 people); one scribe for assumptions and splits.
• Owner: One facilitator for process and timeboxes
• Participation mode: Team round, shared work and alignment
• Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Bucketed Backlog. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Whiteboard or Miro board with a horizontal row of predefined buckets (e.g. 1, 2, 3, 5, 8, 13, 20); cards or notes per item; reference items visible for each bucket; timer; marker colors for annotations.

Preparation

Stick the buckets horizontally on the wall (e.g. 1, 2, 3, 5, 8, 13, 20). Put a reference item into each bucket. Announce the rule: items go into one bucket only, no in-between values. Silence is the rule during sorting.

Agenda

1. Phase 1: Calibrate buckets (10 min) Owner: Facilitator Action: Review the buckets and reference items together. Anyone with a different understanding speaks up now. Rearrange references if needed until consensus is reached. Hint: Without calibrated references, the bucket scale is arbitrary. If no references from delivery history exist, choose three to five items before the workshop and bucket them. Output: Bucketed Backlog

2. Phase 2: First rapid sort (20-30 min) Owner: Facilitator Action: The team sorts items silently into buckets. Max 30 seconds per item. Gut feeling is enough, calibrated on the sample. Moving items back and forth is allowed. Hint: If people argue in this phase, the pace breaks. Rapid sorting is the core of the method. Detailed discussion comes later in phase 3. Output: Relative Estimates

3. Phase 3: Check bucket consistency (15-20 min) Owner: Facilitator Action: Compare the items in each bucket: do they really belong together? Move outliers into a more fitting bucket. Mark items in large buckets (13+, 20+) as split candidates. Hint: If a bucket is very full (>50% of items), the granularity is unsuitable. Refine the bucket scale or handle the items in a second estimation round with a finer scale. Output: Split Candidates

4. Phase 4: Splits and spikes (10-20 min) Owner: Owner Action: Either split items in large buckets (13+) with a proposal, owner, and deadline, or add a spike before them. Send items in the 'too unclear' bucket to refinement. Hint: Large buckets remain wishful thinking if no split proposal is made. If nobody can propose a split, the problem is not understood and the item belongs in discovery. Output: Bucketed Backlog

5. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Bucketed Backlog

Closeout

• Update result artifact: Bucketed Backlog
• Define location, version, and review recipients.
• Define owner, next step, and review date.

Bucketed Backlog: Bucket System

Working Question

Which bucket does each item belong to relative to our references, and which items are so large or unclear that they need to be sliced or clarified before planning?

Context

List of items to sort (typically 30-150); acceptance criteria per item; reference items with assigned bucket values; known dependencies or risks.

Participants

• Owner: One facilitator for process and timeboxes
• Participants: One facilitator for process and timeboxes; one product owner for item context; the delivery team (4-12 people); one scribe for assumptions and splits.

Input

Whiteboard or Miro board with a horizontal row of predefined buckets (e.g. 1, 2, 3, 5, 8, 13, 20); cards or notes per item; reference items visible for each bucket; timer; marker colors for annotations.

Template

Bucket System Working Template

Goal

Sorts many items into predefined estimate buckets to assess large backlogs quickly by relative size.

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

• Bucketed Backlog:
• Relative Estimates:
• Split Candidates:

Assumptions and open questions

• ...

Decision / Next step

Owner, date, and success signal.

Completion Check

• Bucketed Backlog is complete enough for review:
• Location:
• Version / status:
• Review by:
• Next step:

Next Step

• Review result
• Mark open questions
• Schedule review or decision