Laws of Software Engineering · Framework
Framework
Theory of Constraints
The speed of any system is set by its slowest part. Improving anything else makes no difference.
How to use it. Find the slowest part. Get the most out of it. Make everything else serve it. Then add more capacity to it. Then start again, because there will be a new slowest part.
How it gets misused. Confused with just spotting bottlenecks. The discipline is the order. Get the most out of the constraint before spending money to make it bigger. Otherwise the new capacity goes unused.
Related
-
Law
Little's Law
Things sitting in the system = how often they arrive × how long they stay.
- Framework Improvement Kata A four-step pattern for getting better at anything. Understand the direction. Grasp the current condition. Set the next target condition. Run experiments toward it.
-
Framework
Deming's System of Profound Knowledge
Four ways of looking at a problem that work together: seeing it as a system, understanding variation, asking how we know what we know, and paying attention to people.
Clusters
- The Improvement cluster - How systems get better over time.
- The Systems Thinking cluster - Ways of seeing systems whole.