Implementing Continuous Product Delivery
•
0 gefällt mir•863 views
This document discusses continuous delivery (CD), which is a software development practice that automates and improves the process of software delivery. With CD, software can be developed to a high standard and easily packaged and deployed to test environments, allowing software enhancements and bug fixes to be rapidly and repeatedly pushed out to customers at low risk. The document advocates for CD in order to get products to customers faster, reduce disruption from bugs, increase product value, and improve stakeholder happiness. It also discusses related concepts like agile development, Kanban, and feature flags.
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (19)
Andere mochten auch
Ähnlich wie Implementing Continuous Product Delivery
Ähnlich wie Implementing Continuous Product Delivery (20)
Mehr von Jeremy Horn
Mehr von Jeremy Horn (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Implementing Continuous Product Delivery
- 1. Implementing Continuous Product Delivery @MattRogish mattrogish.com The Product Mentor
- 2. About Me • Programmer (Ruby on Rails), DBA • CTO / Dir. Product • Consultant • Founder
- 3. Continuous Delivery Continuous Delivery (CD) is a design practice used in software development to automate and improve the process of software delivery. Techniques such as automated testing, continuous integration and continuous deployment allow software to be developed to a high standard and easily packaged and deployed to test environments, resulting in the ability to rapidly, reliably and repeatedly push out enhancements and bug fixes to customers at low risk and with minimal manual overhead. The technique was one of the assumptions of extreme programming but at an enterprise level has developed into a discipline of its own, with job descriptions for roles such as "buildmaster" calling for CD skills as mandatory.
- 4. tl;dr Any code commit may be released to customers at any point
- 5. Why? • Get product to customers and stakeholders faster • Reduce disruption caused by bugs • Product is more valuable • Makes everyone happier
- 7. The Bad Old Days
- 12. Waterfall • Process resistant to change • Releases take forever • Assumes too much
- 13. Assumptions • People Risk • Process Risk • Product Risk
- 14. What’s More Valuable? • Project A will eventually cost about a million dollars and produce value of around $1.1 million • Project B will eventually cost about a million dollars and produce value of more than $50 million
- 15. Tom DeMarco To my mind, the question that’s much more important than how to control a software project is, why on earth are we doing so many projects that deliver such marginal value?
- 16. Agile
- 18. Agile ! • Minimize assumptions/risk • Iterate, iterate, iterate • High degree of test coverage, CI, refactoring, retrospectives, etc. • Continuous improvement
- 20. Kanban
- 25. Inventory = Muda • Feature Backlogs • Undeployed Features • Unfixed Bugs
- 26. Inventory = Muda • Feature Backlogs • Undeployed Features • Unfixed Bugs
- 28. Kanban • Continuous one-piece pull-based flow • Minimize inventory/waste • Features are released when finished • Pulled from Toyota Production System
- 29. Feature Flags Kanban Agile Continuous Delivery Agile Continuous Delivery Kanban Agile Continuous Delivery
- 30. Feature Flags
- 36. Feature Flag • Turn features on and off in code • Toggle for particular users, groups, or environments • Can turn off if something blows up • Give marketing control
- 38. Lean
- 42. Why? • Get product to customers and stakeholders faster • Reduce disruption caused by bugs • Product is more valuable • Makes everyone happier
- 44. Why? • Get product to customers and stakeholders faster • Reduce disruption caused by bugs • Product is more valuable • Makes everyone happier
- 45. Implementing Continuous Product Delivery @MattRogish mattrogish.com The Product Mentor