Skip to main content

Golden Gates Paper Bridge - Group Initiative

The Golden Gates Paper Bridge Group Initiative

This group initiative is from the UNC-Charlotte's Venture Group Initiatives Manual.

I've used this initiative to discuss team work, leadership, followership, understanding the client and may other issues that arise during the debriefing.

In one training at SolutionsIQ the teams were given the requirements (build a bridge of 12" span - but when the customer acceptance was done the boat that had to pass under the bridge had towers and antenna that exceeded the specification height.  The teams had to negotiate with the Product Owner on the physical acceptance test - a toy boat passing under the bridge.

One team created their own "Unit-Test" - the box.


Golden Gates 

(Facilitator Info)

Materials:
60 sheets of paper per group, paper clips per group, approximately 60 feet of string, tape for the string, copies of rules (next page) for each group, a ruler, flip chart for debrief.

Set up:
•  Lay down string in two parallel lines 3 feet apart.
•  Count out the paper and paper clips for each subgroup.
•  Separate the practice materials: 5 sheets of paper and 5 clips.

Brief:
•    Divide group into sub-groups of approximately 5 people.
•    Hand out the instructions and read though them with group; allow clarifying questions. •    After 14 minutes, remind the group they need to choose a leader and have that person report the plan to the comptroller in one minute (as per instruction sheet). Comptroller (facilitator) informs the leaders that they have been hired by a new company (they must switch groups). Their task is to ensure that their company (the new one now) builds the best, most cost effective bridge possible. As per instructions they have 5 minutes to finalize plans.
•    After 5 minutes: it is time for construction; each group gets a space at the river. Start stopwatch.
•    When a group is done building they inform you and you tell them how much time has elapsed on the stopwatch. From that number they can calculate their costs. You need to keep track of the 1 minute the bridge needs to stay standing, as well as call out times for other groups as they finish.
•    Once all groups are finished, they should calculate their costs and profit margins. Have each group announce their profit- you then announce the winner.


Common Debrief Question Focused on Leadership:
•    It is helpful to let each subgroup do their own mini-processing with suggested questions.
•    In your small groups, please answer the following questions:
     How was the original leader chosen?
     What criteria were used?
     What effect did the new leader have on the group?
     What are the characteristics of effective leadership?
•    Come back together in large group and have sub-groups share their thoughts.

--- page break ---


GOLDEN GATES

Contractor Guidelines

Your bridge-building company has been contracted to build a paper bridge over the 'river' which has been marked out in the middle of the room. The only materials you may use in this enterprise are the paper clips and scrap paper provided. You will be given a planning/ practice phase before construction begins.

The bridge must be:
•    capable of standing for 1 minute without any extra support (other than provided materials
•    at least 30 cm (12") above the river at its central point

Finances:

Your group will be paid $10,000.00 for a bridge built according to this briefing. From this you should deduct construction costs as follows:
•    $100 for every sheet of paper used (paper clips are free)
•    $2,000 for every support/stanchion which is built in the river
•    $100 for every 10 seconds (or part of 10 seconds) it takes you to build the bridge
•    Your profit is $10,000.00 minus your construction costs.

Time Frame:

     Phase I = Planning and Practice (15 minutes)
     Phase II = Group leader presents plans to comptroller
     Phase III = Final planning (5 minutes)
     Phase IV = Timed construction of bridge

Considerations:
•    During the initial planning phase you will be given only 10 sheets of paper and 5 paper clips with which to practice.
•    At the end of the initial planning phase, you must select a group leader who will present your plans (including projected costs) to the comptroller for approval.
•    You will be given a final 5 minutes planning before the construction phase begins.
•    During the construction phase each group may use up to 50 sheets of paper and up to 20 paper clips.
•    The 'river' is one meter wide
•    The group who makes the greatest profit, will be awarded the contract.

# Remember, you need to build a bridge quickly while using as little paper and as few supports as possible; and it must stand freely for one continuous minute.
1 comment

Most Popular on Agile Complexification Inverter

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…

What is your Engagement Model?

What must an Agile Transformation initiative have to be reasonably assured of success?

We "change agents" or Agilist, or Organizational Development peeps, or Trouble Makers, or Agile Coaches have been at this for nearly two decades now... one would think we have some idea of the prerequisites for one of these Transformations to actually occur.  Wonder if eight Agile Coaches in a group could come up with ONE list of necessary and sufficient conditions - an interesting experiment.  Will that list contain an "engagement model"?  I venture to assert that it will not.  When asked very few Agile Coaches, thought leaders, and change agents mention much about employee engagement in their plans, models, and "frameworks".  Stop and ask yourselves ... why?

Now good Organizational Development peeps know this is crucial, so I purposely omitted them from that list to query.

One, central very important aspect of your Agile Transformation will be your Engagement model.  

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, …

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.


Metrics for a Scrum Team (examples)

What metrics do you collect to analyze your scrum team?

We live in a world of data and information.  Some people have a mindset that numbers will diagnose all problems – “just show me the data.”  Therefore many directors and senior managers wish to see some list of metrics that should indicate the productivity and efficiency of the Scrum team.  I personally believe this is something that can be felt, that human intuition is much better in this decision realm than the data that can be collected.  However, one would have to actually spend time and carefully observe the team in action to get this powerful connection to the energy in a high-performing team space.  Few leaders are willing to take this time, they delegate this information synthesis task to managers via the typical report/dashboard request.  Therefore we are asked to collect data, to condense this data into information, all while ignoring the intangible obvious signals (read Honest Signals by Sandy Pentland of MIT).
What if …