I will be doing a webcast on DAD for InformationWeek on Tue, July 10 at 10:00 PDT. If you are interested you can register here.
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.
This short video of an interview with Scott on the Disciplined Agile Delivery (DAD) book is worth the look:
There are some differences as well as some similarities when comparing agile adoption to agile transformation. Which does the DAD book address? One or the other, or both? I know that I have my opinion, but I am interested in yours. Add your comments and let us know what you think. Then we can discuss.
I think that this blog has been quite successful in getting the word out about Disciplined Agile Delivery (DAD) and describing key aspects of the framework in advance of the book being released. However, now that the book is out, it makes sense to evolve the blog into a forum for deeper discussions about DAD. Scott and I would also like to use it as a medium to answer detailed questions about anything from the book.
Anyone who supports DAD is encouraged to become a contributor to be able to blog a new topic for discussion. If you wish to become a contributor, send me a note at Mark@UPMentors.com
If you don’t wish to become a contributor directly but have a DAD question, send the question to me and I will post it for discussion. Thanks!