The document outlines a continuous delivery process that includes continuous integration, automated testing, deployment and acceptance testing. Changes are version controlled and built, then all unit, integration and acceptance tests are run along with regression tests. If tests pass, deployments are automated to staging and production environments. User acceptance testing is also conducted before prioritizing releases. The goal is to enable faster delivery, feedback and learning through continuous processes.

1. Development +
Version Control
Continuous Integration Run
ALL Unit, Integration, and
Acceptance Tests &
Regression tests for each
Build
E2E Testing
UAT
Production Env
Prioritize & slot
into a Release
Continuous Integration
OK?
Deployment
OK?
Deployment
OK?
Deployment
Automated Deployment?
Automated Acceptance Tests?
Manual Hand-offs?
Automated Unit Tests ?
Automated Acceptance Tests ?
TDD, ATDD / BDD ?
Automated Deployment?
Automated Acceptance Tests?
Manual Hand-offs?
Automated Deployment?
Automated Acceptance Tests?
Manual Hand-offs?
Continuous Delivery
Tech Ops
Tech Ops
Tech Ops
PO + PM / Business PO + PM / Business PO + PM / Business
Business Case
Customer
External Customers /
Users
Users
Our Vision: Faster Deliver, Faster Feedback, Faster Learning
Product Extraction &
Packaging for Delivery
PM PO E2E
Users
Successful Build
(available for Testing)
Continuous Enterprise
t1 t2 t3 t4 t5 t6 t7 t8
Teams
Dev Team
PO
Tech Ops
Build & Deploy
E2E

2. D1
D3
D4
Dev 1
D1
D3
D4
Dev 2
D1
D3
D4
Dev 3
Program Level Integration
E2E System Testing
Program 1
User System Testing/ UAT
Staging
Team 1
Team 2
Team 3
E2E System Testing (All Programs together)
User System Testing/ UAT (All Programs together)
Staging (All Programs together)
PRODUCTION
D1
D3
D4
Dev 1
D1
D3
D4
Dev 2
D1
D3
D4
Dev 3
Program Level Integration
E2E System Testing
Program 2
User System Testing/ UAT
Staging
Team 1
Team 2
Team 3