Continuous Delivery Speeds Up Innovation
Thoughtworks recently published a whitepaper including a maturity model for continuous delivery (or CD) as a response to research indicating that most companies understand the importance of innovation, but are not able to deliver software quickly enough to meet the needs of business leaders. The white paper explains that the low level of continuous delivery maturity within companies prevents their software development teams from being strategic partners and makes their software releases slower than needed by their businesses.
Thoughtworks intends for companies to use the maturity model to identify gaps in their processes and tools so they can focus on improving those areas. They believe that continuous delivery is the solution to improving the productivity of software development to the point of exceeding expectations and in turn creating the capabilities within technology departments so that they can play a critical role in the strategic direction of their companies. The following levels and results are explained in detail within the white paper:
- 5: Optimizing - Continuous deployment capability enables business innovation/experimentation
- 4: quantitatively managed - Release on demand: Software is always in a releasable state. Release time box is well defined and equal to, or less than, business need.
- 3: defined - Regular release candence: Release time box is well defined, but duration from idea inception to production release is greater than business need.
- 2: managed - Planned release: Release time box is well defined, but duration from idea inception to production release is greater than business need.
- 1: initial - Ad hoc deployments
Difference between level 2 and level 3
Shane Hastie on Distributed Agile Teams, Product Ownership and the Agile Manifesto Translation Program
Shane Hastie Apr 17, 2015