Start Here
You need the right framework that drives the right mindset to use CD and agents correctly
less than a minute
Start with your problem, not the guide. Not sure what is wrong? Answer a few questions. | Developer symptoms | Manager symptoms
This guide expands on the practices defined at MinimumCD.org and the production-tested playbooks from the Dojo Consortium. Each adapted page includes attribution to its source material.
You need the right framework that drives the right mindset to use CD and agents correctly
Answer a few questions to narrow down which dysfunction symptoms match your situation.
Start from what you observe. Find the anti-patterns causing it.
Start here. Find the anti-patterns your team is facing and learn the path to solving them.
Guides for adopting continuous delivery - whether you are starting fresh or migrating an existing system.
Pipeline reference architectures for single-team, multi-team, and distributed service delivery, with quality gates sequenced by defect detection priority.
A catalog of defect sources across the delivery value stream with earliest detection points, AI shift-left opportunities, and systemic prevention strategies.
Extend continuous delivery with constraints, first-class artifacts, and practices for AI agent-generated changes.
Concise definitions of the core continuous delivery practices from MinimumCD.
Detailed definitions for key delivery metrics. Understand what to measure and why.
Test architecture, types, and best practices for building confidence in your delivery pipeline.
The capabilities that drive software delivery performance, as identified by DORA research.
Visual guide showing how CD practices depend on and build upon each other.
Key terms and definitions used throughout this guide.
Frequently asked questions about continuous delivery and this migration guide.
Books, videos, and further reading on continuous delivery and deployment.
Contributors who have helped shape this migration guide.
This content is being developed and will be available soon.