Appendix F: When to Leave This Process
This framework does not restrict you. Here are specific conditions that mean “skip or modify”:
| Condition | Action |
|---|---|
| Pre-product-market fit (startup) | Drop everything except Build Phase + automated tests. Release daily. No reviews. |
| Crisis / production outage | Drop all process. Fix the issue. Retro after. |
| Team < 3 people | Drop reviews, retros, and flags. Talk directly. |
| AI-assisted rapid prototyping | Skip TDD, skip pair programming, skip Stories. Generate, review, ship. |
| Pure maintenance / no new features | Drop spikes, domain exploration, roadmap. Move to ticketed bug fixes only. |
| Team is demotivated by process | Cut process by 50%. If energy returns, cut more. |
| A rule takes longer than the work it governs | Abolish the rule immediately. No vote needed. |
The team is always free to deviate from this guide. If you deviate successfully, update the guide to reflect what actually works. The guide serves the team, not the other way around.