DevOps Culture Simulation (with Lego and Chocolate Game)
Organizations today can no longer afford to deliver new features to their respective markets once a year or even once a quarter. In an attempt to catch up with the competition, they jump start their DevOps journey with the "How", while losing the sight of "Why" and "What".
Join this tutorial to gain a solid understanding of foundational principles of the DevOps culture and avoid typical DevOps anti-patterns.
In this gamified simulation you will become a part of a "large enterprise" and experience how DevOps will help to eliminate silos. You will experience the benefits of cross-training and start adopting systems thinking. You will participate in the debriefing with Liberating Structures and gain valuable insights that can be immediately applied in your organisation.
The workshop is designed to be equally accessible to technical and non-technical audience alike. It bring together years of practical experience in IT, experiential learning models, elements of game design, Lego, Chocolate, and facilitation with Liberating Structures.
Engaging, simple and powerful, this workshop is not to be missed.
Outline/Structure of the Workshop
2 min - Connection: Turn & Talk (with a partner): Your name, your role, what do you know already about DevOps?
10 min - Content: "Why" and "What" of DevOps
- Misalignment of goals (focus on delivery vs. focus on stability and reliability)
- The impact of a low trust culture in traditional organizations.
- How DevOps is changing the game – findings from the latest State of DevOps report.
- Defining DevOps
- History of DevOps movement (including industry case studies)
15 min - Introducing the game
18 min – Concrete Practice - Simulation game: Part 1 “Feel the pain of the status quo”
- Dev, Ops and Security are separate teams.
- Sys Admin controls release schedule.
- Security tests are executed at the end of the Sprint.
20 min - Conclusion 1 : Debriefing the experience. Why do we need to change?
15 min - Content - Core DevOps Principles: The First Way
- The Theory of Constraints
- Typical bottlenecks in DevOps transformation
15 min - Break
18 min - Concrete practice - Simulation game: Part 2: First steps towards DevOps
- Shift-left on Security - learn about security issues before implementation.
- Build T-shaped skills with cross-training.
- Dev, Ops and Security are no longer silos.
15 min - Conclusion 2: Debriefing the experience with Liberating Structures ( 1-2-4-All)
12 min – Content - Core DevOps Principles: The Second Way
- One-piece flow
- CI/CD, deployment pipeline
- Typical impediment to Continuous Delivery
- Telemetry, Continuous Monitoring
- “You build it, you own it” mindset
18 min – Concrete practice: Simulation game: Part 3: Continuous Delivery of value with DevOps
- Enable better flow with reduced batch sizes.
- Accelerate the feedback loop with simplified deployment. o Enable environment creation on demand.
20 min - Conclusion 3: Debriefing the experience with Liberating Structures (User Experience fishbowl) What have you learnt from the game?
12 min – Content: Core DevOps Principles: The Third Way
- Chaos Engineering
- Safety Culture
20 min – Concrete practice - "Fear in the Workplace" game
20 min - Conclusion 4: Final Debriefing with Liberating Structures (25/10): If you were 10 times bolder, what would you bring back from this workshop to your organizations?
10 min - Buffer time
1) Identify the fundamental principles and practices including: Continuous Integration, Continuous Delivery, testing, “shift left” on security, “one piece flow” and the Three Ways of DevOps.
2) Discuss the critical role of the safety culture in enabling Continual Experimentation and Learning at all levels of an organisation.
3) Explain the changes DevOps brings to a Segregation of Duty, Audit requirements, CAB, risk management etc.
Dev and IT Managers, CTOs, Business Stakeholders, Individual Contributors (Dev and Ops), Security Engineers, Program Managers, DevOps/Agile Coaches
Prerequisites for Attendees
Basic familiarity with Scrum/Agile is helpful, but not mandatory