Design Patterns For Efficient DevOps Processes
summary
Covers concrete patterns: run value stream mapping to document every handoff, measure cycle time vs wait time and run separate sessions per role so hidden work (Bob’s 23 steps) appears and the map becomes a change plan not a wiki. Build tests by criteria (unit, integration, UI) with business success metrics like security, performance, accessibility; use the test pyramid and keep the UI manual when needed. Release via canary with ~10% of users or blue/green and always automated gates for the cutover. For change management, certify pipeline for CAB and classify standard vs high‑risk changes to enable automatic approvals.
AI-written summary · about
chapters (6)
- 0:00Introduction and setup
- 1:07Value stream mapping basics
- 5:01Test automation strategies
- 11:01Release engineering simplicity
- 14:31Change boards and risk
- 17:00Certifying pipelines and ISO principles
related talks
55mPatterns & Anti Patterns for Scaling & Enabling DevOps Adoption
42mObstacles & Patterns To Maximize Flow in IT Operations
40mSustainable Continuous Delivery: Patterns for rapid and reliable Releases
28mThe DevOps Pipeline
29mDevOps Transformation at Scale
25mDevOps Handbook Experiments in Accelerating Delivery
28mBringing DevOps to Product
26mDevOps Kaizen Practical Steps to Start & Sustain a Transformation