Simulations use immersive and exciting high-technology scenarios to bring real world challenges to life whilst demonstrating the benefits that can be achieved through the introduction of technology. Simulations lead participants to come to understand the technology, to apply learning outcomes to implement practical improvements which resolve the challenges being encountered and ultimately drive improved effectiveness.

ROUND 1 – CHAOS

• Highlights a significant customer frustration
• Brings to life the need to collaborate and communicate across an organization, evident through a lack of trust between the teams and information in the right places at the right time
• Establishes the need for single teams with common goals, and defined roles and responsibilities that break down the traditional silos
• Highlights the lack of engagement between Dev and Ops, resulting in; poor Time To Market (TTM), lack of agility, poor business performance and a lack of knowledge in the Development Team of the production systems and standards
• Focuses on manual, time consuming and error prone processes
• Focuses on a lack of priority The DevOps Simulation experience is a one day, role based workshop. A team of 15 – 20 Members is perfect to conduct a Simulation Program.

ROUND 2 – IMPROVED

• Talks to the improvements that have been made from the previous round
• Highlights the need for analytics to drive enhancements and new developments
• Underlines the need for common success measures and owners across the entire software development lifecycle and beyond
• Reinforces the desire to continuously refine the “ways of doing things” to build in quality at the front
• Underlines the need for virtual testing and service virtualization
• Highlights non-functional requirements, such as, monitoring, performance, disaster recovery and high availability

ROUND 3 – OPTIMIZED

• Talks to the improvements that have been made from the previous round
• Focuses on a organization that is still mainly reactive and not yet looking proactively, particularly from Operations
• Highlights the impact to the customer when application deployments are not architected with a service mindset
• Accentuates a “Project” rather than “Product” focused mindset with information being kept within the project rather than shared
• Brings the idea of process duplication and waste into the discussion
• Focuses on a lack of continuous feedback across the teams, particularly back to Development, leading to a discussion around moving roles closer together and “Shift Left”
• Emphasizes the need for continuous integration