Boundless Continuous Delivery
0 likes374 views
This document discusses the benefits of continuous deployment including single ownership over projects from conception to deployment, no arbitrary choke points or delays, faster iteration and learning, and empowering developers. It also outlines how to implement continuous deployment using Kanban via Trello for workflow management, Jenkins for continuous integration, and a publicly visible auto-updating change log.
Related topics:1 of 5
Download to read offline
More Related Content
What's hot (20)
Ad
Viewers also liked (20)
Ad
Similar to Boundless Continuous Delivery (20)
More from MassTLC (20)
Boundless Continuous Delivery
- 1. Boundless Learning - Continuous Deployment
- 2. Why? ➡ Single owner takes something from the conception to deployment. (And if it isn t deployed, it doesn t exist) ➡ No arbitrary choke -points ➡ No delayed value, no lost momentum. ➡ Faster iteration, faster learning, greater odds for success/value. ➡ Developers are more empowered and thus take more ownership over infrastructure ➡ Quickly forces automated testing (this is a good thing) CONFIDENTIAL > Boundless > (date) 2
- 3. How: Kanban via Trello CONFIDENTIAL > Boundless > (date) 3
- 4. How: Jenkins for Continuous Integration CONFIDENTIAL > Boundless > (date) 4
- 5. How: " " Publicly-visible " auto-updating " change-log CONFIDENTIAL > Boundless > (date) 5