In February 2001, 17 software developers met at the Snowbird, Utah resort, to discuss lightweight development methods. They published the Manifesto for Agile Software Development. Of the principles identified in the manifesto, one in particular stands out:
Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
This statement sounds great in theory, but putting it into practice has been a challenge for the industry. Jez Humble published the book Continuous Delivery in 2010 with guidance that distilled over a decade of industry struggles to translate the Agile manifesto into concrete practices that make frequent releases a reality.
Facebook, Yahoo, and Etsy are some examples of feedback-driven organizations that transformed into market powerhouses by using the information Jez and others in the industry provided to their advantage. What made these organizations successful in implementing Continuous Delivery was not a huge pot of cash, but rather a commitment to become focused on continuous improvement and rejecting some of the myths of product development that would prevent them from innovating in the time frame necessary to lead their market.
With years of experience coaching and leading teams to follow agile product development practices, I began in 2012 to put Continuous Delivery to work for my clients in Austin, Texas with great success. Teams are tired of pretending that things are working smoothly and can’t afford to be leapfrogged in their market when they constrain themselves to long release cycles where their customers are not an integrated partner in their success. I created Delivery Acceleration as a way to help clients understand what would need to change from how they are doing work today, how they can go about it using technology, and how to plan for incremental rolling out of Continuous Delivery across the teams in their organization.
Read all of my posts about Continuous Delivery below:
- Burn-Down Charts: The Silent Value Killer (6/1/2016)
- IT deployment standards: why now? (9/30/2014)
- Selecting a Deployment Pipeline: 10 Considerations (9/25/2014)
- Continuous Delivery is about failing faster (9/16/2014)
- Tips for Estimating Continuous Delivery (9/9/2014)
- How frequent releases help you satisfy and retain your best employees (8/27/2014)
- Top 5 business myths about Continuous Delivery (8/21/2014)
- Overcoming your quality debt to enable continuous delivery (7/16/2012)
- Put all your environment-specific configuration in one place for a pleasant troubleshooting experience (4/24/2012)
- Pay off your technical debt by preferring API clarity to generation efficiency (4/17/2012)
- Why continuously deliver software? (4/16/2012)
- Refactoring to the realities of your delivery process (4/12/2012)
- Forgotten oracles – is fortune telling controlling your value stream’s destiny? (4/11/2012)
- When you make production an island, it takes a long time to get there (4/10/2012)
- Cycle time – the important statistic you probably aren’t measuring (4/9/2012)
- Foregoing assumed value in favor of rapid feedback (3/30/2012)