(English) Nexus Zoo (a scaling simulator)
2 Comments
(English) Nexus Zoo (a scaling simulator)
Posted by Don McGreal on juillet 27th, 2016 at 10:51
2 Responses to "(English) Nexus Zoo (a scaling simulator)"
Leave a Reply:
Login
Discuss Comments
- Ivo Peksens on (English) Time-Tree-Fertilizer retro
- Rob Denison on (English) To Plan or Not To Plan
- Mary on The Fast and the Furious (and other Fs) retrospective activity
- John Miller on (English) Core Scrum Game
- Benito on (English) The league of extraordinarily shortsighted agile superleaders retrospective
TastyCupcakes.org is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
Powered by WPNow Wordpress Themes.
Including some info about duration of the game (time schedule?) would be helpfull!
Also, instead of “4. step back and let it happen”, I think it would be more fun and a better learning experience if the facilitator acts more as a Product Owner.
Asking questions (communicating with your client / PO) should be encouraged! When no questions are asked, the Product Owner should reject the results because of additional (implicit) requirements, e.g. “the logo should be more business-like”, “the cheetah should be running in the picture because that’s what cheetahs are known for”.
When asked questions about *what* to build the PO should provide sensible answers. Questions about *how* to build or coordinate should not be answered.
I have done this game with two Sprints. The Sprint defined for 20 minutes: 4 min planning, 9 min work, 3 min review, 4 min retrospectives. As facilitator, I act as the Product Owner (although someone else could as well). For the retro, I ask team representatives to meet to retro integration issues for first half of timebox and then return to their teams to complete team retro.