Why DAD?

The Disciplined Agile Delivery (DAD) process decision framework  is a people-first, learning-oriented hybrid agile approach to IT solution delivery. It has a risk-value delivery lifecycle, is goal-driven, is enterprise aware, and is scalable.  There are several reasons why you should consider adopting the DAD framework.  They are:

  1. DAD picks up where Scrum leaves off.  The DAD framework describes how all agile techniques fit together, going far beyond Scrum, to define a full agile solution delivery lifecycle. Like Scrum the DAD framework addresses leadership, roles & responsibilities, and requirements change management.   Unlike Scrum DAD doesn’t stop there, it also addresses other important aspects of software development such as architecture, design, testing, programming, documentation, deployment and many more.  In short, DAD provides a much broader understanding of how agile development works in practice, doing a lot of the “heavy process lifting” that Scrum leaves up to you.
  2. DAD is pragmatic.  The DAD framework provides guidance, not prescriptions, enabling you to easily tailor a strategy that reflects the situation that your team finds itself in.  To do this effectively you need to understand the process-oriented choices you have and what the trade-offs are.  The DAD framework makes these choices explicit through its process-goal driven approach.
  3. DAD supports both lean and agile ways of working.  The DAD framework supports several delivery lifecycles, including a Scrum-based agile lifecycle, a Kanban-based lean lifecycle, a continuous delivery lifecycle, and a Lean Startup-based exploratory lifecycle.  Teams find themselves in unique situations, and as a result one process size does not fit all.  Even in small companies we’ve seen situations where some teams are taking an agile approach, some a lean approach, and some combinations thereof.  One process size does not fit all.
  4. DAD is based on empiricism.  For several years Scott Ambler, Mark Lines, and many other contributors to DAD worked in or visited hundreds of enterprises around the world in a wide range of industries and environments.  The DAD framework captures the proven strategies adopted by these organizations, describing the strengths and weaknesses of each strategy and providing guidance for when and when not to apply them.
  5. DAD provides a solid foundation from which to scale agile.  The DAD framework supports successful scaling of agile and lean techniques in several ways.  First, its full delivery lifecycles and breadth of software development advice answers how to successfully apply agile in practice.  Second, its goal driven approach provides the required flexibility for tailoring your agile process to meet the challenges faced by agile teams working at scale.  Third, the DAD framework builds in many foundational concepts required at scale, including DevOps, explicit agile governance, and enterprise awareness.
  6. DAD enables SAFe.  SAFe leaves the details of construction to you and as a result can prove to be fragile in many organizations.  DAD provides the solid process foundation missing from SAFe and is in fact complementary to SAFe.
  7. DAD goes beyond SAFe.  The DAD framework describes several strategies for organizing large or geographically distributed teams.  It describes a range of options for scaling your approach to agile and lean software development, giving you context-sensitive options that SAFe doesn’t.
  8. DAD teams deliver solutions, not just software.  DAD recognizes that the software we develop runs on hardware, which may need upgrades, and it is supported by documentation.   Our stakeholders may also need to evolve their business processes, and sometimes even their organization structures, to address the new needs of the situation that they face.  In short, DAD teams deliver solutions that comprise software, hardware changes, supporting documentation, improved business processes, and even organizational changes.
  9. DAD is evolving.  We’re constantly learning as practitioners, learning about and experimenting with new agile and lean strategies all of the time.  These learnings are constantly being applied to evolve the DAD framework.

 

2 thoughts on “Why DAD?

  1. Carolina S T

    Hi!! Lifecycle from OpenUp is very closer to DAD, except the Elaboration phase. But I could find steps from elaboration on Construction phase. So, what exactly is the main advantage of using DAD and not OpenUp? Both OpenUp or DAD can be used when adopting a DevOps culture? Dad has an advantage on DevOps? Tks a lot!!

    Reply
  2. scottwambler

    Several things:
    1. DAD reflects more modern, agile thinking that OpenUP does (I was one of the original contributors to OpenUP).
    2. DAD supports several life cycles, not just one.
    3. DAD is more streamlined (as you point out, there’s one less phase).
    4. DAD is lighter weight.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *