Multiple Services Must Be Deployed Together
Changes cannot go to production until multiple services are deployed in a specific order during a coordinated release window.
Deployment and Release Problems
Symptoms related to deployment frequency, release risk, coordination overhead, and environment parity.
less than a minute
These symptoms indicate problems with your deployment and release process. When deploying is painful, teams deploy less often, which increases batch size and risk. Each page describes what you are seeing and links to the anti-patterns most likely causing it.
How to use this section
Start with the symptom that matches what your team experiences. Each symptom page explains what you are seeing, identifies the most likely root causes (anti-patterns), and provides diagnostic questions to narrow down which cause applies to your situation. Follow the anti-pattern link to find concrete fix steps.
Related anti-pattern categories: Pipeline Anti-Patterns, Architecture Anti-Patterns
Related guides: Pipeline Architecture, Rollback, Small Batches
The Team Is Afraid to Deploy
Production deployments cause anxiety because they frequently fail. The team delays deployments, which increases batch size, which increases risk.
Hardening Sprints Are Needed Before Every Release
The team dedicates one or more sprints after “feature complete” to stabilize code before it can be released.
Releases Are Infrequent and Painful
Deploying happens monthly, quarterly, or less. Each release is a large, risky event that requires war rooms and weekend work.
Merge Freezes Before Deployments
Developers announce merge freezes because the integration process is fragile. Deploying requires coordination in chat.
Staging Passes but Production Fails
Deployments pass every pre-production check but break when they reach production.