Skip to main content

A Game of Experience - Scrum

Presented in OpenSpace at Agile Games 2018 for FUN and Feedback.


This game design is not focused where you might assume - at training people how to "do" Scrum.  The inventors of the game, Tim Snyder and Derek Lane, are focused upon the experience of Scrumming, the group dynamics of being a scrum team.  The game has been designed, and is being refined with the objective of allowing groups of people that know how to do Scrum, to experience some of the Ah-HA moments that mature Scrum team learn after many, laborious retrospectives.  By compressing the group dynamic into a game with the glorious "happen-chance" cards causing random, yet all too common software development events, playing this game for a few hours can give you the deep insights that may only be achieved after months or years of real-life time developing products.  Learning doesn't require time... * Al Shalloway.

One of the core questions Tim & Derek have been pondering:  How does one gain experience with Scrum except by doing Scrum?  Is there a way to simulate the experience - draw analogies - infer similarity - derive guidance and learn quickly - what has taken many Agilist decades of in the trenches hard labor?

Scrum - The Collaborative Board Game  
Copyright (c) 2016-2108 by Tim Snyder & Derek Lane.

Thanks to the Agile Gamers that joined the session, and the feedback.  We had time for one sprint of game play after intro and instruction and received 20+ wonderful questions and suggestions for improvement.  If you have ever designed a game and used it in the wild... you will know just how valuable play-testing truly is to designers.

 

See Also:

* Al Shalloway's comment about Learning:
There is no question that to truly understand something you have to do it. But it doesn't mean it has to take a long time. As one of my mentors used to say "it's not getting it that takes the time, it's the not getting it that takes the time."

Post a Comment

Most Popular on Agile Complexification Inverter

Exercise:: Definition of Ready & Done

Assuming you are on a Scrum/Agile software development team, then one of the first 'working agreements' you have created with your team is a 'Definition of Done' - right?



Oh - you don't have a definition of what aspects a user story that is done will exhibit. Well then, you need to create a list of attributes of a done story. One way to do this would be to Google 'definition of done' ... here let me do that for you: http://tinyurl.com/3br9o6n. Then you could just use someone else's definition - there DONE!

But that would be cheating -- right? It is not the artifact - the list of done criteria, that is important for your team - it is the act of doing it for themselves, it is that shared understanding of having a debate over some of the gray areas that create a true working agreement. If some of the team believes that a story being done means that there can be no bugs found in the code - but some believe that there can be some minor issues - well, …

David's notes on "Drive"

- "The Surprising Truth about what Motivates Us" by Dan Pink.

Amazon book order
What I notice first and really like is the subtle implication in the shadow of the "i" in Drive is a person taking one step in a running motion.  This brings to mind the old saying - "there is no I in TEAM".  There is however a ME in TEAM, and there is an I in DRIVE.  And when one talks about motivating a team or an individual - it all starts with - what's in it for me.

Introduction

Pink starts with an early experiment with monkeys on problem solving.  Seems the monkeys were much better problem solver's than the scientist thought they should be.  This 1949 experiment is explained as the early understanding of motivation.  At the time there were two main drivers of motivation:  biological & external influences.  Harry F. Harlow defines the third drive in a novel theory:  "The performance of the task provided intrinsic reward" (p 3).  This is Dan Pink's M…

Refactoring - examples from the book

Martin Fowler's book Refactoring:  Improving the Design of Existing Code has a simple example of a movie rental domain model, which he refactors from a less than ideal object-oriented design to a more robust OO design. Included in this Refactoring_FirstExample.zip Zip file are the Java source code files of the Movie, Rental, and Customer classes. Along with a JUnit CustomerTest class. Using these example source files you too can follow along with the refactoring that Fowler presents in the first few chapters of his book.


Team Performance Model - by Drexler and Sibbet

Many of you have all heard of the Tuckman model of team dynamics (Forming, Storming, Norming, Performing).  It was created in 1966 and has become the most popular model for describing team behavior.  Is it time to level up in your mental model of team dynamics?  Are you ready for a richer more functional model?



Introducing the Team Performance Model by Drexler and Sibbet



Orientation - Why am I here?
"Orientation is about understanding the purpose of a team and assessing what it will mean to be a member.  you need to understand the reason the team exist, what will be expected of you and how you will benefit from membership.  In a new team, these are individual concerns, because the group is only potentially a team.  that is why these concerns are illustrated as occurring in your imagination at an intuitive level.  As a team leader it is important to provide time and space for people to answer these internal questions themselves."

Keys to when Orientation challenges are resolve…

Elements of an Effective Scrum Task Board

What are the individual elements that make a Scrum task board effective for the team and the leadership of the team?  There are a few basic elements that are quite obvious when you have seen a few good Scrum boards... but there are some other elements that appear to elude even the most servant of leaders of Scrum teams.









In general I'm referring to a physical Scrum board.  Although software applications will replicated may of the elements of a good Scrum board there will be affordances that are not easily replicated.  And software applications offer features not easily implemented in the physical domain also.





Scrum Info Radiator Checklist (PDF) Basic Elements
Board Framework - columns and rows laid out in bold colors (blue tape works well)
Attributes:  space for the total number of stickies that will need to belong in each cell of the matrix;  lines that are not easy eroded, but are also easy to replace;  see Orientation.

Columns (or Rows) - labeled
    Stories
    To Do
    Work In P…