Bang-for-the-Buck

Choose this exercise

Purpose: Map candidate work items across value and cost dimensions to determine an implementation sequence.

Use it when: Use during backlog refinement, sprint planning, or roadmap sessions when a team needs cross-functional alignment between product scope and delivery effort.

Skip it when: Skip when tasks have strict sequential dependencies that dictate delivery order regardless of cost and value tradeoffs.

Group arrangement: Whole group (4 to 8 people). For 9 to 24 people, form parallel cross-functional groups of 4 to 8 members (for example, split 9 into 5 and 4), each with its own grid.

Timing: Source recommends 1 hour for 5 to 8 players. Maintained at 60 minutes.

Materials and tools

• 1 large whiteboard or clear wall space per group
• Painter's tape or dry-erase markers for drawing axes
• Pre-written candidate backlog items on sticky notes (3x3 inch, color A)
• Blank sticky notes for newly generated tasks (3x3 inch, color A, 1 pad per group)
• Sticky notes for axis labels (3x3 inch, color B, 14 notes per grid)
• Fine-tip markers (1 per participant)

Before participants arrive

1. Draw a large grid on the wall: horizontal axis labeled Cost/Effort, vertical axis labeled Value.
2. Write Fibonacci numbers (1, 2, 3, 5, 8, 13, 21) on color B sticky notes and place them along each axis in increasing order (Cost runs left to right; Value runs bottom to top).
3. Stick pre-written candidate backlog items (color A) in a holding area beside the grid.

Say this to open

Welcome. Today we will prioritize candidate work items by graphing relative value against delivery cost. We will use a Fibonacci scale on both axes. Product owners determine vertical value, and engineering or delivery leads establish horizontal cost. Our goal is an agreed delivery sequence, starting with high-value, low-cost tasks.

How to run it

1. Orient and generate tasks 5 minutes

   Speak the opening script. Explain the axes: Cost increases left to right (1 to 21), and Value increases bottom to top (1 to 21). Clarify roles: product or business owners lead vertical placement; delivery or engineering owners lead horizontal placement. Invite participants to spend 3 minutes silently writing additional backlog items on blank sticky notes, one item per note.

2. Pool and clarify items 10 minutes

   Have participants post newly written notes beside the existing backlog items. Read each new note aloud. Merge obvious duplicate items with the room's agreement. Ask the author of any ambiguous item to clarify its core deliverable in a single sentence. Keep each item concise.

3. Plot items on the matrix 25 minutes

   Take one item at a time. The product owner proposes a vertical position on the Value axis. The engineering lead proposes a horizontal position on the Cost axis. Move the note to the intersection point. If an item feels too costly, briefly ask if the team can reduce scope. If participants disagree on numbers, set the note at the higher cost estimate or split the item.

4. Establish execution order 10 minutes

   Review the full board. Trace items in clockwise order: start at top-left (high value, low cost: do first), move toward top-right (high value, high cost: schedule or slice), then review bottom-left (low value, low cost: quick fills). Identify bottom-right items (low value, high cost) to drop or postpone. Record the resulting sequence on a shared list.

5. Review and conclude 10 minutes

   Run a brief debrief with the whole room using the debrief questions. Hear 2 to 3 observations regarding early priorities and scope adjustments for high-cost items. Confirm ownership for the top-priority items and close the session.

Debrief questions

• Which items in the high-value, low-cost quadrant can we schedule immediately?
• Which high-value items sit too far to the right, and what can we cut to move them left?
• Where did product and delivery views diverge most, and what did that reveal?

Finished output: A completed 2D Fibonacci matrix of backlog items with a prioritized execution list transcribed in clockwise order.

Remote

Create a digital board with two perpendicular axes labeled Cost (horizontal) and Value (vertical), marked with Fibonacci increments (1, 2, 3, 5, 8, 13, 21). Place backlog items in a digital staging column. Share screen or invite everyone to the board. The facilitator or designated scribe moves notes as product and technical leads call out relative coordinates.

Hybrid

Display the digital whiteboard on a shared screen in the room. Remote and in-person participants write and view notes on the digital board. Appoint a room scribe to assist anyone without a laptop. Call on remote and in-person leads alternately when negotiating coordinates.

Access and participation choices

• Participants may write candidate items or suggest them verbally to a scribe.
• Anyone may choose to observe the placement discussion without defending an estimate.
• High-contrast markers and large labels ensure axis values are readable from across the room.

If the session gets stuck

Participants debate an item's technical cost or value endlessly without consensus.

Enforce a two-minute limit per item. If consensus stalls, assign the higher cost estimate, mark the note with a question mark, and move on.

All tasks are placed at maximum value (21), crowding the top edge of the board.

Apply relative ranking: allow at most two items in the 21 band without moving an existing one downward.

Terms used here

• Fibonacci scale: A sequence of numbers (1, 2, 3, 5, 8, 13, 21) where each number is the sum of the two preceding numbers, used in agile planning to reflect increasing uncertainty at larger scales.
• Backlog: An accumulated list of features, tasks, or candidate deliverables waiting to be scheduled.