AGILE GAMES

Do/Don’t/Is/Isn’t

AGILE GAMES

Do/Don’t/Is/Isn’t

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: the Development Team, the Product Owner, and the ScrumMaster, but you can do it with roles from any framework or methodology.

Timing

Highly depends on the number of participants and on the format adopted.

Materials

Post-its, pens, and a whiteboard.

Number of Participants

As many as you like. Not less than two, for sure, and I’d recommend doing it with at least four.

Instructions

There are several ways to do this. Here I’ll describe one, and you can see more in the “Variations” section.

Split the whiteboard in a square with four quadrants, with enough room to stick a lot of post-its on each.

DO/DON’T

  1. Do a short lecture on the expected duties of the role in question (10-minutes top);
  2. On the top left quadrant, write “DO” and on the top right quadrant, write “DON’T”;
  3. Ask the participants to write on post-its what a person should and shouldn’t do while performing this role (one per post-it), and stick at the appropriate quadrant. I usually ask each three post-its for the quadrant “DO” and three post-its for the quadrant “DON’T”. And I usually give two or three minutes for that. But, you know, try it, inspect and adapt;
  4. Ask for one volunteer to go to the board, grab one Post-it from the quadrant “DO”, turn to the class, and say: “The <role name> should” and the Post-it contents. Important: it does not have to be a post-it he/she wrote on;
  5. Ask for a new volunteer to grab one Post-it from the quadrant “DON’T” and say: “The <role name> shouldn’t” and the Post-it contents. Again, it does not have to be a post-it he/she wrote on.
  6. Ask for as many volunteers as you feel necessary to repeat that. If you prefer, each volunteer may read more than one Post-it, and from both quadrants. It is interesting to change volunteers, so you promote movement and participation.

IS/ISN’T

  1. Do a short lecture on the expected attributes of the role in question (10 minutes top);
  2. On the bottom left quadrant, write “IS” and on the bottom right quadrant, write “ISN’T”;
  3. Ask the participants to write on post-its what a person should and shouldn’t be while performing this role (one per post-it), and stick at the appropriate quadrant. I usually ask each three post-its for the quadrant “IS” and three post-its for the quadrant “ISN’T”. And I usually give two or three minutes for that. But, you know, try it, inspect and adapt;
  4. Ask for one volunteer to go to the board, grab one post-it from the quadrant “IS”, turn to the class and say: “The <role name> should be” and the post-it contents. Important: it does not have to be a post-it he/she wrote on;
  5. Ask for a new volunteer to grab one Post-it from the quadrant “ISN’T” and say: “The <role name> shouldn’t be” and the Post-it contents. Again, it does not have to be a post-it he/she wrote on;
  6. Ask for as many volunteers as you feel necessary to repeat that. If you prefer, each volunteer may read more than one post-it, and from both quadrants. It is interesting to change volunteers, so you promote movement and participation.

Key Points

This is designed so that DOs and DONTs complement each other (by opposition). And then ISs and ISNTs, besides complementing each other (by the opposition), complement the DOs and DONTs by making participants think about what attributes are needed and what is undesirable to fulfill such duties.

If one or more of the points raised by the students is too wrong, you can make comments on it (perhaps, by asking questions) or ask if and why others agree or disagree.

Variations

  1. You may use it without the lecture, to make your students check what they already know about the subject;
  2. You may also do the lecture after the exercise, and ask the students to verify what they would change on the board;
  3. You may do the DO/DON’T and the IS/ISN’T at the same time if you are short in time (maybe by splitting the board into only two parts: DO/IS and DON’T/ISN’T). However, the students take more benefit from doing it separately.

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…
Timing: 5 minutes plus 15-30 minutes for debriefing Materials: 2 balloons per 4 people Water (Optional) Instructions The "goal" is for teams (of 3-5 people) to compete to blow up the largest balloon. The team with the largest (unburst & tied) bal…
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

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.