AGILE GAMES

The Scrum Workflow

AGILE GAMES

The Scrum Workflow

This is a useful exercise to conduct in a classroom or together with your Scrum team. It creates alignment around the purpose of each event in Scrum and the roles that participate in each event. It’s great to spark a conversation and make sure everyone understands the foundations of Scrum.

Timing: 30 minutes. This is the expected time to run the game, including prep and debriefing: 10 minutes for participants to fill out the blank worksheet, and 20 minutes for debriefing.

Materials

Each person on the team or at the table needs the following materials:

  • A pen, pencil, or fine Sharpie to write
  • A printed copy of the Scrum workflow (no labels) and of the keywords page

This worksheet presents the Scrum workflow as defined by the official Scrum Guide. It is composed of 5 events (Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Retrospective) plus the Refinement Activities. It also shows the roles (Product Owner, Scrum Master, and Development Team) that participate to each event, and the artifacts (Product Backlog, Sprint Backlog, Sprint Goal, and Product Increment) produced by the Scrum Team throughout the process.

The Scrum workflow can be downloaded here: https://www.5dvision.com/docs/scrum-workflow/

Exercise: Learn the Scrum workflow

The second part of this worksheet is an exercise that helps teams learn the core elements of the Scrum workflow in a simple and fun way. The exercise is composed of two pages:

  1. The Scrum workflow without labels. The diagram shows all events, roles, and artifacts, but no one has a label indicating its name. It’s the job of students to identify the right name for each component.
  2. The list of keywords to use to fill in the previous page. This is a reference page that shows all keywords to identify the events, roles, and artifacts of the Scrum workflow, and give them a name.

How to run the exercise

Participants can do this exercise “solo”, in pairs, or together with their team.

Explain the visual difference between “Events” (gray boxes on the diagram), “Roles” (two lines), and “Artifacts” (one line). And share the list of keywords.

Then ask the participants to fill in the Scrum workflow with the names of the events, roles, and artifacts using the list of keywords provided. Give them 10 minutes to do so.

At the end of the exercise, review the Scrum workflow to provide the correct answers. You can share the printed copy with all the labels, or you can have a copy affixed on the wall and you could go through each component answering any questions the participants may have.

Hint: the solutions are provided on the first page. When in doubt, refer to that page, or consult the Scrum Guide.

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 TastyCupcakes.org, 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

Spring Fund Drive

Help support our mission!

Agile Alliance is a global non-profit membership organization founded on the Agile Manifesto and the 12 Principles behind the Manifesto. If you’d like to make a contribution to help us in our mission and to continue our work, you can make a donation today.