1. The three ways of DevOps #
The framework of The Phoenix Project and the DevOps Handbook.
Flow, feedback, learning #
| Way | Goal | Practices |
|---|---|---|
| 1. Flow | Speed up the movement of work from development to production | small batches, CI/CD, limiting work in progress, removing queues |
| 2. Feedback | Detect and fix problems as early as possible | automated tests, observability, alerts, fast reviews |
| 3. Continuous learning | Experiment and learn from failures | blameless post-mortems, time dedicated to improvement, sharing |
DevOps is neither a tool nor a job title: it is a way of organizing work so that shipping often is both fast and safe. The tools (CI/CD, IaC) serve these three ways.
2. Seeing the value stream #
You only improve what you can see.
Value stream mapping #
Value stream mapping follows a request from idea to user and measures, at each step, the processing time and the waiting time. In most organizations, actual work represents less than 15% of the total lead time: gains come from removing waits (manual approvals, unavailable environments, handoffs between teams).
Good practice: Run the workshop with all the teams involved (dev, ops, security, business) and start from a recent real request, not from the theoretical process.
Small batches and work in progress #
- A smaller batch moves through the system faster and its defects are easier to find.
- Limit work in progress (WIP): finish before starting.
- Make work visible: a shared kanban board including operations tasks and technical debt.
3. Organizing teams #
Who builds, who runs.
You build it, you run it #
In the historical model, developers « throw over the wall » what operations must run (see the wall of confusion). DevOps brings the two together: the team that builds a service is also responsible for running it in production, on-call included. In return, it gets the autonomy and tools to deploy on its own.
Anti-pattern: Renaming the operations team « DevOps team » and giving it all the pipelines recreates a silo: DevOps is a shared responsibility, not a new intermediary team.
Team Topologies #
| Type | Role |
|---|---|
| Stream-aligned | delivers value on a business stream, end to end |
| Platform | provides self-service internal services (CI/CD, clusters, observability) |
| Enabling | temporarily helps teams acquire a skill |
| Complicated subsystem | masters a highly specialized component |
4. A learning culture #
Psychological safety and post-mortems.
Blameless post-mortem #
After an incident, the goal is not to find a culprit but to understand how the system (tools, processes, available information) made the error possible. A blame culture pushes people to hide problems, which makes them worse.
- Factual timeline of the incident (detection, actions, resolution).
- Impact: users, duration, data.
- Contributing factors, looking for several causes rather than a single « root cause ».
- What worked well.
- Corrective actions with an owner and a deadline, tracked like the rest of the work.
Did you know?: DORA research shows that a generative culture (trust, information sharing, failures seen as learning opportunities) is a predictor of delivery performance.
My progress
Sign in to track your progress and take notes. Sign in
💬 Questions about this lesson
No questions yet: be the first to ask for help or share your configuration.
Recommended Articles
DevOps best practices: culture, CI/CD, infrastructure as code and measurement
DevOps best practices: culture and collaboration, continuous integration and delivery, trunk-base...
Observability, SRE and incident management for DevOps teams
Operate what you ship: metrics, logs and traces, golden signals, SLIs, SLOs and error budgets, ac...
DevOps variants: understanding how engineering culture has evolved
Discover the different flavors of DevOps: DevSecOps, AIOps, NoOps, GitOps and FinOps. Understand ...
The CALMS framework: the 5 pillars of DevOps
Discover the CALMS framework, the essential foundation for a successful DevOps transformation, th...
The wall of confusion
The 'wall of confusion' is a metaphor often used in a DevOps context to describe the cultural, or...
Git for DevOps: branches, code reviews and versions
Organize work with Git in a DevOps approach: trunk-based development or GitFlow, short-lived bran...
Platform engineering, FinOps and AI: the new frontiers of DevOps
Understand how DevOps is evolving: platform engineering and internal developer platforms (IDP), g...
End-to-end CI/CD (1/5): principles and anatomy of a pipeline
Understand end-to-end CI/CD: continuous integration, continuous delivery and continuous deploymen...
End-to-end CI/CD (2/5): continuous integration, testing and quality
Succeed with continuous integration: the test pyramid, unit, integration, contract and end-to-end...