
The Backlog Maze
Prioritise debt, bugs, and new features to deliver value without exhausting the team.
In short. The Backlog Maze is a serious game (agile) for 4–30 participants, lasting 60–120 min. Created by serious-games.com. Use it for: amélioration continue, prise de décision, priorisation.
Card by serious-games.com, updated 22 November 2026. Original game by serious-games.com.
Participants embody an agile team from a fictional company that must prepare and execute a sprint under constraints. They arbitrate between features, bugs, and technical debt, with limited capacity and unforeseen events. The game makes visible the trade-offs between product value, technical risk, customer satisfaction, and team motivation. It is played in teams of 4 to 6, and concludes with a review and comparative retrospective.
Walkthrough
- 1
Game Framework and Team Formation
10 minThe facilitator presents the scenario: "You are the product team of NovaApp, a fictional application that is losing momentum. Your mission: deliver a useful sprint without breaking the platform or demotivating the team." They form teams of 4 to 6 people and assign roles: Product Owner, Scrum Master, Developer, Agile Coach, and possibly QA or Client. Participants read their roles and ask their first questions. This step establishes a common framework and forces everyone to adopt a different decision-making angle.
Tip : If the group is small, some participants can take on two roles. Ask teams to choose a name to enhance engagement.
- 2
Reading the Backlog and Scoring Rules
15 minThe facilitator distributes the same backlog of 18 cards to each team: 6 features, 4 bugs, 5 technical debts, and 3 internal improvements. Each card indicates a capacity cost of 1 to 5, a business value of 0 to 8, a customer impact of 0 to 5, a reduced technical risk of 0 to 5, and a motivation effect of -2 to +2. They say: "Your sprint capacity is 14 points, not one more." Teams read the cards, clarify the vocabulary, and begin to identify tensions. The goal is to make prioritisation concrete and quantified.
Tip : Prepare the cards in advance. To save time, also display the scoring formula: value + customer impact + reduced risk + motivation.
- 3
Initial Prioritisation
15 minThe facilitator announces: "You have 12 minutes to order your backlog from most to least priority, then 3 minutes to finalise your top five choices." Participants debate in role: the Product Owner defends the value, the Developer alerts on debt, the Scrum Master monitors capacity, and the Agile Coach questions the criteria. Each team places their cards in the High, Medium, or Low Priority columns. The objective is to provoke explicit trade-offs rather than a simple vote of opinion.
Tip : Prohibit soft consensus: each team must formulate a prioritisation rule in one sentence, for example, "We secure first what protects active customers."
- 4
Sprint Planning Under Constraint
15 minThe facilitator provides a sprint sheet with 14 capacity slots and says: "Select the cards you commit to delivering. Any capacity overrun is forbidden." Teams choose their items, calculate their projected score, and note a major risk hypothesis. Then the facilitator quickly checks the capacities and asks each team to announce their sprint goal in one sentence. This step transforms priority into realistic commitment and reveals delivery trade-offs.
Tip : If a team is stuck, ask: "Which card would you remove if your capacity decreased by 3 points?" This reveals the true priority.
- 5
Surprise Event and Adaptation
15 minThe facilitator has each team draw an Event card from 10: minor failure, urgent customer request, absent developer, worsening debt, impatient sponsor, positive feedback, critical bug, market opportunity, reusable automated test, or late clarification. They read: "The plan never survives intact in reality; you have 8 minutes to adapt your sprint." Teams can replace up to two cards, but each change costs 1 motivation point. They recalculate their score and justify their decision. The goal is to experience agility as reasoned adaptation, not as permanent change.
Tip : Ensure the event is not perceived as a punishment: emphasise the quality of reasoning over the raw score.
- 6
Simulated Sprint Execution
15 minThe facilitator gives each team 6 Focus tokens. For each committed card, the team must assign at least 1 token and explain in 30 seconds how they are organising to deliver it. Cards without sufficient tokens are considered at risk and lose 2 points; a technical debt card ignored while a technical event has occurred loses an additional 2 points. Participants discuss quickly, prioritise effort, and note the delivered cards. This mechanic links planning to execution capacity and coordination.
Tip : Use a visible timer. If discussions become too detailed, remind: "We are simulating decisions, not the complete design of the solution."
- 7
Product Review and Results Comparison
15 minEach team presents in 2 minutes their sprint goal, the delivered cards, their final score, and the main trade-off assumed. The facilitator notes four indicators on the board: total value, reduced technical risk, final motivation, and number of cards delivered. They say: "There is not one single good backlog; there are choices consistent with a strategy." Other teams can ask a short question, without lengthy debate. This step highlights the diversity of strategies and their visible consequences.
Tip : Do not rank solely by total score. Highlight teams that protected motivation, reduced a risk, or formulated a clear strategy.
- 8
Retrospective and Learnings
15 minThe facilitator initiates a retrospective in three columns: Continue, Stop, Try. They ask: "What helped your team decide quickly and well? What drained your energy?" Participants write down two ideas individually, then share them in their team before a collective discussion. The facilitator connects the learnings to agile practices: transparency, limited capacity, value, feedback, and continuous improvement. This step transforms the game into transferable lessons for real work.
Tip : Conclude with a concrete commitment: each participant completes the sentence "In my next backlog, I will test...".
Variants
- Short version 60 minutes: play with 12 backlog cards, 10 capacity points, one scoring indicator, and remove the simulated execution step.
- Advanced version: add a second sprint of 25 minutes. Unresolved debts increase the cost of certain cards by 1 point, and teams must show the effect of their choices over time.
- Leadership version: require the Product Owner to change mid-game. The team must reformulate their strategy and observe what remains stable or not in the collective decision.
- Remote version: use a collaborative board with columns Backlog, Priority, Sprint, Delivered, and Retro. The cards are digital post-its, the Focus tokens are icons, and the events are drawn by the facilitator from a numbered list.
Debrief guide
- What criteria truly guided your priorities: business value, customer satisfaction, technical debt, risk, motivation, or something else?
- When did you feel the strongest disagreement, and how did you resolve it?
- How did the surprise event change your initial plan and your decision-making process?
- What did you sacrifice to maintain sprint capacity, and what were the consequences?
- Which role most influenced the final decision, and was that desirable?
- What does your score not show but matters in a real agile team?
- What prioritisation rule could you reuse in your professional context?
Facilitator reviews
No review yet. Have you run this game? Your feedback will help the next facilitators.
Similar games
Same objectives or same category, to vary or follow up.

Lightning Decision Jam (LDJ)
Quickly solve a collective problem by replacing debate with silent work, voting, and clear actions.

20/20 Vision
Prioritising features through successive comparisons, just like at the optician: which one is the clearest?

Buy a Feature
Prioritise through fictitious purchasing to reveal what truly matters and why.

Min Specs (the minimum rules)
Identify the few truly essential rules and eliminate over-prescription.

Impact/effort matrix
Get your group to prioritise initiatives by revealing the real choices between quick wins, major projects and thankless tasks.

Dot voting
Reveal a heat map of the group’s preferences, without debate or lobbying during the vote.