DSDM
Also known as: Atern; Dynamic Systems Development Method
Agile project delivery framework emphasizing fixed time and cost with variable scope, foundational to PRINCE2 Agile.
DSDM (Dynamic Systems Development Method, later renamed Atern in 2007 and subsequently rebranded as DSDM Agile Project Framework / AgilePM) is one of the original Agile methods, predating the 2001 Agile Manifesto. DSDM was developed in 1994 by a UK-led consortium of organizations seeking a vendor-independent rapid application development framework, becoming one of the founding signatories of the Agile Manifesto in 2001. DSDM's central commitments are fixing time and cost while flexing scope through MoSCoW prioritization (Must, Should, Could, Won't have this time), iterative and incremental delivery, and active user involvement. The framework distinguishes itself from Scrum and XP by explicit attention to project-level governance, contractual considerations, and management products, making it more compatible with regulated and public-sector environments. DSDM substantially informs PRINCE2 Agile and the Agile Project Management (AgilePM) certification scheme.
Core components
- Eight principles (focus on the business need, deliver on time, collaborate, never compromise quality, build incrementally from firm foundations, develop iteratively, communicate continuously and clearly, demonstrate control)
- Roles: Business Sponsor, Business Visionary, Project Manager, Technical Coordinator, Business Ambassador, Business Analyst, Solution Developer, Solution Tester, Workshop Facilitator, others
- MoSCoW prioritization
- Timeboxed iteration with explicit timebox internal structure (investigation, refinement, consolidation)
- Fixed time and cost with variable scope
- Required management products (Business Case, Prioritised Requirements List, Solution Architecture Definition)
- Facilitated workshops and modeling techniques
Primary use case
Agile project management with project-level governance overhead acceptable, particularly UK public sector and financial services; foundation for PRINCE2 Agile delivery techniques (MoSCoW, timeboxing, fixed time and cost); basis for AgilePM Foundation and Practitioner certifications via APMG; international adoption particularly in Europe; training reference for organizations adopting agile within regulated or contractually-bound delivery environments.
Common criticisms
- DSDM has been overshadowed by Scrum since the mid-2000s, with the broader agile community treating it as a heavier alternative — many of DSDM's explicit governance and management-product elements that distinguish it from Scrum are interpreted by Scrum advocates as introducing unnecessary ceremony
- the elaborate role structure (10+ roles) is harder to operationalize in smaller teams than Scrum's three-role structure
- the DSDM Consortium / Agile Business Consortium is smaller than PMI, AXELOS, or the Scrum Alliance, limiting practitioner-community network effects and accumulated lessons
- fixed-time-and-cost-with-variable-scope is sometimes contractually incompatible with how agile work is procured, particularly in the public sector where DSDM was meant to fit
- empirical evidence of effectiveness is dominated by consortium-affiliated case studies
- the 2007 Atern rebrand and subsequent reversion to DSDM-related branding produced market confusion
- the framework's continuing evolution has not always tracked with broader agile-community evolution (notably around lean, Kanban, and DevOps), limiting topical relevance.
Lineage
- Siblings
- Scrum, The Agile Manifesto, PRINCE2 Agile