Course overview
The course gives you a comprehensive overview of how and why DevOps can strengthen collaboration between clients, development, operations, support, and management.
You will learn the value of DevOps and the principles, methods, models, and tools that form the core of DevOps. The course also addresses the connection to other models and frameworks such as ITIL,® Lean, and agile development, and which factors determine whether a DevOps adoption succeeds.
The course is a full day and is suitable for those who want an overall understanding of DevOps, whether you are a developer, manager, or work in operations, support, or administration.
See also our courses in methods and frameworks to develop your knowledge in ITIL, DevOps, SAFe and other established working methods for structure and efficiency.
Course Objective
After the course, you can:
- Explain what DevOps is and what it means in different contexts
- Describe the key players and frameworks within DevOps, such as DASA and the DevOps Institute
- Explain the value of implementing DevOps policies and practices
- Describe how DevOps is connected to organization, culture, working methods, and automation tools
- Use concrete tips and ideas when applying DevOps
Target Group
The course is aimed at those who:
- Want an overall understanding of DevOps
- Are a developer, manager, or work with operations, support, or management
Prerequisites
No special prior knowledge is required.
Certification
This course does not have any associated certification. Each participant who completes the course receives a course certificate.
Trainer
The course is led by one of Informator’s experienced DevOps trainers.
More about the course
Course structure
09.00-10.00 – Introduction
- Why start a DevOps journey? What business goals do we believe 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
- Who are the key organizations trying to shape DevOps in their own way? We go through their key 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 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 with 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 way of working in a larger organization and how we can manage 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 customized ways of working and an organization that fits, can work wonders. But why do so many mean tools and other technology when they talk 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 microservices are explained.
16.45-17.00 – Summary