Embracing the DevOps culture involves substantial changes for organizations and significant cultural changes for the people who work there. In order to facilitate its adoption and implementation, it is necessary to understand this culture, its ins and outs, and to know the best practices in order to quickly adopt the right reflexes. Find out how DevOps principles, best practices, and tools will help you rapidly change paradigms. This training takes you right into the DevOps culture!
How it all started
The 3 pillars of DevOps: Agility, Lean and ITSM
The Agile manifesto
The Agile development
The fundamentals of Agility
From Agility to DevOps
Value Stream Mapping
From Agility, from Lean to DevOps
Experimentation and continuous learning
Value Stream Mapping Workshop
Duration: 45 minutes
Participants: Min 8 - ideally 12
Description: «Between what I think, what I mean, what I think I say, what I say, what you want to hear, what you hear, what you think you understand, what you want to understand, and what you understand, there are at least nine possibilities of not understanding each other.» (Bernard Werber).
The number of possibilities is multiplied when we add the new means of communication (e-mail, chat, ticket ...) now available to us. While none of them can replace the value of a simple face-to-face conversation, we still seem to prefer them. It’s easier to write an email or send a text. I feel more compliant by writing my requirement down and sending it. This game is designed to demonstrate the loss of value and understanding when avoiding face-to-face conversations and direct modes of collaboration.
Participants: 7 to 9 (+ observers if more participants)
Description: Understand the principles of the DevOps movement by doing a scenario in the form of development and operations teams. This workshop will show how the seemingly opposing goals of developers (adding functionality) and operators (ensuring stability) can be reconciled to support organizational goals.
This workshop highlights the following difficulties:
- communication between dev and ops,
- importance of collective objectives rather than individual objectives,
- need to work together to solve problems.
It is performed in the form of iterations (silo, dialogue, sharing, common goals, symbiosis).
Conclusion, exchanges & discussion around the following themes:
Determine needs: Dev and Ops, two teams that need each other to better serve the business
Prioritize organizational change
Relaunch and/or improve team communication
Modify work dynamics
Set up KPIs