Lean, agile and dev ops games- facilitator's guide
1. Facilitator’s Guide
to
Lean, Agile and DevOps Thinking-
with Team Building Exercises
Ravi Tadwalkar
Lean/Agile/DevOps Coach
Co-founder, “Cisco Internal Coaches Network”; AgileCamp.org
Event Organizer, SVALN
December 2016. This work is licensed under Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
2. 2
Agenda
Lean Thinking with Penny Game (15 minutes)
Agile Management By Walking Around (15 minutes)4
2
Team Building with Marshmallow Challenge Game (15 minutes)1
Agile and DevOps Thinking with Lego Scrum Game (90-120 min)5
Lean and Agile Thinking with BallPoint Game (30 minutes)3
Lean Kanban Thinking with getKanban Game (90-120 min)6
2
4. 4
▪ Teams cannot hold on to the structure when the time runs out.
Build the tallest Freestanding structure
The entire marshmallow must be on top
Use as much or little of the kit as you need
Sticks, string, and tape can be broken up
Time to complete the challenge: 15 minutes
▪ The winning team is the one that has the tallest structure measured from the table top surface to the top of
the marshmallow. That means the structure cannot be suspended from a higher structure
• Cutting or eating part of the marshmallow disqualifies the team.
• The team can use as many or as few of the 20 spaghetti sticks, as much or as little of the string or tape
as part of their structure
▪ Teams are free to break the spaghetti, cut up the tape and string to create new structures.
Team Building Exercise #1: Marshmallow Challenge
6. 6
Agenda
Lean Thinking with Penny Game (15 minutes)
Agile Management By Walking Around (15 minutes)4
2
Team Building with Marshmallow Challenge Game (15 minutes)1
Agile and DevOps Thinking with Lego Scrum Game (90-120 min)5
Lean and Agile Thinking with BallPoint Game (30 minutes)3
Lean Kanban Thinking with getKanban Game (90-120 min)6
6
7. Exercise: The Penny Game
7
Learn how to achieve more, by
doing less
Work in groups of 5. One
timekeeper and four people doing
work.
Time box: 15 Minutes
7
8. Exercise: The Penny Game
8
Round 1:
Each person flips all pennies, one at a time.
Pass all the pennies to the next person
when you are done.
The time keeper will record the total time it
takes everyone to flip all of the coins.
8
9. Exercise: The Penny Game
9
Round 2:
Flip each penny one at a time
Pass each penny to the next person one at
a time
The time keeper will record the total time it
takes everyone to flip all of the coins.
9
10. Exercise: The Penny Game
10
RETROSPECTIVE:
Which way worked better?
Why do you think that is?
10
11. 11
Agenda
Lean Thinking with Penny Game (15 minutes)
Agile Management By Walking Around (15 minutes)4
2
Team Building with Marshmallow Challenge Game (15 minutes)1
Agile and DevOps Thinking with Lego Scrum Game (90-120 min)5
Lean and Agile Thinking with BallPoint Game (30 minutes)3
Lean Kanban Thinking with getKanban Game (90-120 min)6
11
12. 12
Team Building Activity: Lean Thinking with Ball Point Game
Rules: 5 minutes
1. Each ball must have air-time.
2. Each ball must be touched at least once by every team member.
3. Balls cannot be passed to your direct neighbor to your immediate left or right.
4. Each ball must return to the same person who introduced it into the system.
5. There are a total of five iterations.
6. A designated timekeeper records count of balls passed during each iteration.
Instructions: 5-minute short iteration, 5 such iterations
1. Two minutes of preparation time to determine how team will self-organize. (~Planning)
2. Two minute game play. (~Sprinting)
3. Record #balls that pass through the system (~Demo)
4. One minute to discuss how to improve the process. (~Retrospective)
5. Repeat for five iterations (steps 1 to 5).
Time box: 30 Minutes Goal- Get as many balls “flow” through the team as possible within 2 minutes
12
13. 13
Agenda
Lean Thinking with Penny Game (15 minutes)
Agile Management By Walking Around (15 minutes)4
2
Team Building with Marshmallow Challenge Game (15 minutes)1
Agile and DevOps Thinking with Lego Scrum Game (90-120 min)5
Lean and Agile Thinking with BallPoint Game (30 minutes)3
Lean Kanban Thinking with getKanban Game (90-120 min)6
13
14. Exercise: Management by Walking Around
14
Learn why empowering teams is
so effective
Work in groups of 2. One team
member is the manager, the other
is the team member.
Time box: 15 Minutes
15. Exercise: Management by Walking Around
15
Manager Directs Team Member to
take steps to walk across the room
Manager must count steps,
instruct the team member and
walk behind the Team Member
Team member cannot talk
Round 1
16. Exercise: Management by Walking Around
16
Manager Instructs the Team Member to
cross the room but does not give
direction
Team Member counts steps and moves
alone (Manager stays behind)
When completed, Team Member
reports the number of steps to the
Manager.
Round 2
17. Exercise: Management by Walking Around
17
• Which approach worked more
efficiently?
• Which felt better to the team
member?
• Was the manager satisfied with
the results for round 2?
Retrospective
19. 19
Agenda
Lean Thinking with Penny Game (15 minutes)
Agile Management By Walking Around (15 minutes)4
2
Team Building with Marshmallow Challenge Game (15 minutes)1
Agile and DevOps Thinking with Lego Scrum Game (90-120 min)5
Lean and Agile Thinking with BallPoint Game (30 minutes)3
Lean Kanban Thinking with getKanban Game (90-120 min)6
19
20. 20
Chocolate Lego Scrum Game
Sys Admin
provisions team
with environment
Business Owner adjusts
Market Demand in each sprint
Team tries to
make money by
creating batches
(user stories) in
each sprint
Time box: 90-120 Minutes Goal- Make Money based on Quantity, Batch Size & Price
20
21. 21
Lego Scrum Game: Three Sprints Simulations
• Sprint 1: Cyclical value delivery–
with Scrum
• Sprint 2: Agile Transformation –
optimizing Scrum team
• Sprint 3: Optimizing flow of value
21
22. 22
Lego Scrum Game: Characters in the game
• Each Scrum teams have characters
associated: 4 Dev, 2 Testers, 1 Scrum
Master and 1 Product/Service Owner
• Each scrum team has 3 Ops team
members: 1 Release Engr, 1 Sys
Admin, and 1 Security Engr
• Each Scrum team has 1 Business
Owner associated.
22
23. 23
Lego Scrum Game: Definition of Done
• Each package contains:
• one Lego animal
• one chocolate candy
• Type of animal as per user story.
• Each animal has a label with a
unique number between 1 & 120
• white numbered labels in all sprints
Sample animals:
A lion and a horse
23
24. 24
Lego Scrum Game: A Batch = A User Story Shippable As A Deployment Package
• LEGO animal = software tasks
• Chocolate = user documentation
User Story
Deployment
package
Five small
individual
packages
with a
LEGO dog
and a
chocolate
24
25. 25
Lego Scrum Game: Sprint 1- Cyclical Value Delivery with Scrum
Rules for Sprint 1:
• Sys Admin creates development environment for team
• Dev creates animal
• QA labels animal with a unique numbered label & attaches a chocolate to put it into small package with that chocolate.
• QA will create Deployment Package (“batch”) with such small packages
• QA hands off the deployment package to Release Engineer.
• Security Engineer then conducts security checks at Operations table.
• Scrum Team and Ops team both operate within the boundaries of their roles.
Product/Service Owner instructions:
• Product/ Service Owner specifies work for the sprint, e.g. 1 batch of dogs, 2 batches of cats, etc.
• Once batches produce desired quantity, Release Engineer takes deployment package to Business Owner.
Scrum Master manages time-box:
• Planning: 2 min
(to plan work for the sprint)
• Execution: 8 min (to hand-off deployment package and run security checks. If possible, Demo: 2 min, and Retrospective: 1 min)
25
27. 27
Lego Scrum Game: Sprint 2- Optimizing the Scrum Team
Rules for Sprint 2:
• Dev and QA are not siloes anymore
• Cross-train Developers and Testers
• Everyone now creates animal and attaches a chocolate to it
• Invite Sara Security into Scrum Team – learn about security issues before implementation.
• Security Engineer tells what not to put into the Deployment Package
• Everyone puts white label on the animal with a unique numbered white label & puts it into small package with that chocolate.
• First release into production. Only release engineer can deploy.
• Everyone will create Deployment Package (“batch”) with such small packages
• Everyone hands off the deployment package to Release Engineer.
• First release into production. Only release engineer can deploy, since packages are bug-free.
Product/Service Owner instructions, same as sprint 1:
• Product / Service Owner specifies work for the sprint, e.g. 1 batch of dogs, 2 batches of cats, etc.
• Once batches produce desired quantity, Release Engineer takes it as deployment package to Business Owner.
Scrum Master manages time-box:
• Planning: 2 min
(to plan work for the sprint)
• Execution: 8 min (to hand-off deployment package and run security checks. If possible, Demo: 2 min, and Retrospective: 1 min)
27
28. 28
Lego Scrum Game: Sprint 2- Group Level Debriefing
How was your experience?
What was different in Sprint 1 and Sprint 2?
28
29. 29
Lego Scrum Game: Sprint 3- Optimizing the system with Agile Transformation
Rules for Sprint 3:
• Improving the flow:
• Dev and OPs are not siloes anymore
• Building T-shaped skills
• At the start of Sprint 3, players will cross-train each other and exchange red & green labels to indicate
completion of cross-training on their name tags. Now they are able to play additional roles in the overall process.
• Right after the cross-training is complete, introduce two more changes to the game:
• Batch size = 1
• Team agreed to move to “one-piece flow”, no more large user stories
• Simplified deployment process
• Now instead of building a task in a small package and then assembling all tasks in a deployment package,
the task will be built directly in a single deployment package –for a simplified, automated deployment.
• Everyone who has been cross-trained by Robert Release Engineer can now deploy into production.
• Accelerating the Feedback
• Simplifying deployments
• Continuous Delivery
29
30. 30
Lego Scrum Game: Sprint 3- Group Level Debriefing
How was your experience?
What was different in Sprint 1, Sprint 2 & Sprint 3?
30
32. 32
Agenda
Lean Thinking with Penny Game (15 minutes)
Agile Management By Walking Around (15 minutes)4
2
Team Building with Marshmallow Challenge Game (15 minutes)1
Agile and DevOps Thinking with Lego Scrum Game (90-120 min)5
Lean and Agile Thinking with BallPoint Game (30 minutes)3
Lean Kanban Thinking with getKanban Game (90-120 min)6
32
35. 35
Summary: What is Lean? How to implement Lean with Agile & DevOps?
Lean Principles Implementation in Agile & DevOps
Eliminate waste Retrospectives, Feedback loops at every iteration
Amplify learning Retrospectives, Feedback loops at every iteration
Decide as late as possible Iteration Planning every 2 weeks
Deliver as fast as possible Short Iterations
Empower the team Servant Leadership, Team Collaboration
Build integrity in Build Quality In: Continuous Testing & integration
See the whole Cross functional teams, breaking down Silos
Principles
Values
Process
Practices
(kata)
35
Learning Scrum with Lean Thinking with Ball Point Game large open space with enough room for everyone to stand. You’ll also need about 20 brightly colored tennis/pingpong balls for 20 people, and you may want a whiteboard to do the debriefing
In this game, we will run 3 – 10 minutes sprints simulations. By the end of last sprint, we will transition from cyclical to continuous value delivery and will get a taste of Agile & DevOps cultural transformation!
In this game, we will run 3 – 10 minutes sprints simulations. By the end of last sprint, we will transition from cyclical to continuous value delivery and will get a taste of Agile & DevOps cultural transformation!
In this game, we will run 3 – 10 minutes sprints simulations. By the end of last sprint, we will transition from cyclical to continuous value delivery and will get a taste of Agile & DevOps cultural transformation!
In this game, we will run 3 – 10 minutes sprints simulations. By the end of last sprint, we will transition from cyclical to continuous value delivery and will get a taste of Agile & DevOps cultural transformation!
In this game, we will run 3 – 10 minutes sprints simulations. By the end of last sprint, we will transition from cyclical to continuous value delivery and will get a taste of Agile & DevOps cultural transformation!
Sprint 1:
Dev and Ops are silos
Everyone operates within the boundaries of their roles.
Sys Admin controls release schedule
How was your experience?
Scrum Teams, how many user stories you delivered?
This is great! Why are the customers unhappy?
Business Owners, did you get any products delivered to you?
Observers, would you like to share you observations?
It took a long time to start – getting the stories, building environments…
Then security testing at the end caused delays and rework.
Team built potentially shippable products, but wasn’t able to deploy due to the code freeze.
Effectively, they were not getting any feedback!
Why do you think there IS a code freeze?
This is a function of deployment process being manual, brittle and potentially causing service disruption.
With the Water-Scrum-fall it gets expensive to deliver changes and making them live in production.
One of the advantages of embracing DevOps , is that you are able to re-define that!
Sprint 2:
1. Cross-train Developers and Testers - address dev process bottlenecks.
2. Invite Sara Security into Scrum Team – learn about security issues before implementation.
3. First release into production. Only release engineer can deploy.
How was your experience?
What was different in Sprint 1 and Sprint 2?
Observers, what were your observations?
What about the first deployment? Robert release was working really hard to get all the stuff into production!
Sprint 3:
Improving the flow:
Building T-shaped skills
Reducing batch sizes.
Accelerating the Feedback:
Simplifying deployments
Continuous Delivery
How was your experience?
What was different in Sprint 1, Sprint 2 & Sprint 3?
Observers, what were your observations?
What about the deployments? Dev & Ops worked together really hard to get all the stuff into production!
Learning Scrum with Lean Thinking with Ball Point Game large open space with enough room for everyone to stand. You’ll also need about 20 brightly colored tennis/pingpong balls for 20 people, and you may want a whiteboard to do the debriefing
Without Lean Thinking, you really can’t be Agile!
Lean Thinking provide a compass for good decision making
Peeling the onion:
Lean -> Thinking/Principles
Agile -> Mindset/Values
Scrum -> Process/Framework
XP -> Engineering Practices