anchor.diff:  
   Selection of work is indicated by moving selected backlog into the "doing" column. This is considered to be estimation. Sticky notes moved into the "doing" column must be completed by the sprint end.
   
  -== Phase 1: Workcells w/expeditor
  -
   In this model, the team is more or less anonymous to the project manager and operates on a "first come, first served" basis.
   
   The project manager decides what is feasible to build.
  
positive.code: image::sampleCity.jpg[]
  
  == Initial backlog
  * Infrastructure (illustrated on two large Post-it sheets on a central table)
  ** Streets
  ** Bus stops
  ** Intersection(s) (can be drawn)
  
negative.code: Have people look up and down to see the silo, and back and forth to see the feature.
  
  == Phase 3: Isolated product team
  Learning objective: Product teams can collaborate in a different way.
  
  Each product team takes 10 minutes to reform. Remind them that within their team, they still need clear roles. Within each team identify:
  
  * Product owners (1 only)
  * Sourcers
  * Assemblers
  * Integrators
  
  Project managers need to be something other than feature managers, just to mix things up.
  
  The roles are suggestions but not enforced.
  
  3 x 10 minute sprints.
  
  In sprint 2: Complication emerges: an operational concern that no red bricks be used. All structures must be retrofit. No new red bricks can be used.
  
  == Phase 4: Product team with guilds
  The roles meet across teams as guilds. Business rules are promoted by guild.
  
  Each team convenes and selects the work to perform. Then the guild briefly meets for the new rules.
  
  Sprint 1 guild rules:
  
  * Feature owners: Need to coordinate work with other feature owners
  * Sourcing: New rules on sourcing - no red OR black
  * Assembly: New rule: yellow and blue cannot be used in the same wall (no retrofits needed)
  * Integration: Wires can only be attached to blue parts
  
  Sprint 2 & 3 guild rules:
  
  