Timing: 

20 minutes to prepare plus 30 minutes for Standard version, or 75 to 90 minutes for Extended Version

Overview:

Small teams collaborate to order a backlog with a specific business goal in mind. Once the team has produced their backlog, they review the output of another team and discuss the differences. Everyone participates and discussion plays a key part in the game. Participant’s eyes are often opened to the complexity of backlog prioritisation. The game has been designed for all staff, not just Product Owners. The Extended Version of the game ramps up the challenge. It is aimed at Product Owners, yet suitable for anyone with a little more time to spare

Learning Points:

  • Experience the challenges of prioritising and ordering a backlog.
  • Understand how an agile team can help their Product Owner by making the backlog items easier to compare.
  • The Extended Version also adds the experience of how business goals impact your approach to prioritisation.
Example of resulting backlog:

Link to Game: Instructions (PDF)

5 thoughts on “Weekend Escape an agile backlog management game

  1. I plan on using this game in an upcoming class and just need to get some more details instruction on how to communicate and the task for the students. I understand the objective for the students as they prioritize the user stories from the Time travelers perspective, but just remind me what is the Spike as the Agile team. Is this a question the Agile teams need to gain further insights around the User Stories?

    How are the Spike suppose to be prioritized along with the Stories?

  2. Oh, this looks promising!
    Might be just what I need for a PO coaching session.
    If I do end up using it, I’ll let you know how it worked out 🙂
    Thanks for sharing!

  3. Fabio, that is great to hear, thank you for the feedback. If you have any suggestions for additional questions/topics of discussion or other tweaks please let me know.

    Cheers,

    Andrew Rusling

Leave a Reply

Your email address will not be published. Required fields are marked *