1. Continuous Delivery :
For Fast and Consistent Value
Ebin John Poovathany
ebinjp@hotmail.com
http://in.linkedin.com/in/ebinjp

2. About me

3. Check-in : Expectations

4. Story for Today
• Continuous Delivery
• Why
• How
• What

5. Value Stream Mapping
5
Total lead time
2206 hours
Value added time
267 hours
Efficiency
12%
http://en.wikipedia.org/wiki/Value_stream_mapping

6. How do we deliver!
Users PO BA
Architect,
Tech Lead
Dev Test BA PO
Productio
n
Users

7. Build software that is
production ready at all times
Continuous Delivery
Frequent, low risk
releases
Faster Time to
Market
Fast feedback,
visibility and
control
Built-in Software
Quality
Reduce Risk

8. Is this new for us?

9. Our Principles

10. Our Principles

11. Principles of continuous delivery
1.The process for releasing/deploying software MUST be
repeatable and reliable.
2.Automate everything!
3.If something is difficult or painful, do it more often.
4.Keep everything in source control
5.Done means “released”.
6.Build quality in!
7.Everybody has responsibility for the release process.
8.Improve continuously.

12. 4 Practices of Continuous Delivery
1. Build binaries only once
2. Use precisely the same mechanism to deploy to every
environment
3. Smoke test your deployment
4. If anything fails, stop the line!

13. Deployment pipeline
http://en.wikipedia.org/wiki/Continuous_delivery

14. Summary
Are we Agile without Continuous Delivery?

15. Questions & Answers

16. Thank You 
Ebin John Poovathany
ebinjp@hotmail.com
http://in.linkedin.com/in/ebinjp