DAD Lifecycle – Continuous Delivery: Agile

DAD lifecycle - Continuous Delivery:Agile

The Continuous Delivery: Agile lifecycle is a natural progression from the Agile lifecycle. Teams typically evolve to this lifecycle from the Agile lifecycle, often adopting iteration lengths of one-week or less. The key difference between this and the Agile lifecycle is that the continuous delivery lifecycle results in a release of new functionality at the end of each iteration rather than after a set of iterations. Teams require a mature set of practices around continuous integration and continuous deployment and other Disciplined DevOps strategies.

Figure: DAD’s Continuous Delivery: Agile lifecycle (click to expand).

Lifecycle - DAD Agile Continuous Delivery 

When to Apply This Lifecycle

The Continuous Delivery: Agile lifecycle is suitable when:

  • Solutions that can be delivered to stakeholders in a frequent and incremental basis
  • Work remains relatively stable within an iteration
  • Organizations with streamlined deployment practices and procedures
  • Projects where getting value into the hands of stakeholders rapidly, before the entire solution is complete, is critical
  • Teams have mature DevOps practices in place including continuous integration, continuous deployment, and automated regression testing
  • The team is long-lived (stable), working on a series of releases over time

Get a Poster

Would you like a printable poster of this lifecycle? Disciplined Agile Consortium (DAC) members can download a printable PDF file.