methodDelivery & agility

Dynamic Systems Development Method

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

Download Markdown (.md)

01What 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.[1][2][3]

Governed agility with fixed constraints and flexible lower-priority scope Protect time, cost, and quality by varying what is not essential
Protected constraintsTime · cost · quality

Fixed timeboxes, explicit governance, agreed quality, and active business participation

Negotiated variableLower-priority scope

Should, Could, and Won't Have work provides contingency around the minimum outcome

Business need · feasibility · collaboration · incremental delivery

MoSCoW prioritization preserves a genuine minimum viable project outcome and leaves contingency; labeling everything Must Have defeats the method.

02Why 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.

03When 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.

04How 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.

05A practical example

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.

06Where 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.

07Sources

  1. About the ConsortiumAgile Business Consortium · Framework owner historyAbout the Consortium
  2. Agile Practice GuideProject Management Institute and Agile Alliance · Institutional practice guideAgile Practice Guide
  3. DSDM: Dynamic Systems Development MethodIEEE · Conference publicationDSDM: Dynamic Systems Development Method
View saved topics

Start typing to search titles, definitions, categories, and frameworks.