Split Poker

Split Poker is a serious game that helps teams decompose oversized user stories into deliverable elements. This game promotes collaboration and enhances understanding of user needs while optimising workflow.

Walkthrough

1. 1

   Introduction

   10 min

   The facilitator begins by explaining the importance of breaking down user stories for an efficient workflow. "Today, we will practice breaking down user stories using the Split Poker game. This will help us better understand user needs and optimise our backlog." Participants are invited to ask questions to clarify the workshop's objective.

   Tip — Use concrete examples from your backlog to illustrate the importance of decomposition.

2. 2

   Presentation of the Rules

   10 min

   Distribute a set of cards to each participant. Explain that each card represents a proposal for breaking down a large user story. Participants should propose a breakdown for user stories estimated at more than 5 effort points. "Your task is to suggest a breakdown that could reduce the size of these stories."

   Tip — Ensure that each participant fully understands the concept of 'effort points' before starting.

3. 3

   Individual Brainstorming

   15 min

   Each participant works individually to think of ways to break down the user stories. They write their ideas on the cards. "Take this time to consider different ways to decompose these stories into smaller, more manageable elements."

   Tip — Encourage participants to think of various criteria for decomposition, such as functionality, user value, or technical complexity.

4. 4

   Group Sharing

   20 min

   Participants regroup and share their breakdown proposals. Each person presents their ideas and the reasons behind them. "Share your proposals with the group and explain why you believe this breakdown is effective."

   Tip — Facilitate the discussion by asking open-ended questions to encourage debate and idea exchange.

5. 5

   Selection of the Breakdown

   15 min

   The product owner listens to the proposals and selects the breakdown that seems most appropriate, explaining their choice. "As the product owner, I will now choose the breakdown that I believe is most relevant for our backlog."

   Tip — Encourage the product owner to explain their choice in terms of user value and prioritisation.

6. 6

   Conclusion

   10 min

   The facilitator concludes the workshop by summarising the learnings and thanking participants for their engagement. "Thank you all for your active participation. We now have a better understanding of how to break down our user stories for a smoother backlog."

   Tip — Make a connection to the next concrete steps to integrate these breakdowns into the actual backlog.

Variants

• Use real user stories from your backlog to make the workshop more relevant.
• Add a team reflection time before individual brainstorming to stimulate collective creativity.
• Incorporate a participant vote to select the best breakdown before the product owner makes their choice.