CI/CD Course
CI/CD in Modern DevOps
In this lesson
DevOps is a set of practices, cultural values, and organisational patterns that break down the traditional wall between the team that writes software and the team that runs it. It is not a job title, a tool, or a department — it is a philosophy about how high-performing engineering organisations work. At its technical core sits CI/CD: the pipeline that translates DevOps culture into daily, repeatable practice. You cannot have a functioning DevOps organisation without it.
What DevOps Actually Is — and What It Is Not
DevOps is widely misunderstood. Some organisations treat it as a job title — a "DevOps Engineer" who manages the pipeline while developers and operations teams continue to work in silos. Others treat it as a toolset: buy the right CI/CD platform and you have done DevOps. Neither is accurate.
DevOps is fundamentally about shared ownership. Developers own what happens in production. Operations teams understand the code that runs on their infrastructure. Everyone is responsible for quality, reliability, and delivery — not just the person whose job title contains the relevant word. The tools support this shared ownership; they do not create it on their own.
The Restaurant Kitchen Analogy
In an old-fashioned kitchen, chefs cook and waiters serve — with a wall between them and no shared accountability for the dining experience. In a modern open kitchen, chefs see the dining room, waiters understand the menu, and everyone cares about whether the guest leaves happy. DevOps is the open kitchen model applied to software. CI/CD is the pass — the counter where code moves from one side to the other, checked, confirmed, and ready.
The Three Ways — How DevOps Organisations Think
Gene Kim's The Phoenix Project and The DevOps Handbook describe the underlying principles of high-performing engineering organisations as the Three Ways. These are not steps in a process — they are mental models that shape how work flows through an organisation. CI/CD is the practical implementation of all three.
The Three Ways — and How CI/CD Implements Each One
Where CI/CD Sits in the Modern Toolchain
A CI/CD pipeline does not operate in isolation. It connects to a wider ecosystem of tooling that together forms the DevOps toolchain. Understanding how these tools relate to each other is essential for working inside any modern engineering organisation.
The Modern DevOps Toolchain — Where Each Tool Fits
A Day Inside a Mature DevOps Team
Abstract descriptions of DevOps culture are easy to misread. Here is what a working day actually looks like inside a team that has CI/CD and DevOps working well together — not as a best-case scenario, but as an ordinary Tuesday.
An Ordinary Tuesday — With Mature CI/CD and DevOps
Platform Engineering — The Next Step After CI/CD
As organisations mature beyond basic CI/CD, many are moving towards platform engineering — building an internal developer platform (IDP) that wraps the entire toolchain into a self-service layer. Instead of every team configuring their own pipelines, secrets management, environment provisioning, and observability, a dedicated platform team builds and maintains a standardised platform that product teams use.
The pipeline is still there — it is just pre-built, standardised, and available to every team without each team having to reinvent it. A new service that follows the platform conventions gets CI/CD, monitoring, secrets management, and deployment tooling automatically, from day one. This is what large engineering organisations like Spotify (Backstage), Netflix, and Airbnb have built internally — and what open-source platforms like Backstage and Port are now making available to smaller organisations.
You do not need to build a platform to benefit from CI/CD. But understanding where platform engineering sits helps you see the trajectory — CI/CD is not the destination, it is the foundation that everything else is built on.
Warning: Buying the Tools Does Not Mean You Have DevOps
The most common failure mode for DevOps adoption is treating it as a tooling purchase rather than a cultural change. A team can have GitHub Actions, Terraform, Datadog, and Kubernetes — and still operate in silos, still blame each other for outages, still hold monthly release calls, and still fear production. The tools enable DevOps; they do not create it. If developers are not responsible for what runs in production, and operations teams do not understand the code, adding more tooling will not help.
Key Takeaways from This Lesson
Teacher's Note
When you join a new team, the fastest way to understand its DevOps maturity is one question: "Who gets woken up when production breaks?" If the answer is "operations," the wall is still there.
Practice Questions
Answer in your own words — then check against the expected answer.
1. What is the name of the framework from The DevOps Handbook that describes the principles behind high-performing engineering organisations — covering Flow, Feedback, and Continual Learning?
2. What is the discipline called — practised by large engineering organisations like Spotify and Netflix — where a dedicated team builds and maintains a standardised internal developer platform so that product teams get CI/CD and tooling automatically?
3. What is the core principle that separates genuine DevOps from simply buying a set of DevOps tools — the idea that developers and operations teams are both responsible for what runs in production?
Lesson Quiz
1. A colleague says their company "does DevOps" because they hired a DevOps Engineer to manage the pipeline. What is the most accurate response?
2. A CI pipeline reports a failing test within 3 minutes of a commit, while the developer is still working on the same task. Which of the Three Ways does this most directly implement?
3. What is the goal of platform engineering in a mature DevOps organisation?
Up Next · Lesson 11
Source Code Management
Every pipeline starts with a commit. Section II opens with source code management — how Git branching strategies, pull request workflows, and repository structure directly shape how your pipeline behaves.