This is a game I created, which was then used and refined by me and my colleague Laurie Young to help gauge how well everyone involved in a project understand their responsibilites to the project and each other. It lends insight in to the pre-conceptions that people have about how projects should be run, which helps you tackle potential problems early.
It has really helped projects get off to a good start and its good to revisit later on to see how peoples understanding have changed.
Timings: 1hour – 1hour 30mins
Materials: The Team, White Board, Pre-written out index cards, Blank index cards, Pen, some method of sticking cards up (magnets, bluetac etc)
Instructions: Draw a big circle on the whiteboard, inside that draw a smaller but reasonably sized circle in the middle. You should now have something that resembles a ring doughnut. Now draw three equidistant lines from the outer circle to the inner circle as if you are going to divide said doughnut equally between three people.
In the very centre of the doughnut write “Everybody” and then put one of the following in each section of the doughnut: Product Owner (PO), Development Team (DT) and Scrum Master (SM). Finally on somewhere outside the doughnut write “no one”.
Now on the index cards write roles and responsibilities with in the Scrum Framework. These are some of the things I have written down in the past, but its certainly not the exhaustive list:
- Cancelling a Sprint
- Changing the Product Scope
- Conveying The Product Vision
- Prioritises Product Backlog
- Prioritises Sprint Backlog
- Writes User Stories
- Facilitates Meetings
- Facilitates Retrospectives
- Builds the Product Backlog
- Commits to a Sprint Backlog
- Remove Impediments
- Motivates the team
- Protects the team from outside distraction
- Chooses the Amount of Work in a Sprint
- Commits to Completing the Sprint
- Inspects and Adapts to Improve their Performance
- Manages the Team
- Points Out Other People’s Mistakes
- Makes Sure the Product Works
- Accepts a Story as Ready
- Recognises Impediments
- Accepts a Story as ‘Done Done’
- Ensures Something Useful is Built by Launch Date
- Represents the Business/Customers
- Keeps Stakeholders Informed
Now get everyone in the team to arrange the cards on the board. If a responsibility is for one section of the team it lives in its specific area of the doughnut. If two groups share it, it goes on the dividing line between them and “everyone” and “no one” are self-explanatory.
The way that has worked best for me is tackling each card at a time, talking about it and trying to reach a consensus on where the card belongs, but you can equally get all the cards up there and start pulling them off. I find that can get confusing though.
Variations: This can be used for developing broad understanding of Scrum, but also for specific areas that we may be misunderstanding i.e what are our responsibilities for testing?. I also find that asking: “Where do you think this card goes?” reaps different result to asking the question: “Where do you want the card to go?” so I am sure there are other clever questions that can be asked while playing this.
- This is a very good game for setting the expectations within the team and avoiding conflict due to misunderstandings.
- It establishes a level of good communication throughout the team.
- Creates a very focused discussion on what things should be happening on the project overall.
- Can create commitments from everyone early on.
- Helps expose misunderstands that have grown over time.
- Reinforces the idea of the whole team being the committed people on the project (if you are bored of pigs and chickens).
- It helps highlight responsibilities that no one has taken on or thought about.