Introducing Scrum Bowling

[Rob Healy]

I'm new to this group but I'd like to introduce a new game I've invented. I call it Scrum Bowling. It is a team sport with an emphasis on Productivity, Continuous Improvement, T-Shaping, Self-Organisation and, usually, fun. I created it when out bowling in London recently when I realised that bowling is essentially a rapid learning and feedback loop. 

You will need:

1. A bowling alley with two or more lanes
2. At least two teams of 12 players
   
3. One ore more flip charts for estimates
4. Helpers (one for every two teams)

Instructions:

1. Once you know how many people are playing (get them to pay first to ensure commitment) book the lanes.
2. Divide the teams into equal numbers of players (see note on unequal number of players). One neat way to do this is to line everyone up by amount of bowling experience and divide into the number of teams so that each team has some stronger players and some weaker players. This can be done at the alley or before-hand.
3. At the bowling alley, instead of getting each player to register their name enter a placeholder name  such as "P1", "P2" and so on. 
4. Give everyone the instructions:
1. Welcome to Scrum Bowling. This is a team based game  where the goal is to beat the other lanes.
2. Each team member must bowl once per round.
3. Other than the teams are self-organising. The order you bowl at can change each round.
4. Before each round begins each team must estimate how many points you will score.  
5. After each round we will have a short 2 minute retro to decide the strategy for the following round.
6. At the end of the game there are prizes for:
1. Most Accurate Compared to Estimates
2. Most Improved
3. Highest overall Score
7. Beyond that, normal ten-pin bowling rules apply.
5. To start get each team to give an estimate of the number of points that they will score.
6. Allow the round to take place (The Good, The Bad and the Hopeless will become obvious very quickly)
7. Don't let the next round take place until all teams have finished the first round, the actual scores have been calculated (this is usually easy as they are on a screen near the lane) and the next estimates have been given.
8. Repeat for all rounds. Keep each round short and snappy. Encourage acts of coaching and mentoring between players.
9. Tally the total points. Celebrate the awards (these will usually go to at least two teams)
10. Go to the bar and enjoy a great night out!

Really easy. Good fun. Nice team building exercise.

Let me know how you get on trying it.

- Rob

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.

[Mark Levison]

Rob this seems like fun. I'm a little confused, this seems to be an excellent game to focus on estimation - but I don't see how estimation is Scrum.

Please help me see what I have missed.

Cheers

Mark

--
You received this message because you are subscribed to the Google Groups "AgileGames" group.
To unsubscribe from this group and stop receiving emails from it, send an email to agilegames+...@googlegroups.com.
To post to this group, send email to agile...@googlegroups.com.
Visit this group at https://groups.google.com/group/agilegames.
For more options, visit https://groups.google.com/d/optout.

[Rob Healy]

Hi Mark,

Thanks for your reply. It seems more than a little unfair to say the focus is on estimation. For me, the focus is on building continuous improvement and learning in teams with varying abilities in a competitive environment using Transparency, Inspection and Adaption and just a little a bit of fun. 

I haven't tried yet this but I'd suggest that we could remove the estimation part entirely and just award for Most Improved and Highest Score. The #NoEstimates version seems like a little bit less craic as it removes one of the opportunities for the team to speak with each other to establish a target for the round. However, you are welcome to give it a go and let us know how you get on.

Best regards,

- Rob

 

  

Rob Healy

Principal Consultant

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Email: robert...@ammeon.com

Phone: +353 087 751 8592

TeleCon: +353 (01) 906 1889 passcode: 187440#

MeetMe: https://doodle.com/ammeon.robert.healy

Web: www.ammeon.com 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

You received this message because you are subscribed to a topic in the Google Groups "AgileGames" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/agilegames/tZXkxXb3qCk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to agilegames+...@googlegroups.com.

To post to this group, send email to agile...@googlegroups.com.
Visit this group at https://groups.google.com/group/agilegames.
For more options, visit https://groups.google.com/d/optout.

[Mark Levison]

Rob - As a Scrum person, I struggle constantly in engagements/training/coaching with people who believe that Scrum mandates the use of User Stories and Estimates (Planning poker specifically). Both you and I know that isn't true. So when you publish an idea/game where estimates/forecasting are a big feature and call it a way to lean about Scrum, I feel compelled to comment.

Hope the perspective helps

Mark