# Dynamic Systems Development Method

DSDM is a full-lifecycle Agile project-delivery method that fixes time, cost, and quality while varying lower-priority scope.

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

## What it means

The Dynamic Systems Development Method \(DSDM\) is an Agile project-delivery framework developed by an industry consortium. It combines iterative and incremental delivery with explicit governance, business roles, timeboxing, facilitated collaboration, and MoSCoW prioritization. Modern guidance is also known through the DSDM Agile Project Framework.

## Why it matters

Agile teams often need to operate inside projects with deadlines, budgets, governance expectations, and several stakeholder groups. DSDM addresses that environment directly. Its constraint-driven approach protects time, cost, and quality while allowing negotiable scope, keeping business need and timely delivery visible throughout the lifecycle.

## When to use it

Use DSDM for project-shaped change where the deadline and business case matter, active business participation is available, and scope can be prioritized. It can cover software and broader business change. It is a poor fit when every stated requirement is mandatory or empowered business roles cannot engage regularly.

## How it works

1. Assess feasibility and foundations, clarifying the business need, solution direction, governance, roles, and delivery approach.
2. Prioritize requirements with MoSCoW, reserving Must Have for the minimum viable project outcome and leaving contingency in lower categories.
3. Deliver through fixed timeboxes in which business and technical participants explore, engineer, and demonstrate evolving increments.
4. Maintain agreed quality criteria while varying lower-priority scope to protect deadlines and cost constraints.
5. Deploy increments, review benefits and outcomes, and retain enough management products to demonstrate control.

## A practical example

A university must replace course registration before the next academic year. DSDM roles bring registry experts, developers, operations, and sponsors into one project. Secure enrollment and prerequisite checks are Must Haves; timetable export is a Should Have. Timeboxes demonstrate working flows, and optional reporting features move when integration work threatens the date.

## Where it breaks

DSDM has more roles, products, and lifecycle guidance than lightweight team methods, so a small product team may find it excessive. MoSCoW fails when stakeholders label everything mandatory. Fixed dates can encourage hidden quality compromises unless quality is genuinely protected, and access to empowered business representatives is essential rather than decorative.

## Common mistakes

- Declaring most requirements Must Have and eliminating contingency.
- Using timeboxes as mini-waterfalls with testing deferred to the end.
- Assigning business roles to people who lack time or decision authority.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/dynamic-systems-development-method/#visualization-dynamic-systems-development-method>)

## Sources

1. [About the Consortium](<https://www.agilebusiness.org/about-us/>) — Agile Business Consortium · Framework owner history
2. [Agile Practice Guide](<https://www.agilealliance.org/wp-content/uploads/2021/02/AgilePracticeGuide.pdf>) — Project Management Institute and Agile Alliance · Institutional practice guide
3. [DSDM: Dynamic Systems Development Method](<https://ieeexplore.ieee.org/document/779095/>) — IEEE · Conference publication

## Related topics

- [MoSCoW Prioritization](<https://wiki.soroush.uk/topic/moscow-prioritization/>)
- [Crystal Methods](<https://wiki.soroush.uk/topic/crystal-methods/>)
- [Feature-Driven Development](<https://wiki.soroush.uk/topic/feature-driven-development/>)
