Laws of Software Engineering · Framework
Framework
The Three Ways
A way of seeing DevOps as a whole. Optimise flow from idea to production. Amplify feedback from production back to development. Build a culture of continuous experimentation and learning.
How to use it. Use it to diagnose what is missing. Most engineering organisations are good at one of the three and weak at the others. The one you neglect is usually the one limiting your performance.
How it gets misused. Treated as a sequence: first flow, then feedback, then learning. The three reinforce each other. Working on one without the others gives short-term gains that decay.
Related
-
Law
DORA / Accelerate Findings
Four numbers predict whether a software organisation is performing well: how often you ship, how long changes take, how often changes break things, and how fast you recover when they do.
- Principle Continuous Delivery Keep software in a state where it could be released to users at any moment, by anyone, with confidence.
- Principle Feedback Loops Every system improves at the rate of its slowest feedback loop. Shorten the loops between action and outcome.
Clusters
- The Improvement cluster - How systems get better over time.