The presentation gives high-level overview of most important aspects of implementing Continuous Delivery comparing CD with Agile, DevOps and Lean software development.
2. Our common goal
• Give customer what they want
• When they want
• At the lowest costs possible
• Quickly, cheaply and reliably implement ideas for customers and
receive feedback.
3. One in six IT projects have an average cost overrun of 200% and a
schedule overrun of 70%. (Harvard Business Review, 2011)
75% of business and IT executives anticipate their software projects will
fail. (Geneca, 2011)
Fewer than a third of all projects were successfully completed on time
and on budget over the past year. (Standish Group, 2013)
5. Last mile problem
• Streamlined value delivery from left to right
• We need to remove the wall of separation between development/QA
and Production.
OperateLast mile
9. Principles of CD
• Create repeatable and reliable process for releasing software
• Keep everything in the source control
• Automate (almost) everything
• Build quality in
• Redefine ‘Done’ to mean released
• Make everybody responsible for the release process
• Implement continuous improvements
17. Principles of CD
• Create repeatable and reliable process for releasing software
• Keep everything in the source control
• Automate (almost) everything
• Build quality in
• Redefine ‘Done’ to mean released
• Make everybody responsible for the release process
• Implement continuous improvements
18. Continuous Delivery vs
Continuous Deployment
• Possibility to aggregate changes in preproduction
• Possibility to deploy every change/commit
26. How to start?
• Agile development
• Continuous Integration
• Infrastructure automation
• Automated testing
• Automated deployments
• Shared tools and procedures
• Shared goals and communication
35. Conway’s law
Organizations which design systems ... are constrained to produce
designs which are copies of the communication structures of these
organizations.
—Melvin Conway
If the architecture of the system and the architecture of the
organization are at odds, the architecture of the organization wins.
—Ruth Malan
42. Process perspective
• Workflow
• Each step – repeatable
• No defects go further
• No local optimizations that degrade overall performance
• Increase the flow, analyze and optimize
• Reduce the batch size
• Improve at the bottleneck
Inception Plan Develop Integrate Testing Release Operate
44. Lean software development
• Deliver as fast as possible
• Build quality in
• Optimize for the whole
• Eliminate waste
• Amplify learning
• Decide as late as possible
• Empower the team
49. Lean startup/enterprise
1. Make a guess based on experience and observation.
2. Propose an explanation - hypothesis.
3. Make a prediction from the hypothesis.
4. Test the prediction.
5. Repeat!