5-10 team members One 6 sided die per team member One deck of cards Several big sheets of sticky note paper Regular size sticky note pad
Remove all the aces, twos, threes, fives and eights from the deck. Set these cards aside. This is your "backlog." (note, this means the backlog is 76 story points)
Assign a scrum master. The rest of the team are developers.
- Shuffle your backlog.
- Lay the cards out in order, this is your "ordered backlog."
- Create a burndown chart
- Create a Kanban style board (backlog, in progress, completed)
- Take cards off the top of the ordered backlog. Only take as many cards as you think you can accomplish in this first two week sprint. Each card is written as a sticky note in the "current" column.
- Each developer takes a card from the backlog as their first story.
- Put the sticky note in the in progress column.
There are 10 days in the sprint. For each day,
- Each developer rolls their die. If it's even, they completed one story point. If it's odd, they completed zero story points. If you roll a six, you get two story points.
- Have a daily stand up meeting. Each developer shares the amount of story points they completed.
- Note the number of story points on the sticky note attached to the user story.
- When a story is complete, move it to the complete column.
- If you roll a five, you introduce a bug - add a two point story to the backlog.
The end of the sprint counts the number of stories you completed. Incomplete stories stay in the backlog.
- Complete the setup step from Round 2 & Plan your first sprint.
For each sprint day, you now have more options,
- You can work with TDD. If you write tests first, the story you're working on is now n + 1 story points, but you get to re-roll on a five.
- Option to break up 8 point stories into smaller ones.
- If you don't write tests first, your story is the same number of story points, but if you roll a five or six, you add a bug.
- Bugs are 2 point sticky notes added to the backlog.
Everything else works the same.
- Same setup as above.
For each sprint day,
- You can now pair with another developer. You'll roll your dice together. If either of you rolls a positive, it's worth a point.
- If either pair roles a five, they get the TDD reroll without the extra story point.
- If you both roll the same number, you get two story points of productivity.
- You get TDD rules without extra story point.
After each sprint, the organizer draws a card from a deck. If the card is a face card, draw more cards until you get to a non-face card. That card value is added to all backlogs.
After each sprint, the scrum master compiles / updates the burndown chart and reestimates the delivery date.
TODO / Feedback add burn down to slides can we do "heroics" re-roll the dice, but then you roll again - if you roll an odd, you lose the next day. add slides with demo die rolls slide for the story sticky schema. visual / color code for the points add bigger sticky for retro - what went well, what didn't. 76 points is too much for 6 person team. display the data from each round. track the velocity over time so they can see how it normalizes. better instructions for the burndown chart? compute the burndown in excel from each team. do the big sprint EOS report as a group. Add random product manager points from the beginning. Breeze'd through the point commitments. make sure the priority is still followed. Emphasizes TDD & Pairing, but not grooming or other things.
Questions Is it fun? yes. engaging. Sree - this would work in India, better than a recorded session.
