From DevOps to Lean: A Two‑Year Reflection on Value‑Stream Delivery and Continuous Improvement

Two years ago I read *The Phoenix Project* and wrote an unpromoted article titled “DevOps Overview”, which unexpectedly attracted many readers. At that time DevOps meant continuous delivery pipelines and operational automation.

Since then the industry has undergone a dramatic shift: cloud computing, Docker, Kubernetes and micro‑services have become mainstream, and DevOps is now a hot topic with dozens of conferences and certifications.

DevOps originated from the goal of “ten deployments a day” to increase deployment frequency, ultimately improving reliability, stability, agility and security of production systems.

The three‑step workflow described in the book aligns with Goldratt’s Theory of Constraints (TOC) and focuses on delivering business value with minimal resources.

Step 1: Build an end‑to‑end workflow from development through IT operations to the customer, visualizing the value stream, limiting batch size, preventing defects from flowing downstream, and continuously optimizing for the overall system throughput. Essential practices include Kanban visualization, continuous integration, automated testing, on‑demand environments, and a secure, change‑friendly system.

Step 2: Establish rapid feedback loops for each stage of the value stream, amplifying benefits and ensuring problems are detected and fixed at the source. This involves stopping the pipeline on build or test failures, daily continuous improvement, automated test suites, shared goals between development and operations, and telemetry that shows whether code and environments meet customer expectations.

Step 3: Foster a culture that encourages experimentation, learning from failure, and repeated practice. Allocate at least 20 % of development and operations cycles to non‑functional work, promote a “Say No” mindset to avoid waste, and embed anti‑fragility principles such as chaos testing to turn failures into learning opportunities.

The ultimate aim is to embed IT into everyday business so that its presence becomes invisible, delivering value without a distinct “IT department”. The article concludes with reflective questions about personal work, value delivery, goals, metrics, and risk, encouraging readers to discuss these with colleagues.

References: *The Phoenix Project* by Gene Kim, *The Goal* by Eliyahu Goldratt, *Lean Product Development* by He Mian, and the “DevOps Overview” article linked above.