Epic bedtime story

There are not many games out there to explain and discuss how distributed teams work and for very good reasons. Teams **should** be co-located.
This simple game is intended for any member of your organisation/teams to understand the challenges related to “distributed scrum”.
This also relate to the roles/skills and how natural instincts affect teams so there is no wrong way to play it.
**I tried it with 4th graders to test it before I brought this to the grownups. Went really well in both cases.
Goal: The goal is to create a children’s book of 10-12 pages within 40 minutes using 2 to 6 teams.

Lego Flow Game

Timing: 60-90 minutes Overview: The Lego Flow Game is a fun exercise to compare and contrast different approaches to processes, with respect to how work flows. The aim of the game is to build Lego Advent Calendar items, with a defined workflow: finding the next advent calendar number (analysis), finding the matching set of lego pieces (supply), creating the lego item (build) and checking the item…

Ball Flow Game

Timing: 1 hour Overview: The Ball Flow Game is a variation of the Ball Point Game, where the aim is for a team to process 20 balls as quickly as possible (as opposed to complete as many in 2 minutes), with the following rules: Participants play as a whole team (everyone must touch each ball) Balls must have air time between people No passing to a…

Means First, Then StatesLes moyens d’abord, les résultats après

This exercise introduces and demonstrates the “Means First, Then States Syndrome” and the negative impact it could have on software projects’ execution and/or outcomes. It also drives a meaningful discussion on what success is to software projects and what factors could lead to it (including an evaluation of the values and principles of the agile manifesto). It further emphasizes the importance of stakeholder theory and…

Three Projects, Three Experiments

Context: This game is similar to multi-tasking game, and can be used to teach concepts like   focusing on people utilization (instead of completing projects early), continuous partial attention,  effect of lack of face to face communication, limiting Work-in-progress, etc. Acknowledgements: This is a variation of how Peter Saddington did his multi-tasking game at Agile 2013 What you need: flip charts (to note down times), stop watch, 6-8…