Add more details to the instructions for the Lego simulation

Explain a bit more what the objectives of each teams are, adding ideas
and few practical examples of how to conduct the game.

Change-Id: I784067821f151d2b823dac65dc991b73d7be584c

doc/upstream-training/source/20-training-agile-for-contributors.rst

@@ -30,7 +30,7 @@ Using Lego to represent the community
   - PTLs
   - Core team
   - Companies
-  - Free agents
+  - Unaffiliated contributors (free agents)
 
 Your mission, should you choose to accept it
 ============================================
@@ -49,6 +49,8 @@ Choosing roles - Upstream
 - PTL : 1
 - Core : 5
 
+Upstream is responsible for the finished product.
+
 Choosing roles - Companies
 ==========================
 
@@ -59,6 +61,8 @@ Each company has:
 - CEO : 1
 - Team members : 3-5
 
+Companies have to deliver value to their stakeholders.
+
 Choosing roles - Free agent contributors
 ========================================
 
@@ -66,6 +70,8 @@ Choosing roles - Free agent contributors
 - Controversial : 1
 - Agreeable : 2-3
 
+Each individual sets their own objective.
+
 Timing
 ======
 

doc/upstream-training/upstream-details.rst

@@ -266,18 +266,21 @@ understand the metaphors in use. The Lego in the exercise represents the
 code of a software project, in this case OpenStack. The students all take
 on roles that represent various facets of the OpenStack community, including
 upstream roles like Foundation and TCT, and contributors like corporations,
-and individual free agents.
+and unaffiliated individuals animated by unknown motives (free agents).
 
 The group is split into their new 'teams' at this stage. Facilitators can
 choose any way they prefer to do this (selecting teams, or allowing students
 to self-select). The recommended numbers are in the slides, but can be
 changed to suit the number of participants in the room. For a very large
 group, consider separating into two 'communities', which then have to
-fit their streets together (use the metaphor of an API for this) to
-complete the session. Give each person a nametag to wear, with their first
-name and their role written on it. For free agents, don't disclose who
-is distracted, controversial, or agreeable. The community will need to
-work this out on their own.
+fit their streets together to complete the session. Having more
+communities requires an extra level of coordination to reach
+`interoperability` between the results of their work.
+
+Give each person a nametag to wear, with their first name and their
+role written on it. For free agents, don't disclose who is distracted,
+controversial, or agreeable. The community will need to work this out
+on their own.
 
 Contribution Simulation (2 hour)
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@@ -292,11 +295,20 @@ understanding of the project, begin the timer for the first sprint. During
 the five minutes planning time, encourage each group to get together and
 think about their project. If possible, give each group a corner of the room
 and access to a whiteboard or flipchart. For companies, ensure the CEO sets
-a direction, and the team are on board. For upstream, have them think about
-the community standards they want to set. Free agent contributors can get
-straight to work during this phase.
+a direction, and the team is on board. Their responsibility is to
+deliver value to their stakeholders. For upstream, have them think about
+the community standards they want to set: they are responsible for the
+quality of the finished product. For free agent contributors,
+use this time to get them to understand their role in the simulation:
+explain their part as agents of chaos. They can get straight to work
+as soon as they understand their role, no need to wait for the timer
+to go off. The free agents should not be forced to coordinate among
+themselves: there are better results if they find out how hard it is
+to accomplish anything without coordinating with others. In theory,
+the free agents can decide to demolish things, too: try suggesting
+this option to one of them, see what happens.
 
-Suggestions:
+Suggestions of projects to work on:
 
 * Companies: big industrial items like a shopping mall, carpark, energy
   plant, datacenter, hospital.
@@ -308,17 +320,24 @@ Suggestions:
 * Upstream: consider guidelines around consistency in the bricks used, how to
   connect the road and sidewalk between the buildings, the kinds of
   buildings they should request the community to make, and the things they
-  simply will not accept.
+  simply will not accept. Make them understand that they are
+  responsible for the finished product.
 
 Start the timer for building time, and allow everyone to start work. During
 each building phase, have mentors wander around the groups listening in and
-making suggestions, without actually doing any of the work or giving answers.
+making suggestions, without actually doing any of the work or giving
+answers. The role of the mentors is to ask questions to orient the
+conversations among the teams. For example, during the first sprint it
+is common that the CEO and the PTL will face incompatibility of their
+plans. Mentors should ask the teams how to address those issues.
+
 In your interactions with the students, do not be afraid to provoke some
 issues. For example, bring up the idea of an API (a way of connecting the
 buildings to each other) with individual companies, but don't mention it
 to upstream, so that upstream are finally faced with the challenge of
 standardizing the API. You could also, in the second or third sprint,
-encourage one group to call a midcycle to sort the problem out.
+encourage one group to call for a meeting off the sprint cycle to sort
+the problem out.
 
 During the final five minutes of the sprint (review time), ask everyone to
 take their hands off the Lego, and gather around the in-progress street. At