Timing: This game is normally done in a forty-five minute time block: 5 minutes upfront for instructions, 10 minutes for the game, 5-10 minutes for the team reflection and 20 minutes for the debrief. Overview: The Scrumheads game is a quick game to practice the Daily Scrum activity in a safe to fail environment where constraints have been setup to result in a challenging Daily Scrum to…
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.
This game is perfect to express the duties of a Product Owner, not only for those that are running that role, but also for any other that works with scrum (Developers, Stakeholders, Managers, etc.). The idea is to focus on what the PO must do for the success of the project.
Visit the execution results in the Open Space UY 2014!
<a href="”> Read More…
This exercise can be used as a retrospective technique (in addition to other popular techniques as the Start-stop-continue retrospective, Starfish retrospective, Speed boat retrospective, etc.). I called it the Sandwich retrospective as it covers three different “slices of ingredients” which I believe are essential for self-reflection. These (in “sandwich terms”) are: The issues (the “hunger”) we face in our organization, project, release, sprint, etc. (the…
A quick game to facilitate discussion about the manifesto. I like teams to understand this is about values & principles before we start diving into methodologies.