On September 19, in the format of Tech Hangout internal meetings Dmitriy Velykoivanenko and Galina Kostetskaya, Engineering Managers at Innovecs, conducted Scrum Simulation Game with LEGO bricks. GOALS: The main goal is to make sure the teams practice Scrum by building “products” with LEGO bricks. *TECH HANGOUT COMMUNITY was found in 2012 by the developers for the developers for knowledge and experience sharing. Such meetings are the part of Innovecs Educational Project that actively develops sphere of internal trainings and knowledge exchange program among professionals. This Initiative was born within the walls of Innovecs and has proved to be extremely popular and high-demand. In a short period of time it gained its own Facebook group with more than 100 members, blog with more than 40 posts and constant quarterly external meeting of Tech hangout community with more than 80 participants. The concept of the event proposes a 30-minute report on the topic previously defined, and the discussion in a roundtable session format. Join to discuss - https://www.facebook.com/groups/techhangout/

2. Scrum Simulation
with LEGO
Dmitry Velykoivanenko
Galina Kostetskaya
Engineering Managers
19/09/2014

3. Scrum terms
• Burndown/Burnup Charts
• Daily Scrum Meeting
• Product Backlog
• User Story
• Product Owner
• Scrum Master
• Sprint
• Retrospective
• Velocity
• Demo
© Copyright Innovecs 2012 2

4. The game
Timing: 120 min;
Groups: 4-6 people
Roles:
• Trainer/Scrum master (Galina)
• Product owner (Dmitry)
• Teams: developers, testers.
© Copyright Innovecs 2012 3

5. Schedule
Pre-game:
• Organizing teams: 5 min
• Project Chartering: 10 min
• Building the backlog: 15 min
• Estimating: up to 20 min
Coffee-break: 15 min
Game:
• Sprint planning: 3-5 min
• Sprint: 7 min
• Demo: 5 min
• Retrospective: 5 min
Post-game: up to 20 min
© Copyright Innovecs 2012 5

6. © Copyright Innovecs 2012 4

7. Debriefing
• How did it feel being on a Scrum team?
• How did the short iterations go?
• How accurate were the estimations?
• What would we have done differently from the
beginning, if we had another
• What was the job of the Product Owner?
• How did it feel after the first sprint when almost
all items required re-work?
• How will your strategy change, if you know the
Product Owner is unavailable during sprints?
• How did inter-team communication go? Were
there any dependencies? How were they
resolved?
© Copyright Innovecs 2012 5

8. Thank you!
Galina Kostetskaya
Dmitry Velykoivanenko
Engineering Managers

9. Photos (Sep 19, 2014)
© Copyright Innovecs 2012

10. Photos (Sep 19, 2014)
© Copyright Innovecs 2012