# Disciplined agile delivery

Disciplined agile delivery (DAD) is the software development portion of the Disciplined Agile Toolkit. DAD enables teams to make simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including scrum, agile modeling, lean software development, and others.
The primary reference for disciplined agile delivery is the book Choose Your WoW!, written by Scott Ambler and Mark Lines. WoW refers to "way of working" or "ways of working".
In particular, DAD has been identified as a means of moving beyond scrum. According to Cutter Senior Consultant Bhuvan Unhelkar, "DAD provides a carefully constructed mechanism that not only streamlines IT work, but more importantly, enables scaling." Paul Gorans and Philippe Kruchten call for more discipline in implementation of agile approaches and indicate that DAD, as an example framework, is "a hybrid agile approach to enterprise IT solution delivery that provides a solid foundation from which to scale."

## History

Scott Ambler and Mark Lines initially led the development of DAD, and continue to lead its evolution. DAD was developed to provide a more cohesive approach to agile software development; one that tries to fill in the process gaps that are (purposely) ignored by scrum, and one that is capable of enterprise-level scale. According to Ambler, "Many agile methodologies—including scrum, XP, AM, Agile Data, kanban , and more—focus on a subset of the activities required to deliver a solution from project initiation to delivery. Before DAD was developed, you needed to cobble together your own agile methodology to get the job done."
DAD was developed as a result of observing common patterns where agility was applied at scale successfully.
In 2015 the Disciplined Agile (DA) framework, later to become the Disciplined Agile Toolkit, was developed. This was called Disciplined Agile 2.x. DAD formed the foundation for DA. A second layer, disciplined DevOps, was added as was a third layer called Disciplined Agile IT (DAIT). These layers, respectively, addressed how to address DevOps and IT processes in an enterprise-class setting.
Disciplined Agile 3.x was released in August 2017 to introduce a fourth layer, Disciplined Agile Enterprise (DAE), to address the full process range required for business agility.
In December 2018, Disciplined Agile 4, now referred to as the Disciplined Agile Toolkit, was released. It focused on a completely revamped description of DAD and a team-based improvement strategy called guided continuous improvement (GCI).
In August 2019, Disciplined Agile was acquired by Project Management Institute.

## Key aspects

Many of the challenges that teams are facing are out of scope for scrum and the teams need to look to other methods with overlapping parts and conflicting terminology. DAD attempts to address these challenges by using a people-first, learning-oriented, hybrid approach to IT solution delivery.

### People-first

Disciplined agile delivery (DAD) identifies that "People, and the way they interact with each other, are the primary determinant of success for a solution delivery team." DAD supports a robust set of roles (see below section), rights, and responsibilities that you can tailor to meet the needs of your situation. DAD promotes the ideas that team members should collaborate closely and learn from each other, that the team should invest effort to learn from their experiences and evolve their approach, and that individuals should do so as well.

### Hybrid

DAD is a hybrid toolkit that adopts and tailors proven strategies from existing methods such as scrum, extreme programming (XP), SAFe, agile modeling (AM), Unified Process (UP), Kanban , outside-in software development, agile data (AD) and Spotify's development model. Rather than taking the time to adapt one of these existing frameworks, with DAD all of the effort of combining relevant pieces of each technique has already been done.

### Full delivery lifecycle

Unlike first generation agile methods that typically focus on the construction aspects of the lifecycle, DAD addresses the full delivery lifecycle, from team initiation all the way to delivering a solution to your end users.

### Support for multiple lifecycles

DAD supports six lifecycles to choose from: agile, lean, continuous delivery, exploratory, and large-team versions of the lifecycle. DAD does not prescribe a single lifecycle because it recognizes that one approach does not fit all.

### Complete

DAD shows how development, modeling, architecture, management, requirements/outcomes, documentation, governance and other strategies fit together in a streamlined whole. DAD does the "process heavy lifting" that other methods leave up to you.

### Context-sensitive

The approach is goal-driven or outcome-driven rather than prescriptive. In doing so, DAD provides contextual advice regarding viable alternatives - what works, what doesn't and more importantly why - and their trade-offs, enabling you to tailor your way of working to address the situation in which you find yourself and do so in a streamlined manner.

### Consumable solutions over working software

DAD matures focus from simply producing software to providing consumable solutions that provide real business value to stakeholders. While software is clearly an important part of the deliverable, being solution focused means taking a holistic view of the overall problem. This can lead to suggested updates in hardware, business and organizational processes, and overall organizational structures.

### Self-organization with appropriate governance

Agile and lean teams are self-organizing, which means that the people who do the work are the ones who plan and estimate it. They must still work in an enterprise aware manner that reflects the priorities of their organization, and to do that they will need to be governed appropriately by senior leadership.

## Lifecycles

Disciplined originally supported an agile (scrum-based) project lifecycle and a Lean (Kanban-based) project lifecycle. It has since been extended to support six lifecycles:
* Agile. A three-phase project lifecycle based on scrum. The phases are Inception (what is sometimes called "Sprint 0"), Construction, and Transition (what is sometimes called a Release sprint).
* Lean. A three-phase project lifecycle based on Kanban.
* Continuous delivery: Agile. An Agile-based product lifecycle that supports a continuous flow of work resulting in incremental releases (typically once a week).
* Continuous delivery: Lean. A lean-based product lifecycle that supports a continuous flow of work.
* Exploratory. An experimentation-based lifecycle based on lean startup that has been extended to address the parallel development of minimum viable products as per the advice of cynefin.
* Program. A lifecycle for coordinating a team of teams.

## Process goals

DAD is described as a collection of twenty-one process goals, or process outcomes. These goals guides teams through a leaner process to decisions that address the context of the situation they face. It enables teams to focus on outcomes and not on process compliance and on guesswork of extending agile methods. It enables scaling by providing sophisticated-enough strategies to address the complexities you face.
| Inception phase | Construction phase | Transition phase |
| Get the team going in the right direction. | Incrementally build a consumable solution. | Release the solution into production. |
| Form Team Align with enterprise direction Develop common project vision Explore scope Identify architecture strategy Plan the release Develop test strategy Develop common vision Secure funding | Prove architecture early Address changing stakeholder needs Produce potentially consumable solution Improve quality Accelerate value delivery | Ensure production readiness Deploy the Solution |
| Ongoing goals |||
| Improve and work in an enterprise aware manner. |||
| Grow team members Coordinate activities Address risk Evolve ways of working (WoW) Leverage and enhance existing infrastructure Govern delivery team |||

## Roles
### Primary roles

These five primary roles in the disciplined agile delivery are typically found regardless of scale.
* Stakeholder. Someone who is materially impacted by the outcome of the solution. More than just an end-user or customer, this is anyone potentially affected by the development and deployment of a software project.
* Product owner. The person on the team who speaks as the "one voice of the customer", representing the needs of the stakeholder community to the agile delivery team.
* Team member. The team member focuses on producing the actual solution for stakeholders, including but not limited to: testing, analysis, architecture, design, programming, planning, and estimation. They will have a subset of the overall needed skills and they will strive to gain more to become generalizing specialists.
* Team lead. The team lead is a host leader and also the agile coach, responsible for facilitating communication, empowering them to choose their way of working, and ensuring the team has the resources it needs and is free of obstacles.
* Architecture owner. Owns the architecture decisions for the team and facilitates the creation and evolution of the overall solution design.

### Potential supporting roles

These supporting roles are introduced (sometimes on a temporary basis) to address scaling issues.
* Specialist. Although most agile team members are generalizing specialists, sometimes other specialists are required depending on the needs of the project.
* Domain expert. While the product owner represents a wide range of stakeholders, a domain expert is sometimes required for complex domains where a more nuanced understanding is required.
* Technical expert. In cases where a particularly difficult problem is encountered, a technical expert can be brought in as needed. These could be build-masters, agile database administrators, user experience (UX) designers, or security experts.
* Independent tester. Although the majority of testing is done by the DAD team members, in cases with complex domains or technology an independent testing team can be brought in to work in parallel to validate the work.
* Integrator. For complex technical solutions at scale, an integrator (or multiple integrators) can be used to build the entire system from its various subsystems.