In 30 seconds
- DSDM fixes time, cost and quality; features are what flex.
- It popularized MoSCoW prioritization.
- Now maintained by the Agile Business Consortium.
Origins
DSDM began in 1994 when a UK consortium of companies wanted a standard for rapid application development. It's one of the lightweight methods represented at the Agile Manifesto meeting. The consortium is now called the Agile Business Consortium.
Fix time and cost, flex features
Traditional projects fix features and let time and cost slip. DSDM flips this: deadlines, budget and quality are fixed up front, and the set of features delivered adapts to fit, guided by priorities.
MoSCoW prioritization
| Category | Means |
|---|---|
| Must have | Without it, the release fails |
| Should have | Important, but there's a workaround |
| Could have | Nice to have |
| Won't have (this time) | Agreed out of scope for now |
Myth vs reality
Myth · DSDM is only for big projects.
Reality · It scales down; its ideas suit many projects.
Myth · MoSCoW means everything is a Must.
Reality · DSDM recommends keeping Musts to around 60% of effort.
Myth · DSDM isn't agile.
Reality · It was one of agile's founding methods.
FAQ
Is DSDM still used?
Yes, especially in the UK, often as AgilePM for project managers.
Does DSDM have roles?
Yes, several, covering business, solution and management responsibilities.
Can DSDM work with Scrum?
Yes; teams often run Scrum sprints inside a DSDM project frame.