Upload
ebin-john-poovathany
View
148
Download
2
Embed Size (px)
DESCRIPTION
This is presented in Scrum Bangalore Meet-up
Citation preview
Continuous Delivery : For Fast and Consistent Value
Ebin John [email protected]
http://in.linkedin.com/in/ebinjp
About me
Check-in : Expectations
Story for Today
• Continuous Delivery
• Why
• How
• What
Value Stream Mapping
5
Total lead time 2206 hours
Value added time267 hours
Efficiency12%
http://en.wikipedia.org/wiki/Value_stream_mapping
How do we deliver!
Users PO BA Architect, Tech Lead Dev Test BA PO Production Users
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
Is this new for us?
Our Principles
Our Principles
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 control5.Done means “released”.6.Build quality in!7.Everybody has responsibility for the release process.8.Improve continuously.
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!
Deployment pipeline
http://en.wikipedia.org/wiki/Continuous_delivery
SummaryAre we Agile without Continuous Delivery?
Questions & Answers