You can also download a free guide in English or other languages from this website. This is a new book released 31 January 2017 by Alexey Krivitsky who has invented lego4scrum back in 2009 or so. This is the third and by now the most complete guide with a foreword by Henrik Kniberg. This book summarises years of experiments and hundreds of lego4scrum workshops with groups of 10 toIt will let you teach Scrum in a complete new, fresh and also fun way. This book is written for: Scrum Trainers exploring way of adding more elements of interactivity and gaming into the trainings turning them more to “from the back of the room” kind of things. Agile Coaches looking for new training and coaching ideas with some elements of serious plays and simulations. Scrum Masters willing to get ideas how to introduce agile thinking to new teams and newcomers in a fun and easy way. Professors and Teachers trying to adapt their teaching style to the ever-changing world that is full of games, fun and LEGO.
Anyone else who is in charge of "installing Agile thinking and Scrum in a workspace". lego4scrum 3.0 incorporates the following popular agile coaching techniques: overall backlog refinement with multiple teams joint multi-team scrum meetings continuous integration and deployment and more little tips and tricks to make the simulation valuable and fun. Get the book, get some LEGOs and have fun with this. Ask any question on the simulation. Talk to other facilitators. Help improve the simulation. Get connected with the book author. Join our #slack team. Planning to teach Scrum? Consider bringing a bag of LEGO! Get advices to make the simulation a great experience not only for your students but as well for yourself. The original paper by Alexey Krivitsky gives the bare minimum to get it going. Have just run the simulation? We'd love to post your reports as a blog post, a link to your article, photos or video as many other trainers have already done.
English is too easy? Consider the choice of 20 languages! You are very much welcome to contribute to our community with a translation into your language. FINDS THE BRIEF GUIDE Recently I had a chance to run lego4scrum for ... And it was fun! The simulation started with explaining the ideas of the LeSS and LeSS Huge frameworks. Then we run a team self-design workshop where all participants create 22 teams based on their skills and some other constraints. Six product managers played a Product Owner team with a Chief Product Owner in charge of the overall product visioning and alignment. This was a Lego Enterprise with a mission of providing long-distance sightseeing trips to city citizens. The enterprise received its initial funding and was expected to get profitable as soon as Based on presented market needs (users were willing to travel and pay for certain destinations) the Product was split into six Requirements Areas (one for each of the cities) each
with an Area Product Owner and 3-6 teams to work on a specific city with its infrastructure. Then all Requirement Area groups had a simultaneous Initial Product Backlog Refinement session for about 15 minutes defining product elements to get built. This process was facilitated by a pair of ScrumMasters serving each group. Surprisingly a community of practice emerged during these discussions - representatives of different groups started to design a transportation hub with a goal to minimize the needed material (the materials had to be bought and were expensive). Then a multi-team Sprint Planning for 22 teams all in our room. All teams created their Sprint Backlog and also a visual Sprint Board to visualize sprint The Enterprise nearly broke after the 1st sprint - too much material spent on cities (Lego bricks had its price) and very little buses and roads to actually help making money (Oops!). After a series of retrospectives: one per a Requirement Area and then an Overall one, the Enterprise agreed on its key improvements.
Surprisingly, the market changed too. Right after "Brexit" everyone was willing to leave London, and also due to the Christmas time Prague became the number-one destination. This came to a big surprise to the teams and the Product Onwers since Prague was not in a list of the six initial cities... The 2nd sprint demonstrated the whole power of self-organization and unleashed creativity. The teams were able to demonstrate 6 cities interconnected with transportation lines cruising passengers and they made good profit! Wesley van Heije has just submitted an experience report on teach Scrum with LEGO. Check it out: Teaching Agile through Image by Hakan Forss The LEGO Set referred to in the facilitator's guide is no longer available in stores. So here are few ideas for its replacement. Creative Building Box (#10695) LEGO Medium Creative Brick Box (#10696) Filmed and shared by Jan Kees Velthoven Filmed and shared by Bartosz Zieleźnik
Bartosz has shared with us recently an amazing video from his lego4scrum workshop. Find out how powerful Scrum can be Learning by doing, and failing. Do not underestimate any Story... it may cost you a lot! The Scrum Lego City brings you right to the point: You will experience what it means to be agile. With the Scrum Lego City from agile42 you can find out how powerful Scrum can be. Scrum Lego City by agile42 is licensed under a Creative Commons Attribution-Share Alike 3.0 License. LInk to buy the Material LEGO, a lot, with plans (possibly CREATIVE boxes where you can build many things with the same blocks) Product Vision: a document containing the Vision to build the LEGO city Requirements and User Stories (Cards): pre-compiled Requirements and Stories related to various building and elements of the City Whiteboard or electrostatic sheets to write sprint outcome and velocity and make a whiteboard for the team Post-It to write tasks
Pen and whiteboard markers Unexpected (Cards): some cards containing unexpected behavior to steer from outside the Game (e.g: you are ill, you leave the team for 4 min.) Cards - contain also suggestions on what people should do in particular situations (e.g: Prepare the whiteboard with 3 columns, commit first to the items which have a specification cause are less risky). Here you can download the User Stories for the Lego City Game The goal of the Game is to simulate every aspect of the Scrum process learned in theory the day before. The Team and the Scrum Master will have to put in practice everything learned during the theoretical part. The game will dedicate specific time to the various phases: 5 min. Preparation from the Product Vision for the Product Owner, includes sorting out the provided stories plus adding some own or enriching some of the 5 min. Product Owner presenting the Product Vision as well as a high level presentation of the Backlog, Teams can ask questions on stories or requirements
Here you can have a release planning meeting session, where the team(s) focus in estimating as many stories as possible to have an initial idea of the Release Costs. This assumes that the Trainer guides the Product Owner in setting a reasonable Release scope (that can be adjusted anyway after every sprint). 5 min. Release Planning Meeting, teams estimating stories from top to bottom Now start with the first sprint planning meeting, and prepare to run 4 Sprints and execute as much as possible of the Backlog: 5 min. Sprint planning meeting, basically commit to some stories and make an initial task breakdown 3 min. Review Meeting (showing the Product Owner what has been build) 5 min. Team Retrospective At the end of the 4th Sprint the Product Owner should make the Release Review and together with the Teams analyze the results. Discuss the outcome of the whole Release cycle in comparison with the initial Vision and Goals Outcome of the game What are the goals of the game from a training perspective?
We expect the people to experience the following: Learn to organize a Backlog properly, prioritizing what is more important first Learn to measure the Team velocity and based on that make decisions, and re-prioritize the Product Backlog Learn to negotiate with the Team about acceptance criteria and the deliverable Experience self-organization and pressure given from the time-box Learn to communicate focused on the sprint goal Learn how to plan and organize tasks during a sprint Learn to estimate fast and precisely based on the experience Learn to measure performance and improvements Learn to deal with unexpected events Learn to moderate the meetings Learn to mediate between the Team and the Product Owner Learn how to deal with Impediments Learn how to coach and suggest improvements to the Team Start with the product vision of the Scrum Lego City Game To understand the vision of a product is the first important step in order to develop the product in the right way.
This is why you need to give the vision to the whole Scrum Team at the beginning of the game. Here is the vision we use... agile42 wants to build a website to present what can be done with LEGO bricks in only 20 min of time. You will have to use Scrum to prove that you can build a LEGO city with fully fledged buildings, cars and natural environments. The city needs to fulfill some specific criteria PO: make clear that there are already some fixed and defined requirements and stories, and that you have prepared a backlog At the end of 4 Sprint the city will be released to agile42, that will make a photo and post it on the agile42 Blog where everyone will see and vote, comment your results :-) When and how to use the Scrum Lego City Make sure that the basics of Scrum are known. Everybody needs to know e.g. relative estimation Focus on the Synergies Scrum brings out Respect the Creative Common Licenses Scrum Lego City with agile42 You like to get professional help introducing Scrum and playing the game?