### SlideShare for iOS

by Linkedin Corporation

FREE - On the App Store

This is the set of instructions for a game that illustrates how increasing collaboration increases effectiveness.

This is the set of instructions for a game that illustrates how increasing collaboration increases effectiveness.

- Total Views
- 260
- Views on SlideShare
- 239
- Embed Views

- Likes
- 1
- Downloads
- 7
- Comments
- 0

http://confengine.com | 20 |

http://news.google.com | 1 |

Uploaded via SlideShare as Microsoft PowerPoint

© All Rights Reserved

- 1. Collaboration: Power of 13 Simulation This game was created at Agile Games 2014 by – Jamie Gaull Robert Smith Peter Barzdines Bobby Zhakov Paul Boos
- 2. Power of 13 Goal: Work off the the number of cards equal to the number of people within your iteration’s length Mechanics: • We need a ‘Scrum Master’ and ‘Product Owner’ – everyone else is a development team member • Each card is worked off whenever a 13 is rolled on 3 dice (~10% chance per roll) • The product owner will count off the number of cards completed using a deck of cards • The scrum master will use another suit of cards to count down your iteration of 13 work days (3 week Sprints, the other two days are sprint review, retro, and planning = 15 days) • We will mark down what day you meet your goal and the total # of cards worked off
- 3. Power of 13 :: Round 1 This round will simulate developers working alone in their silos/cubes • Each developer is responsible for completing a card from the backlog • Each developer rolls the dice once per day; the scrum master keeps track of the 13 work days using the suit of cards he or she has • If a dice roll has a sum total of exactly ‘13’, they state “my card is DONE.” The product owner turns this card over from his stack. The developer stops work and pats himself on the back. • Record cards completed once all the work days are completed or when everyone says they are ‘DONE’; also record what day the required # of stories was completed.
- 4. Power of 13 :: Round 2 This round will simulate helping others after you complete your work • The team is still responsible for completing at least the a number of cards from the backlog equal to the number of developers • Each developer rolls the dice once per day; the scrum master keeps track of the 13 work days using the suit of cards he or she has • If a dice roll has a sum total of exactly ‘13’, they state “my card is DONE.” The product owner turns this card over from his stack. The developer pats himself on the back; however they may now continue to roll on subsequent days and declare another card done for each ‘13’ they roll – identify who they helped if someone else isn’t completed. • Record cards were completed and what day the required # of stories was completed.
- 5. Power of 13 :: Round 3 • This round simulates collaborative swarming to complete work • The team is still responsible for completing at least the a number of cards from the backlog equal to the number of developers • Each developer rolls the dice once per day; the scrum master keeps track of the 13 work days using the suit of cards he or she has • Once each developer has rolled, they work together to pull as many sums of exactly ‘13’ on 3 dice as possible; each ’13’ identified equals a card worked. The product owner turns these cards over from his stack. • Record cards were completed and what day the required # of stories was completed.
- 6. Collaboration: Power of 13 Simulation Debrief What did you notice happening? What did the dice/rolls represent? How did the effectiveness change in each round? How does or does not this correlate with how real work happens? How did the coordination in the last round feel? What did allowing a person to continue work simulate?

Full NameComment goes here.Bernie Maloney, Agile Coach | Product and Program Management at GreenFieldz 1 month ago