Just a delivery lifecycle?
I was recently asked a question around the scope of the DAD lifecycle and thought that I would share my answer publicly.
The focus of DAD is the delivery portion of the solution lifecycle, from initiation to delivery into production (or the marketplace in the case of a commercial product). Any given solution will go through the delivery portion of the lifecycle many times during it’s existence as releases are put into production.
BUT, this isn’t the entire solution lifecycle. For example:
- There are some portfolio management activities before a project starts such as project identification and selection that are outside the scope of DAD. We show this as input into the DAD lifecycle to help provide context.
- There are also post-delivery activities, particularly operations and support, that are part of the overall solution lifecycle but outside of the delivery portion of the lifecycle. In DAD we explicitly show feedback coming back from the production portion of the solution lifecycle because this is a common occurrence.
Note that these comments apply to both the basic (Scrum-like) version of the lifecycle as well as the advanced/lean version. Because DAD explicitly recognizes that your process improvement activities will include changes that affect the lifecycle, we don’t enforce a single DAD lifecycle.