Jan 282014
 

Many organizations start their Agile journey by adopting Scrum because it describes a good strategy for leading Agile software teams. Scrum, however, is only part of what is required to deliver sophisticated solutions to your stakeholders. Invariably, teams need to look to other methods to fill in the process gaps that Scrum purposely ignores. When looking at other methods, there is considerable overlap and conflicting terminology that can be confusing to practitioners as well as outside stakeholders. Worse yet, people don’t always know where to look for advice or even what issues they need to consider.

To address these challenges, the DAD process decision framework provides a more cohesive approach to Agile solution delivery (see Disciplined Agile Delivery: A Practitioner’s Guide to Agile Software Delivery in the Enterprise). To be more exact, here’s our definition of 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.

DAD provides a foundation from which to scale because it:

  • Addresses the full delivery lifecycle. DAD recognizes that projects go through some startup activities as well as the work involved in transitioning the solution to stakeholders.
  • Is a hybrid of good ideas. DAD adopts proven practices from methods such as Scrum, XP, Agile Modeling, and Kanban, to name a few. DAD shows how practices for management, testing, architecture, programming, continuous integration, deployment, and other practices fit together.
  • Is goal-driven. We have found that process-related goals are fairly consistent across most types of projects. However, context is inevitably different, so DAD provides easy-to-consume guidance for how to adapt to the unique situations that you will face.

Of all these aspects of DAD, our experience is that adopting a goal-driven approach is the one that most organizations have missed in their attempts to successfully scale Agile solution delivery.

Discussion

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)