Here’s an training activity I came up with a few years ago that I love to do when I want attendees to research a topic on their own. It is great when there are two opposing sides to the topic, and you want attendees to research both sides. If there aren’t two sides, you can often create them ;)
I would not say that I invented it, because it is really simple, and I would not be too surprised if other trainers / coaches did similar things.
You will need:
- A flip chart or whiteboard and markers
- Small index cards
- Pens and/or pencils
- Sticky tape
- 1 - 1.5 hours for two groups, 1.5 - 2 hours for four groups.
So, there’s a topic that has two sides, e.g.
- Star Wars or Star Trek
- Is TDD more or less effective than not doing it?
- Feature branching or mainline development
You want your attendees to research arguments for both sides, and you want them to do thorough research.
Suppose there are 9 attendees and the topic is Star Wars or Star Trek. The times for the four phases below are, in my experience, the bare minimum. 50% more time is better.
Connections (1-2 minutes)
- Write the topic or question on a flip-chart page.
- Ask attendees to (secretly) write down their own opinion on a small index card (now everyone from our hypothetical group writes down either “Star Wars” or “Star Trek”)
Concepts (10 minutes)
- Quickly explain both sides (for people who know neither “Star Wars” nor “Star Trek”)
- Create Groups
- Explain the rules of the game
Randomly divide your attendees into two or four groups. It must be an even number because the groups will play against each other. And with more than four groups, the game takes very long.
To divide them into groups, I use small index cards. For our 9 attendees, I create 5 cards with “Star Wars” on them and 5 cards with “Star Trek”. I shuffle those cards and let attendees draw a card. Now we have two groups, one with four people and one with five.
Then I explain the rules:
“Do an internet research together. You must find arguments that defend your side, and also counter-arguments against any argument that your opposing group might find.”
“Later, you will play a game against each other. Team ‘Star Wars’ will ‘play’ an argument. If the other team has a good counter-argument, they get no point, if the other team does not have one, they get a point. Then team ‘Start Trek’ will ‘play’ an argument.”
“We will play 4 rounds like that, so every team can get up to four points.”
“Write every one of your arguments on a small index card. Those cards will be your card deck. You need at least 4 arguments for your side, and as many counter-arguments for the other side as you can find.”
“But don’t just write down your own opinions. You must be able to back every argument or counter argument with something you found in a book or online (a research paper, blog post or even just a tweet).”
Concrete Practice (45 minutes)
- Research: 35 minutes
- Prepare flip chart
- Game: 10 minutes
The two or four teams now do the research and create the card deck. Help them by making sure they first make a plan and distribute the work (you don’t want everyone on the team to read the same blog post).
Remind them to research arguments for their own side first and to create 4-8 cards they can ‘play’. Also remind them to spend slightly more time researching arguments for the opposite side and researching counter-arguments to those arguments.
While the group creates their card deck, prepare the flip chart for the game. Create four rows for the four rounds and some space to write down the results.
Then play the game as described above. I let the team that ‘plays’ an argument stick their card to the colored square, the team that must come up with a counterargument post the card next to it.
Those cards are gone now, the teams cannot put them back into their card decks!
When one team plays an argument and the other team has a counter-argument, someone has to decide whether this is a “good enough” counter argument or whether the playing team should get the point.
When the playing team gets the point, write a 1 next to their half in the current row, otherwise write a zero.
First, see if the two teams can sort it out by them selves. If they can’t (which will most probably happen), you need a referee. When there are four groups, let the other two groups (that are not currently playing) vote.
Otherwise, you must be the referee yourself. (I always struggle whether I should be very strict or generous when accepting counter-arguments. In the game where I took the pictures, I was very strict, which meant that I discarded all counter-arguments for technical reasons: They were good counter arguments, but not exactly for the argument played.)
Conclusions / Debriefing (5 minutes)
- Ask attendees what side they picked before the game, and why.
- Ask attendees whether they changed their mind, and why.
This blog post is part of a new series about technical agile coaching. Read all posts of this series here: