rate) and throughput (deployment lead time, deployment frequency) e. ENABLE COORDINATION AND SCHEDULING OF CHANGES i. Loosely coupled architectures enable greater team independence and can likely succeed succeed with more informal coordination approaches like chat rooms ii. For deliberate change scheduling, gather representatives, not authorize changes, but to schedule and sequence. f. ENABLE PEER REVIEW

of our code and environments—we do this by reserving cycles in each development interval, or by scheduling kaizen blitzes, which are periods when engineers self-organize into teams to work on fixing any