DevOps Introduction

Course structure

09.00-10.00 – Introduction

• Why start a DevOps journey? What business goals do we think we can achieve?
• What is DevOps? And what is not?!
• DevOps from the start
• Modern DevOps: according to whom?

10.00-10.15 – Morning break

10.15-11.15 – Devops Greatest Hits

• What are the key organizations that are trying to shape DevOps in their own way? We go over their most important contributions to the DevOps movement. DASA’s six principles, the DevOps Institute’s CALMS model, SAFE’s Continuous Exploration, and much more.

11.15-12.15 – Deep dive into the DevOps culture

• What organizational culture best supports DevOps-based ways of working?
• And above all: how to implement it?
• We’ll look at how other organizations have gone about finding ‘their’ DevOps culture, and learn about the best (and worst!) ways to create the culture we want using methods like ADKAR, Kotter’s 8 steps, the agile onion(!), and 5C.’

12.15-13.00 – Lunch break

13.00-14.00 – A tour of the DevOps organization

• What does an organization look like that supports and helps create our DevOps culture?
• This is where DevOps began; by merging the groups that worked with development, maintenance, and operation. But today, we’ve gone so much further, with fully cross-functional teams that have both responsibility and mandate for what they deliver.
• We also look at the difficulty of maintaining a DevOps culture and DevOps ways of working in a larger organization and how we can deal with it.

14.00-15.00 – A walk through DevOps ways of working

• If our culture says we should delegate decisions, and we should organize ourselves in independent teams, what should our ways of working look like?
• We are taught that strict processes that must be followed at all costs do not work in a DevOps organization. Instead, we work with more loosely cohesive ways of working, where each team adapts them to their needs. We travel to places like Lean and Agile and let ourselves be inspired by mindsets and methods such as focusing on creating a “flow” with the help of Scrum.

15.00-15.15 – Afternoon break

15.15-16.45 – Building a DevOps architecture

• The right culture, supported by adapted ways of working and an organization that fits can work wonders. But why do so many tools and other technologies mean when talking about DevOps?
• Well, because automation and flexible tools are very important for us to be able to realize, above all, the vision of shortening lead times and getting new functions into production faster. But also so that those who work in the team can thrive in the workplace while being productive.
• We look at the most common tools that can be used to create the Continuous Delivery Pipeline that is our goal. But we’re also looking at how the basic architecture of our product can be changed to fit more easily into our pipeline.
• Automation is a success factor for shortening lead times, increasing quality and reducing costs. Automation places demands on the technical architecture and the structure of services. Concepts such as micro service are explained.

16.45-17.00 – Summary