In 30 seconds
- Shorter loops mean faster learning and less waste.
- Agile runs loops at every level: code, sprint, product.
- A loop only counts if someone acts on it.
Loops at every level
| Loop | Typical length |
|---|---|
| Unit tests | Seconds |
| Pairing | Seconds to minutes |
| CI build | Minutes |
| Daily Scrum | Daily |
| Sprint Review and Retro | Weeks |
| Release and user data | Weeks to months |
Why shorter is better
The longer between action and feedback, the more work builds on a wrong assumption. Short loops catch mistakes while they're cheap.
Tightening loops
- Speed up builds and tests
- Release smaller slices to real users
- Give personal feedback regularly, not just in annual reviews
Myth vs reality
Myth · Feedback is only from customers.
Reality · Tests, teammates and data are feedback too.
Myth · More feedback is always better.
Reality · Too much unprocessed feedback is noise.
Myth · Collecting feedback closes the loop.
Reality · Acting on it does.
FAQ
What's the most important loop?
Usually the one with real users.
How do we get feedback faster?
Smaller changes, automation and earlier demos.
How does this relate to empiricism?
Feedback loops are how inspection and adaptation happen.