Migration Path

A phased approach to adopting continuous delivery, from assessing your current state through full continuous deployment.

less than a minute

The Migration Path is a structured, phased journey from wherever you are today to continuous deployment. Each phase builds on the previous one, so work through them in order.

The Phases

Phase	Focus	Key Question
0 - Assess	Understand your current state	How far are we from CD?
1 - Foundations	Daily integration, testing, small batches	Can we integrate safely every day?
2 - Pipeline	Automated path from commit to production	Can we deploy any commit automatically?
3 - Optimize	Reduce batch size, limit WIP, measure	Can we deliver small changes quickly?
4 - Deliver on Demand	Deploy any change when the business needs it	Can we deliver any change to production when needed?

Where to Start

If you are unsure where to begin, start with Phase 0: Assess to understand your current state and identify the constraints holding you back.

Phase 0 - Assess - The recommended starting point for any migration
Baseline Metrics - Measure where you are before making changes
For Managers - How delivery problems appear from a management perspective
FAQ - Frequently asked questions about continuous delivery
Common Blockers - Frequently encountered obstacles and how to address them

Phase 0: Assess

Understand where you are today. Map your delivery process, measure what matters, and identify the constraints holding you back.

Phase 1: Foundations

Establish the essential practices for daily integration, testing, and small work decomposition.

Phase 2: Pipeline

Build the automated path from commit to production: a single, deterministic pipeline that deploys immutable artifacts.

Phase 3: Optimize

Improve flow by reducing batch size, limiting work in progress, and using metrics to drive improvement.

Phase 4: Deliver on Demand

The capability to deploy any change to production at any time, using the delivery strategy that fits your context.