# Disciplined Agile

Disciplined Agile is a context-sensitive toolkit for choosing and continuously improving ways of working across teams and value streams.

- Type: framework
- Domain: Delivery & agility
- Level: Advanced
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/disciplined-agile/>)

## What it means

Disciplined Agile \(DA\) is a process-decision toolkit maintained by the Project Management Institute. Rather than prescribing one lifecycle, it presents goals, options, and trade-offs drawn from Agile, Lean, DevOps, and other approaches so teams and organizations can choose a way of working suited to their context.

## Why it matters

Teams rarely start with identical products, risks, skills, regulations, architecture, or organizational constraints. DA makes those differences explicit and helps people compare practices instead of defaulting to a single branded framework. Its guided continuous-improvement stance encourages small, informed experiments while considering the wider value stream and enterprise.

## When to use it

Use DA when a team needs structured help tailoring its lifecycle or when local delivery must connect with architecture, data, security, governance, operations, and portfolio concerns. It is most useful when practitioners can evaluate trade-offs; novices may need coaching to avoid being overwhelmed by choices.

## How it works

1. Describe the current situation, desired outcomes, constraints, risks, stakeholders, and boundaries of the value stream.
2. Select an initial lifecycle and practices using process goals, decision points, options, and their documented trade-offs.
3. Make the chosen way of working explicit so team members and partners understand responsibilities and flow.
4. Measure outcomes and bottlenecks, maintain an improvement backlog, and run small experiments rather than launching a wholesale transformation.
5. Share useful learning across teams and evolve practices as context, capability, and organizational needs change.

## A practical example

A medical-device software team uses iterative delivery but must coordinate formal risk evidence, hardware integration, and operations. It maps its way of working, keeps Scrum-like planning, adds explicit architecture and compliance options, and uses a continuous-improvement backlog. After measuring approval delays, it involves quality specialists earlier instead of adding a final gate.

## Where it breaks

A broad catalog can produce analysis paralysis or arbitrary “pick and mix” behavior without strong goals and feedback. DA terminology and training add learning cost, and tailoring may hide avoidance of difficult organizational changes. Context sensitivity does not mean every practice is equally effective; teams still need evidence, technical competence, and clear outcome measures.

## Common mistakes

- Choosing practices by preference without examining context or trade-offs.
- Documenting a tailored process once and failing to evolve it.
- Calling every local variation successful without measuring delivery and customer outcomes.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/disciplined-agile/#visualization-disciplined-agile>)

## Sources

1. [Foundation for Business Agility with Disciplined Agile](<https://www.pmi.org/disciplined-agile>) — Project Management Institute · Official toolkit overview
2. [Disciplined Agile](<https://www.pmi.org/learning/agile/disciplined-agile>) — Project Management Institute · Official learning overview
3. [Continuous Improvement Process](<https://www.pmi.org/microsites/disciplined-agile/process/continuous-improvement>) — Project Management Institute · Official process guidance

## Related topics

- [Scaled Agile Framework](<https://wiki.soroush.uk/topic/scaled-agile-framework/>)
- [Flight Levels](<https://wiki.soroush.uk/topic/flight-levels/>)
- [Agile Product Development](<https://wiki.soroush.uk/topic/agile-product-development/>)
