DAD is a new-generation framework that provides developers with a comprehensible, end-to-end methodology for the delivery of agile solutions. More importantly, DAD is a user-oriented agile approach that promotes learning in the development lifecycle. It uses a risk-value cycle, which is goal-driven and easily scalable.
Disciplined Agile Delivery functions as a hybrid methodology that implements proven methods like Extreme, Scrum, Agile Modelling (AM), Agile Data (AD), etc., into a single practice. So instead of beginning a process with a kernel like Extreme or Scrub, and then adding on techniques and practices, it combines all of them, which can be an extremely useful tool for a team. In short, DAD promises to take all of the hassle and time out of combining agile techniques.
What does DAD do Differently?
An Enterprise Team
Dad moves beyond Scrum. When developers work at scale, they simply can’t afford to have different members of a team working on their own, even if they are actually using their time in a productive manner. The truth is that agile teams do not work in a vacuum.
Several teams work in parallel to each other, and an enterprise needs to take advantage of what those teams are doing at any given moment. An organization is usually working towards a common goal or vision; one that the entire team should contribute too. DAD disciplines agile teams, and forces them to recognize that they are part of a larger organization.
Focus on Solutions
DAD allows a group to focus not only producing software, but also on providing consumable solutions, which provide real business values to stakeholders. Producing good software is important, but meeting the needs of stakeholders is probably more crucial to the overall structure of the organization. When working at scale, it’s not enough for developers to deliver potentially marketable software. DAD allows groups to focus on the end-solutions of their projects.
According to Scott Amber, the creator of Disciplined Agile Delivery, the regular DAD lifecycle begins with the initiation of a project, goes through all the steps of construction, and ends with production, and then post-delivery production activities. This is quite different from first generation agile methods, which generally focus on the construction aspects of a cycle, and leave the rest to fate.
The basic DAD lifecycle is an improved version of the construction portion of the Scrum lifecycle. DAD uses lightweight milestone reviews at the end of their lifecycles, and its non-prescriptive aspect removes some of the constraints that Scrum brings when it comes to delivery focus.
Manage Stakeholder Needs
Every team’s specific situation is different. Scaling can often bring several risk factors into an agile development. DAD addresses these obstacles by taking a process and goal-driven approach, which forces teams to reflect on the context of their situations. So instead of organizing work as a stack of prioritized values, which is what Scrum directs us to do, DAD prioritizes stakeholder needs above all else.
DAD’s goal-driven approach provides agile teams with the discipline and guidance that they in order to get scaling correct.