Part 1 of our series on putting CD into practice.

1. HOW DO YOU
IMPLEMENT
CONTINUOUS
DELIVERY?
Part 1 of our series
on putting CD into
practice.
Share this ebook.
PERSPECTIVES

2. WHY DO CD?
Before we get to the how,
let’s understand the why…
WHY DO CD?

3. Reliable delivery of
software
WHY DO CD? Before we get to the how,
let’s understand the why…

4. Faster time to market
WHY DO CD? Before we get to the how,
let’s understand the why…
Reliable delivery of
software

5. WHY DO CD?
Continuous Innovation
Before we get to the how,
let’s understand the why…
Faster time to market
Reliable delivery of
software

6. Let’s look at a “classic” release
Design Development Release
WHY DO CD?

7. The reality
Deployment Issues
Defects
Product changes
WHY DO CD?

8. Defect introduced
Feature
incorrectly
implemented
Stuff built on
top
Deployment Issues
Defects
Product changes
WHY DO CD? The reality

9. HOW DOES CD
HELP?
9

10. #1 Helps you build the right thing
Release small
chunks
of functionality
frequently.
Release
How does
CD help?

11. Release small
chunks
of functionality
frequently.
Release
How does
CD help?
Get regular customer
validation of the
product’s value
Get
Feedback
#1 Helps you build the right thing

12. Release small chunks
of functionality
frequently.
Release
How does
CD help?
Get regular customer
validation of the
product’s value
Get
FeedbackImprove
Incorporate feedback
rapidly. Fail fast and
learn fast.
#1 Helps you build the right thing

13. #2 Reduces risk of releases
How does
CD help?

14. 1 1
2
1
2
3
1
2
3
4
1
2
3
4
5
2
3
4
5
1
6
2
3
4
5
1
6
7
How does
CD help?
Time
Unreleased
#2 Reduces risk of releases
Unreleased changes = RISK.

15. How does
CD help?
Released changes = VALUE
#2 Reduces risk of releases
1
1
1
2
1
3
2
1
4
3
2
1 2
3
4
5
1
3
4
5
6
2
1
3 4 5 6 72 Unreleased
Released

16. #3 Delivers “real” progress
How does
CD help?

17. How does
CD help?
RELEASE CHECKLIST:
 Regression Testing
 Integration Testing
 User Acceptance Testing
 Infrastructure Setup
 Performance Testing
 Security Audit…
“Done” is no longer “dev-
complete”, but is thoroughly
validated as only a release can.
#3 Delivers “real” progress

18. HOW DO I FIT CD
INTO MY AGILE
PROJECT?
18

19. An Agile release
How do I fit CD
into my
Agile project?
Each release
comprises of
multiple iterations

20. How do I fit CD
into my
Agile project?
Each iteration
comprises of
multiple stories
An Agile release

21. How do I fit CD
into my
Agile project?
Each story
comprises of
multiple commits
An Agile release

22. How do I fit CD
into my
Agile project?
Each release is thus a series
of multiple commits
An Agile release

23. An Agile release…with CD appliedHow do I fit CD
into my
Agile project?
With CD, that is reversed.
Each commit is now a potential
release candidate

24. Thus releasing now is a business
decision
How do I fit CD
into my
Agile project?
Release on Demand

25. Caution!How do I fit CD
into my
Agile project?
Have your checks in place, as any
commit could go live

26. How do I fit CD
into my
Agile project?
Iterations should not be time-boxed,
mini-waterfalls
Caution!

27. How do I fit CD
into my
Agile project? Iterations should not be time-boxed,
mini-waterfalls…
That require stories to be re-ordered
Caution!

28. How do I fit CD
into my
Agile project?
Instead “Continuous” iterations serve
only as checkpoints
Caution!

29. HOW DO I MANAGE
MY CODEBASE?
29
Stay tuned for Part 2…

30. LEARN MORE
Deploy a great product faster.
Agile teams deliver working software early and
often.
Go automates and streamlines the build-test-
release cycle for worry-free, continuous delivery
of your product.
Share this ebook.
Visit our Continuous Delivery Channel for more
posts like this.