Dynamic Systems Development Method (DSDM)

What is Dynamic Systems Development Method (DSDM)?

The Dynamic Systems Development Method (DSDM) is a UK agile framework from 1994 that locks time, cost and quality and treats scope as the variable, using MoSCoW prioritization and timeboxes.

Updated November 2026 · 3 min read


The Dynamic Systems Development Method (DSDM) is an agile project delivery framework that fixes time, cost and quality at the start of a project and lets the scope vary. Instead of promising every feature and then slipping the deadline, a DSDM project commits to a date and budget and delivers the most important requirements within them, using MoSCoW prioritization and timeboxes to decide what makes the cut.

DSDM was created in the United Kingdom in 1994 by the DSDM Consortium, a group of vendors and practitioners who wanted to bring discipline to rapid application development (RAD). It predates the Agile Manifesto, and the consortium was later renamed the Agile Business Consortium. The framework has been revised several times, including a 2007 version called DSDM Atern, and the Agile Business Consortium also publishes AgilePM, a project management certification based on it. Unlike many agile methods that focus on a single team, DSDM covers the whole project, including governance, business roles and the business case.

The eight principles of DSDM

  1. Focus on the business need. Every decision should serve the project's business goal.
  2. Deliver on time. Timeboxes and deadlines are protected; scope flexes instead.
  3. Collaborate. Business and technical people work together throughout.
  4. Never compromise quality. The quality level is agreed at the start and held constant.
  5. Build incrementally from firm foundations. Do enough analysis up front to build on, then deliver in increments.
  6. Develop iteratively. Use feedback to converge on the right solution.
  7. Communicate continuously and clearly. Prefer workshops, models and prototypes to long documents.
  8. Demonstrate control. Make plans and progress visible so stakeholders can trust the process.

DSDM project phases

PhaseWhat happens
Pre-ProjectConfirm the idea is worth exploring and set up the next step
FeasibilityCheck whether the project is likely to be technically and commercially viable
FoundationsEstablish the business case, prioritized requirements, solution approach and delivery plan
Evolutionary DevelopmentBuild the solution iteratively in a series of timeboxes
DeploymentRelease increments into live use, then review the benefits
Post-ProjectAssess whether the expected business benefits were achieved

Evolutionary Development and Deployment repeat as each increment is released, so a single project usually deploys several times.

MoSCoW and timeboxing

DSDM is where MoSCoW prioritization became widely known. Requirements are classed as Must have, Should have, Could have or Won't have this time. DSDM's guidance is that Must haves should take no more than about 60% of the planned effort, leaving the Shoulds and Coulds as contingency. If the work runs late, the team drops Could haves first, then Should haves, without moving the deadline. Work is organized into timeboxes, typically a few weeks long, each with its own prioritized objectives.

A hypothetical DSDM project

Consider a hypothetical council that needs a new online permit-application system live before a regulation takes effect in six months. The team estimates 200 person-days of work and plans it as follows:

  • Must have (120 person-days, 60%): application form, payment, case worker queue.
  • Should have (50 person-days, 25%): status tracking for applicants, email notifications.
  • Could have (30 person-days, 15%): a saved-draft feature and a reporting dashboard.

Midway through, integration with the payment provider takes 20 person-days longer than expected. Rather than slip the date, the team drops the reporting dashboard (20 person-days) from the Could haves and keeps the saved-draft feature (10 person-days). The system launches on time with all Must and Should haves, and the dashboard moves to a later release.

Common pitfalls

  • Labeling everything a Must. If 90% of the work is Must have, there is no contingency and the fixed deadline becomes fiction.
  • Skipping Foundations. DSDM expects enough early design to build on. Teams that jump straight into development lose the "firm foundations" principle.
  • Missing business roles. DSDM depends on active business participants, such as the Business Visionary and Business Ambassador. Without them, prioritization stalls.
  • Compromising quality to hit the date. The framework holds quality fixed; cutting testing to meet the deadline breaks the model.

DSDM grew out of rapid application development and is one of the earlier members of the agile software development family. Its fixed-time, flexible-scope stance is a useful contrast in any agile vs. waterfall discussion, and its trade-offs map closely to the agile iron triangle.

Frequently asked questions

How does DSDM use MoSCoW prioritization?

DSDM classes requirements as Must have, Should have, Could have or Won't have this time, the scheme known as MoSCoW prioritization. Its guidance is that Must haves take no more than about 60% of planned effort, leaving Shoulds and Coulds as contingency. If work runs late, the team drops Could haves first, then Should haves, rather than moving the deadline.

What are the phases of a DSDM project?

A DSDM project runs through Pre-Project, Feasibility, Foundations, Evolutionary Development, Deployment and Post-Project. Feasibility checks technical and commercial viability, Foundations sets the business case, prioritized requirements and delivery plan, and Evolutionary Development builds the solution in timeboxes. Development and Deployment repeat for each increment, so a project usually deploys several times.

What is the relationship between DSDM and AgilePM?

AgilePM is a project management certification based on the DSDM framework and published by the Agile Business Consortium, the body formerly called the DSDM Consortium. DSDM itself was created in the UK in 1994 and has been revised several times, including the 2007 version called DSDM Atern. Unlike many team-level agile methods, DSDM covers the whole project, including governance, business roles and the business case.