Disciplined Agile (DA)

What is Disciplined Agile (DA)?

Disciplined Agile (DA) is a toolkit, created by Scott Ambler and Mark Lines and now owned by PMI, that helps teams and organizations choose their own way of working from options drawn from Scrum, Kanban, lean, XP and other methods.

Updated November 2026 · 3 min read


Disciplined Agile (DA) is a toolkit for choosing and tailoring a team's or organization's way of working, rather than a single prescribed method. It draws practices from Scrum, Kanban, Extreme Programming, lean, SAFe and other sources, organizes them around the goals a team needs to achieve, and helps teams pick the options that fit their situation. Its central idea is that context counts: a regulated bank, a startup and a government agency should not all run the same process.

DA was created by Scott Ambler and Mark Lines. It began as Disciplined Agile Delivery (DAD), described in their 2012 book Disciplined Agile Delivery: A Practitioner's Guide to Agile Software Delivery in the Enterprise, and later grew to cover IT, business functions and the wider enterprise. The Project Management Institute (PMI) acquired Disciplined Agile in 2019 and took over its content, training and certifications.

Principles of disciplined Agile

DA is built on a set of principles that explain why it favors choice over prescription:

  • Delight customers. Aim beyond meeting requirements.
  • Be awesome. Build teams people want to be part of.
  • Context counts. Every team faces a different situation and should work accordingly.
  • Be pragmatic. Aim to be as effective as possible, not as "agile" as possible.
  • Choice is good. Teams need several options to pick from, and need to understand the trade-offs.
  • Optimize flow. Look at how work moves across the whole organization, not only inside one team.
  • Organize around products and services. Structure teams around what customers value.
  • Enterprise awareness. Teams should consider the organization's broader goals, standards and shared assets.

Lifecycles and phases

For delivery teams, DA describes several lifecycles instead of one. They include an agile lifecycle based on Scrum, a lean lifecycle based on Kanban, continuous delivery variants of both for mature teams, an exploratory lifecycle based on lean startup experiments, and a program lifecycle for coordinating a team of teams. Most of them pass through three phases:

PhasePurposeTypical activities
InceptionGet going in the right directionForm the team, agree initial scope and architecture, secure funding, identify risks
ConstructionBuild a consumable solutionProduce working increments, address changing needs, improve quality
TransitionRelease into productionFinal testing, deployment, training and handover to users and operations

Goal-driven tailoring

DA organizes its guidance into process goals, such as "explore scope," "improve quality" or "coordinate activities." For each goal, a goal diagram lists decision points and the options available, along with their trade-offs. A team exploring scope might choose between a light requirements envisioning session, detailed specifications or a lean canvas, depending on its risk and regulatory context. This is what DA means by "choose your way of working," the phrase PMI uses for its main DA book.

Disciplined Agile in practice: A hypothetical example

Consider a hypothetical insurance company with three teams starting new work at the same time:

  • A claims-portal team with an established backlog and monthly releases chooses the Scrum-based agile lifecycle.
  • A platform support team that handles a steady stream of unplanned requests chooses the Kanban-based lean lifecycle with WIP limits.
  • A team testing whether customers want usage-based car insurance chooses the exploratory lifecycle and runs small experiments before committing to a full build.

All three use the same Inception goals, so the company's architecture and compliance groups get consistent information, but each team runs the process that suits its work. Over the following quarters, the support team adopts continuous delivery practices and moves to the continuous delivery lifecycle.

Common pitfalls

  • Overwhelm from choice. The toolkit is large. Teams that try to evaluate every option stall. Start from a lifecycle and tailor a few decisions at a time.
  • Treating DA as paperwork. Goal diagrams are aids for conversation, not forms to complete.
  • Tailoring without learning. DA expects teams to experiment and improve continuously. A one-time selection that never changes misses the point.
  • Ignoring enterprise awareness. Picking practices that suit one team but break shared standards or reporting creates friction elsewhere.

Disciplined Agile is one of several approaches to agile at scale, alongside the Scaled Agile Framework and Large-Scale Scrum. It is often considered during an agile transformation when an organization wants flexibility rather than a single standard method.

Frequently asked questions

Who owns Disciplined Agile?

The Project Management Institute (PMI) has owned Disciplined Agile since acquiring it in 2019, and it manages the content, training and certifications. Scott Ambler and Mark Lines created the toolkit, which began as Disciplined Agile Delivery (DAD), described in their 2012 book, and later expanded to cover IT, business functions and the wider enterprise.

How is Disciplined Agile different from Scrum?

Scrum is a single framework, while Disciplined Agile is a toolkit for choosing a way of working. DA draws practices from Scrum, Kanban, Extreme Programming, lean, SAFe and other sources, organizes them around process goals and offers several lifecycles, including Scrum-based and Kanban-based ones, so each team can pick the options that fit its context.

What are the phases of the Disciplined Agile lifecycle?

Most Disciplined Agile lifecycles pass through three phases. Inception gets the team going in the right direction by forming it, agreeing initial scope and architecture, securing funding and identifying risks. Construction produces working increments of a consumable solution as needs change. Transition releases into production through final testing, deployment, training and handover to users and operations.