A Continuous Delivery Maturity Model

Grand Ballroom - Salon C

How mature are your Continuous Delivery and Release practices? Where can you get the most improvement based on your specific problems and needs? How are other organizations solving these same problems?In recent years the role of automation in software development has expanded dramatically. The collision of the Agile practice of Continuous Delivery withthe realities of enterprise development projects where large projects, distributed teams or strict governance requirements are not aberrations has resulted in increased automation efforts throughoutthe lifecycle. Continuous Delivery requires a cultural transformation as well and feeds into the growing DevOps movement. Top performing teams have the culture and automation in place that enables them to deliver changes faster with higher quality, and with more control for less effort.However, adoption of automation has been uneven. There are many paths to improving your development automation efforts, but where to start? When seeking these benefits, it is useful to have a guide.In this talk, Eric presents a simple model for scoring the maturity of your organizations efforts across Build, Deployment, Testing, and Release. This model is based on several years of first-hand experience with hundreds of teams and reports from the field. With this model you understand the industry norms so you know where youre keeping up andwhere you're falling behind.

Eric Minick's picture
Eric Minick is a lead consultant at UrbanCode where he helps customers implement continuous delivery. Eric has been at the forefront of Continuous Integration and Delivery for 8+ years as a developer, tester and consultant.