As you know the Disciplined Agile (DA) toolkit supports several delivery lifecycles – Agile, Lean, Continuous Delivery: Agile, Continuous Delivery: Lean, Exploratory, and Program. We do this because solution delivery teams face different situations, so one lifecycle will not fit all. This begs the question of when would a team adopt each lifecycle? That is the focus of this blog.
This blog explores the following topics:
What Lifecycles Does DAD Support?
The delivery lifecycles we will explore are:
What Criteria Should You Consider When Choosing a Lifecycle?
The following table compares the lifecycles, suggesting when you would choose to follow each one.
Who Should Choose the Lifecycle?
They will often do this with the guidance of an experienced Disciplined Agile coach, particularly when they are new to DA. It’s tempting to have your portfolio management team to make this choice, and they may often make a (hopefully solid) suggestion when the first initiated an endeavour, but in the end it needs to be the choice of the team. As you see in the table above there are common considerations for when to use each lifecycle, but the primary considerations are always the skill and preferences of the team itself.
Disciplined Agile Delivery (DAD) is a hybrid framework that builds upon the solid foundation of other methods and software process frameworks. The DA toolkit adopts practices and strategies from existing sources and provides advice for when and how to apply them together. In one sense methods such as Scrum, Extreme Programming (XP), Kanban, and Agile Modeling (AM) provide the process bricks and DAD the mortar to fit the bricks together effectively.
The DA toolkit adopts strategies from the following sources:
One of the great advantages of agile and lean software development is the wealth of practices, techniques, and strategies available to you. This is also one of its greatest challenges because without something like DAD it’s difficult to know what to choose and how to fit them together.