Below is a handout that was given at the beginning of the day. A second handout was given just after lunch. Together they define an exercise designed to require teams to work out and demonstrate these skills:
- Self organization of teams when given full reign (and full responsibility).
- How to work with what you’re given, even when extremely sparse.
- How to deliver iteratively (MVP).
- How to keep parts of the solution decoupled from one another.
<Handout #1 - Morning session>
Welcome to the BBC - Part I
Welcome to the BBC - The “Bouncy Ball Company”. You have been selected to join the newly formed Super Hot Automation Facilitation Team, SHAFT for short
The focus of this team is to outcompete every other manufacturer by building software that will automate every step in the manufacture of most any sort of ball, starting with the most popular product here in the northeast; the football (American NFL football).
Manufacturing overview reference: http://www.madehow.com/Volume-3/Football.html
For the bill of materials and manufacturing steps, see the link above:
Forms teams, possibly based on the stages of the manufacturing process, and be sure to remain agile. More news later
The first half of the day (pre-lunch) will be devoted to iterating and improving the process with at least three deliveries, each accompanied by a customer review and feedback.
<end Handout #1 - Morning session>
<Handout #2 - Afternoon session>
Welcome to the BBC - Part II
Start manufacturing soccer balls. The requirement is to apply all the learning that went into making footballs to now making soccer balls, maximizing the automation by maximizing parameterization, and minimizing waste of the raw materials.
Manufacturing overview reference: http://www.madehow.com/Volume-5/Soccer-Ball.html
As you may have surmised by now, the real exercise is about teamwork, both within teams and across teams, and rapidly finding out what works for the people who show up.
<end Handout #2 - Afternoon session>
Here’s what happened:
The morning was predictably defined by lots of questions -
- What constitutes “acceptance”?
- How will we divide the work up?”
- How will me track progress?
The answers were much simpler than attendees imagined:
- Ask the customer what is acceptable, and a rank-ordered list of what comes first, second, etc.
- Organization is entirely up to the team(s).
- Deliver working (acceptable) software.
The afternoon session raised the bar on agility at both the testing and implementation levels:
- Similarities: Both balls have an inner bladder, are inflated with a given quantity of air, required a valve to inflate the bladder, and require a stitched-together outer skin of n faces which has to be printed on (e.g. the logo, serial #, etc.)
- Differences: The specification (diameter, width, length, lacing or not, number of outer layer faces, shapes of the faces, number of different face shapes, weight, etc.) varied.
The outcomes I was most pleased with were that 18 peoples who do not work together, all of who met at this monthly workshop …
- collaborated rather than competing,
- natural leaders emerged quickly and at different points during the day,
- everyone participated and remained engaged for the entire day.