AGILE GAMES

Don’t Blow It

AGILE GAMES

Don’t Blow It

Timing:

5 minutes plus 15-30 minutes for debriefing

Materials:

2 balloons per 4 people
Water (Optional)

Instructions

The “goal” is for teams (of 3-5 people) to compete to blow up the largest balloon. The team with the largest (unburst & tied) balloon wins

The person blowing up the balloon will be blindfolded and will have to be guided by their team-mates when to blow and when to stop

One person should wear the blindfold and everyone else in their team should stand very close around the blindfolded member

Rules

The blower cannot open their eyes or remove the blindfold

The non-blowing team-mates may not back away from the blower

The balloon must be tied for it to be considered “done”

Learning objectives

1. Operating without trust can be scary

2. Team members having a shared interest (standing close) increases trust

3. If trust is broken (balloon pops) then (i) trust is even harder to re-establish (the willingness of the blindfolded member to go again is reduced) and/or (ii) the team blows a smaller balloon (productivity drops)

Variations

1. A time limit of 60 seconds to blow the biggest balloon

2. The balloon can be filled with a little water

3. Have the non-blowing team-mates hold the blindfold and balloon

4. Run different variations in parallel (one team standing close, one team standing further away for example)

About Tasty Cupcakes

This content was originally published on Tasty Cupcakes, a community-run website founded by Michael McCullough and Don McGreal after they presented a series of games at Agile2008 in Toronto. The site’s tagline was “fuel for invention and learning.” After 15 years at TastyCupcakes.org, the content has found a new permanent home here at Agile Alliance.

The games, techniques, and approaches presented are here to use and explore. All we ask is that you tell others about us and give us some feedback on the games themselves. All of this work is licensed under a Creative Commons Attribution 4.0 International License.

Add to Bookmarks Remove Bookmark
Add to Bookmarks Remove from Bookmarks
Add to Bookmarks Remove from Bookmarks

Got feedback? Join the conversation!

Explore additional Agile Games

Description Organization and prioritization are two distinct activities that can be used to improve the quality of a product backlog. A simple linear list is difficult to prioritize. As well, many stakeholders are forgotten in the rush to deliver cus…
Objectives Learn about the attributes and duties of a role. Verify what your students already know about the subject (complemented by a short lecture). Let your students learn from each other. I've successfully used it with all three Scrum roles: th…
This activity was designed to teach continuous integration concepts and value without resorting to code, a continuous integration server, or any hardware or software.  While the participants will experience some frustration in trying to complete the …
While we've all heard about "pair programming", pairing is not just for programmers. In this activity, participants will use fiction/creative writing to understand the importance and value (and fun) of pairing. Timing Prep: Printing out the ha…

Discover the many benefits of membership

Your membership enables Agile Alliance to offer a wealth of first-rate resources, present renowned international events, support global community groups, and more — all geared toward helping Agile practitioners reach their full potential and deliver innovative, Agile solutions.

Not yet a member? Sign up now

Help support our mission!

Agile Alliance is a global non-profit membership organization founded on the Agile Manifesto and the 12 Principles behind the Manifesto. If you’d like to make a contribution to help us in our mission and to continue our work, you can make a donation today.