Scrum Master and Team Training @ Nokia (part 1)
Hi all, as agreed with our classes we decided to initiate a series of posts communicating the highlights of our trainings. In particular we constantly evolve the way we teach Scrum, and we make a lot of effort to make people live the best possible experience in only two days of training.
After some years doing training, we came to the point where we really needed to find something that was good enough to put all together in a reasonable time, the theory of Scrum. Well after some reading over the internet and some inspecting & adapting, we came out building the Scrum LEGO City Game... well it is literally a building experience :-)
Basically the need is to experience all the most important moments of the Scrum process through practical experience, not only using "partial" coverage games like: balls-point game, boss-worker game, impediment game, dysfunctional scrum game... but really trying to build a product. Well we also want to generate the urgency of having to deliver something which will go "online" so that the team is committed and proud to achieve the result.
The Scrum LEGO City Game is about building a nice city with LEGO bricks - not a new idea till here - and doing it using as much as possible what learned during the Scrum Training. To create the sense of urgency, agile42 presents the "Product Vision" as to prove to the world that it is possible to build a LEGO city in only 20min. of working time, and the outcome of the work will be photographed and posted on out blog, where everyone can see it and comment it. The city has to be attractive and inviting, and has to look as much real as possible, and in order to make cities comparable there are some constraints...
Prepare a Backlog with some Requirements and User Stories where you describe elements of the city you want to see, and you define some clear Acceptance Criteria and why not, you leave some room for being really creative.
|The Product Owner introduces the Vision and presents the Product Backlog to the Team, giving the overall idea and declaring that his intent for a whole release (20 min.) is to get some important requirement solved. The team can make some questions as far as the time allows it: timebox 5 min.|
|Sprint Planning Meeting 1: The Team estimates the Backlog using Planning Poker, and at the end gives an initial commitment to the Product Owner: timebox 5 min.|
|Sprint Planning Meeting 2: The Team with the Scrum Master, breaks down the Stories into actionable tasks and put them on the whiteboard, assigning the name of the people who will do the job: timebox 2 min.|
|Sprint: the team builds the stories, using LEGO, and track the progress with the help of the Scrum Master on the whiteboard (a burndown chart will also be nice, but 5 min of Sprint are really hectic): timebox 5 min.|
|Sprint Review Meeting: The Team invites the Product Owner to present the achievement of the Sprint, and contemplate the Results together. The Product Owner accepts or rejects the works and together with the team discusses improvements: timebox 5 min.|
|Team Retrospective: The Team improves the process and write down some tasks to improve the product (refactoring) according to the Review Meeting discussion and than place them on the Sprint Backlog (whiteboard) ready for the next Sprint: timebox 5 min.|
The round is repeated for 4 times, so you will have a release of 4 Sprints, the last one is normally a Release Sprint where there are no new feature added, but the Team layout the work, refactor and beatify the whole city, to make the final photo-shooting.
Curious to see what comes out? Here you go...
What do you think?