Sprint Simulation – Scrum Practice Game


Sprint Simulation – Scrum Practice Game

A simple, interactive, and collaborative game to experience at a high level the ceremonies and common practices of Scrum through simulating a sprint.

This game has been used as one part of a longer session focused on learning about Scrum. Prior to playing this game, the team had read the Scrum Guide, been given an overview of Scrum methodology, and been exposed through various other activities to the Scrum roles and Scrum ceremonies. This game is used to experiment with how to put what they’ve learned into practice!

Timing30 – 45 minutes


A public Trello board with column headers pre-defined – “Backlog”, “Sprint Plan/ To-Do”, “In Progress”, “Done”

Note: You could instead use a wall to create a physical board in the room and the team can populate with sticky notes if all participants are in-person and if you prefer this approach to a digital board.


  1. Have the team decide who will play each of the Scrum roles for the game – Product Owner, Scrum Master, Delivery Team, Stakeholder/s
  2. Backlog Refinement
    • The goal is for everyone to work together to quickly create a backlog
    • The facilitator asks – What are the potential user stories for someone who needs to get themselves ready for work in the morning?
    • These items get added as cards in the “Backlog” on the Trello
    • The team asked to size each item (S, M, L or Fibonacci) and add that to the card as well
  3. Sprint Planning
    • Identify the Sprint Goal: Work from home day
    • Have the team pull in the stories that would meet that sprint goal into their “Sprint Plan/ To-Do” on the Trello
  4. Sprint
    The team assigns themselves to items, acts out the items they assign to themselves (like charades), and moves the cards across the board
  5. Sprint Review
    • Product Owner shares an overview of what the team has completed to the Stakeholder/s
    • The team has the option to demo what they’ve done
  6. Sprint Retrospective
    The team, SM & PO all brainstorm a couple of things that went well & what they want to do differently next time
  7. Sprint Planning
    • Identify the Sprint 2 Goal: Go to the office for work & have an important presentation
    • Have the team pull in the stories that would meet that sprint goal into their “Sprint Plan/ To-Do” on the Trello
  8. Debrief

Learning Points

  1. Which parts were easy/ hard to remember from what we learned prior to the game?
  2. What came to you easily? What did you find difficult?
  3. How did the sprint goal help focus the team & impact what stories get pulled into the sprint?
  4. How will this relate to our day-to-day?
  5. What is something you’ll remember and apply in the future?

About Tasty Cupcakes

This content was originally published on Tasty Cupcakes, a community-run website founded by Michael McCullough and Don McGreal after they presented a series of games at Agile2008 in Toronto. The site’s tagline was “fuel for invention and learning.” After 15 years at, the content has found a new permanent home here at Agile Alliance.

The games, techniques, and approaches presented are here to use and explore. All we ask is that you tell others about us and give us some feedback on the games themselves. All of this work is licensed under a Creative Commons Attribution 4.0 International License.

Add to Bookmarks Remove Bookmark
Add to Bookmarks Remove from Bookmarks
Add to Bookmarks Remove from Bookmarks

Got feedback? Join the conversation!

Explore additional Agile Games

Description Organization and prioritization are two distinct activities that can be used to improve the quality of a product backlog. A simple linear list is difficult to prioritize. As well, many stakeholders are forgotten in the rush to deliver cus…
Objectives Learn about the attributes and duties of a role. Verify what your students already know about the subject (complemented by a short lecture). Let your students learn from each other. I've successfully used it with all three Scrum roles: th…
This activity was designed to teach continuous integration concepts and value without resorting to code, a continuous integration server, or any hardware or software.  While the participants will experience some frustration in trying to complete the …
While we've all heard about "pair programming", pairing is not just for programmers. In this activity, participants will use fiction/creative writing to understand the importance and value (and fun) of pairing. Timing Prep: Printing out the ha…

Discover the many benefits of membership

Your membership enables Agile Alliance to offer a wealth of first-rate resources, present renowned international events, support global community groups, and more — all geared toward helping Agile practitioners reach their full potential and deliver innovative, Agile solutions.

Not yet a member? Sign up now