don't miss

Miroverse Challenge: Agile Games 🥳 Postponed to Autumn 2022

Miroverse Challenge: Agile Games 🥳 Postponed to Autumn 2022
Userlevel 7
Badge +1

Hi Miro Heroes,

 

You may know that this April has been all about Agile 💡

 

We’ve had loads of amazing conversations and attended insightful events run by you — our amazing community members 🎉🎊

After some thought and brainstorming with Miro’s Lean- Agile Evangelists group here, we decided that it would also be loads of fun to run an Agile Games templates challenge.

 

What are Agile Games? 🤔

‘Agile Game is a fun activity that helps you learn something about Agile or helps you get your work done.’

@Richard Kasperowski 

 

For inspiration, take a look at some Agile Games templates already available on Miroverse or read some games ideas in this thread.
 

 

For those who need help, @Henrik Ståhl  created a ‘back of the box’ instructions checklist template

 

We look forward to seeing all the amazing Agile games that you create in Miro 😍

 

 

More Challenge Details

 

:calendar:  Timing

Submission period: April 29–June 19

Voting and judging: June 20 - June 27

Winners announced: June 28

 

:ballot_box:  Voting and judging

Miro Team’s Choice will be awarded by our panel of expert judges. Submissions will be judged on their ease of use, layout, and that special fun factor.

People’s Choice will be awarded based on top likes under the comment here in the online community. Make sure to vote for your favourite template by June 5. ☝️

 

:gift:  Prizes for each category 

Miro team’s Choice -  iPad and an Apple Pencil

People’s Choice- AirPods 

Miro swag will be awarded to all other participants who will get published on Miroverse :sunglasses:  

 

How to participate 📌

 

:pencil:  To enter, please add a comment to this thread with the following details:

  • Your full name

  • Role and company

  • Miro board embedded with your template (with view access)

  • Instructions on how to use the template

  • Optional: 1–3 minute video overview of your template

:warning:  Entry requirements

  • Your template must be in English, and have been created and designed using Miro

  • Your template must be newly created or not published on Miroverse earlier

  • All information must belong to you, the board owner (We will reject all submissions containing copyright-protected content on board.)

  • Your template must be submitted to Miroverse before the challenge deadline

  • By participating in the challenge

 

 

Judges: TBA

 

Happy collaborating, and good luck!  :rocket:


13 replies

Userlevel 7
Badge +4

I have a question! 🙋‍♀️

Is it OK for one person to submit more than one template?

Userlevel 7
Badge +1

@Henrik Ståhl it is :)

Userlevel 7
Badge +4
  • Henrik Ståhl.
  • Product Manager, Telia Company.
  • Miro board template password is battleships (sorry about the inconvenience, it’s a company-imposed configuration – our boards can’t be shared publicly without password...)

Instructions

 

Group size:

  • A minimum of 2 players, but preferably more.

Game length:

  • ∼20 minutes.

Goal:

  • Score as many hits as possible.

Rules:

  • Each ship must be placed horizontally or vertically across grid spaces—not diagonally—and the ships can't hang off the grid.
  • Ships can touch each other, but they can't occupy the same grid space.

How to play

  1. Divide the participants into Team A and Team B.
  2. Show each team their respective Battleships sheets. Use the Breakout Frames if you want to make sure no one is cheating. ;)
  3. Both teams are given 2 minutes to plan their ship placement (horizontal or vertical only, not diagonal), a total of 5 ships each.
  4. Team A is given 5 minutes to plan 30 shots up front, marking these on the Enemy Ships section (mark by changing color on the specific table cells or by using emojis). 
  5. When they have finished planning, Team A relay all of their shots to Team B. Team B then reports misses, hits and successfully sunken ships.
  6. Team B will then take 5 minutes to play each of their 30 shots, but this time with realtime feedback from Team A on the misses, hits and sunken ships (the way traditional Battleships is played).
  7. At the end of the game, count the number of hits and sunken ships for each team.

What do we learn?

  • Predictive planning is unreliable.
  • The iterative approach is empirical.
  • Occasionally Team A will win, but it's more due to luck than judgement.
Userlevel 7
Badge +4
  • Henrik Ståhl.
  • Product Manager, Telia Company.
  • Miro board template password is sinkingship.

Instructions

 

Group size:

  • A minimum of 2 players, but preferably more.

Game length:

  • 20-30 minutes.

Goal:

  • Agree on an order of priority for the list of celebrities that will be saved.

Rules:

  • Only one celebrity can be saved at a time, so the list must be in order from 1 to 30.

How to play

  1. A cruise ship with a number of famous people on board has hit an iceberg and is sinking, leaving the celebrities in mortal danger. Inform players that they don’t know how long it will be until the boat has sunk. The good news is that they have a rescue boat and can be heroes by rescuing the celebrities. The bad news is that the rescue boat is small – they can only rescue one person at a time.
  2. Task players to work together as a team and list the celebrities in the order in which they would rescue them (divide large groups into separate ”teams”). Set them a time limit of 10-15 minutes.

What do we learn?

  • Some teams will fail to agree on an order. In this case, everyone dies. The learning point is that, in agile, almost any decision is better than no decision.
  • It often isn’t worth arguing too much about priority 1 vs priority 2.
  • Arguing about priorities 10-15 is relatively pointless; the boat will probably have sunk by then anyway.
  • Once you have rescued person 1, you can get some feedback on your decision and potentially change your mind about who you rescue next.
  • Most teams will decide on a set of criteria for how to decide on their order. Agile setups need this understanding too. Things become easier then.
  • Prioritization is subjective – there is no getting away from that.

Based on Paul Goddard’s and Geoff Watts’s original game, ”Celebrity Prioritisation.”

Userlevel 7
Badge +1

@Henrik Ståhl please don’t forget to submit to Miroverse & send me the RTB files :)

Userlevel 7
Badge +4

@Helena Brandist Thanks for the reminder, will do asap! 🙌

Userlevel 3
Badge

 

Hi all,

 

Wanted to add my Scrumopoloy retrospective template!

 

 

 

  • Dave Westgarth

  • Project Manager @ Attraqt

  • Miro board embedded with your template (above!)

 

Instructions

 

Group size:

  • A minimum of 2 players, but preferably more.

Game length:

  • Limited to a timebox (Suggestion 1 hour.)

Goal:

  • Generate discussions and insights around a previous sprint, phase or iteration.

Rules:

  • Each player rolls initially (Highest roll selects piece and rolls for main game first, lowest selects and plays last)
  • Rolling a double results in a roll again
  • Rolling 3 doubles in a row means you are sent to jail and the next player then rolls

How to play

  1. Each player rolls initially to establish the order of play and piece selection (Highest first, lowest last)
  2. Players then take turns rolling the dice, landing on board squares and tackling the associated actions or prompts for the square they’ve landed on (Use the key for guidance!)
  3. Generate discussion tickets and insights as you make your way around the board capturing them in the Ticket Board
  4. Towards the end of the time box draw the main game to a close and allow the team to vote for the most important tickets created using their monopoly money. Team mebers can “invest” more or less in each ticket depending on how important they feel each ticket is.

What do we learn?

  • We learn about our past performances and how we can improve our team’s quality and effectiveness moving forwards. We also discuss the following topics
    • What went well
    • What can be improved
    • Give kudos to the team
    • What would we wish for
    • What impediments did we remove
    • Experiments we can run
    • Identify next challenges
    • Identify skills or knowledge we want to develop
    • Constraint management
    • Scoring the sprint 1-5
    • Meme/ Gif of the sprint
    • Forfeit to escape jail 😁
Userlevel 7
Badge +4

@DWestgarth Oh wow, it really looks like Monopoly! Nice work! 🤩

My Name is Ulrich (Uli) Mueller
and my Role is Scrum Master at Thalia Books GmbH.

I started with Miro about 2 Month ago and I am new to this community here.


This little Agile Game I invented myself some weeks ago.
I had one test with an agile Open Space Community and I think they had a lot of fun.
It bears no resemblance to any games I know... :-)
Uli Mueller 2022

 

GOAL OF THE GAME:
    •    This game is originally  meant to be an Icebreaker - it's supposed to be fun...
    •    But it also offers an opportunity to reflect on how one usually judges people
    •    In addition, with the optional step 4, you can discuss together in the team how to keep a cross-functional team made up of different characters together.
    •    It also allows you to reflect about how different characters can influence the team.

NUMBER OF PLAYERS: 2-12

TIME: 20 - 60 min. (depends on using the optional parts)

INSTRUCTION:

First Step (about 4 min.):
    •    Go to https://this-person-does-not-exist.com/en.
    •    Keep clicking "Refresh Image" until you find a photo of someone who might be your co-worker.
    •    Use the right mouse button over the image and copy it to the clipboard ("Save image as" dialog)
    •    Go to your Miro board and paste the graphic from the clipboard with ctrl+v (win) or command+v (mac).
    •    Click on the picture in Miro and a small circle will appear at the edge where you can grab and scale the picture. Drag it to a size that fits in the pre-made frame in the workspace below. Move your picture there.

Second Step (about 4 min.):
    •    Give the person in your picture a suitable first and last name. 
    •    Think of a job (colleague) for the person.
    •    Describe the main character traits of the person

Third Step (1-2 min. per person)
    •    Introduce the new person to your Team.

Fourth Step (optional - about 10 - 15 min.):
    •    Copy the picture into the Team Area on the right side and create a cross functional team together.
    •    Which role does which person have?
    •    How do the characters get along?

Fifth Step (optional - about 4 min.):
    •    Google the web for a person with the same name as your virtual person and see if there are any similarities between the two.


 

 

 

 

I uploaded the template in miroverse but unfortunately it seems to be blank…
Don’t know what I did wrong there….

Hope you have fun with my game...

  • Henrik Ståhl.
  • Product Manager, Telia Company.
  • Miro board template password is battleships (sorry about the inconvenience, it’s a company-imposed configuration – our boards can’t be shared publicly without password...)

Instructions

 

Group size:

  • A minimum of 2 players, but preferably more.

Game length:

  • ∼20 minutes.

Goal:

  • Score as many hits as possible.

Rules:

  • Each ship must be placed horizontally or vertically across grid spaces—not diagonally—and the ships can't hang off the grid.
  • Ships can touch each other, but they can't occupy the same grid space.

How to play

  1. Divide the participants into Team A and Team B.
  2. Show each team their respective Battleships sheets. Use the Breakout Frames if you want to make sure no one is cheating. ;)
  3. Both teams are given 2 minutes to plan their ship placement (horizontal or vertical only, not diagonal), a total of 5 ships each.
  4. Team A is given 5 minutes to plan 30 shots up front, marking these on the Enemy Ships section (mark by changing color on the specific table cells or by using emojis). 
  5. When they have finished planning, Team A relay all of their shots to Team B. Team B then reports misses, hits and successfully sunken ships.
  6. Team B will then take 5 minutes to play each of their 30 shots, but this time with realtime feedback from Team A on the misses, hits and sunken ships (the way traditional Battleships is played).
  7. At the end of the game, count the number of hits and sunken ships for each team.

What do we learn?

  • Predictive planning is unreliable.
  • The iterative approach is empirical.
  • Occasionally Team A will win, but it's more due to luck than judgement.

Password is not “battleships”. Its “battleship”

Userlevel 7
Badge +4

@Panda Oops, my bad – sorry!

Userlevel 7
Badge +1

Hi @Henrik Ståhl @DWestgarth @Ulrich Mueller after some deliberation, we decided to postpone this challenge to Autumn due to the low number of submissions. 

You will be able to use the same templates even though they were submitted earlier 😊 

Thank you for understanding!

Userlevel 7
Badge +4

@Helena Brandist Thanks for letting us know! Hopefully there will be more submissions during the autumn. 😊

Reply