Dynamic systems development method (DSDM) is an agile project delivery framework, initially

used as a software development method.[1][2] First released in 1994, DSDM originally sought to

provide some discipline to the rapid application development (RAD) method.[3] In later versions the
DSDM Agile Project Framework was revised and became a generic approach to project
management and solution delivery rather than being focused specifically on software development
and code creation[clarification needed][citation needed] and could be used for non-IT projects.[4] The DSDM Agile Project
Framework covers a wide range of activities across the whole project lifecycle and includes strong
foundations and governance, which set it apart from some other Agile methods.[5] The DSDM Agile
Project Framework is an iterative and incremental approach that embraces principles of Agile
development, including continuous user/customer involvement.
DSDM fixes cost, quality and time at the outset and uses the MoSCoW prioritisation of scope
into musts, shoulds, coulds and will not haves to adjust the project deliverable to meet the stated
time constraint. DSDM is one of a number of Agile methods for developing software and non-IT
solutions, and it forms a part of the Agile Alliance.
In 2014, DSDM released the latest version of the method in the 'DSDM Agile Project Framework'. At
the same time the new DSDM manual recognised the need to operate alongside other frameworks
for service delivery (esp. ITIL) PRINCE2, Managing Successful Programmes, and PMI.[6] The
previous version (DSDM 4.2) had only contained guidance on how to use DSDM with Extreme
Programming.

Contents

 1History of DSDM
 2DSDM Atern
o 2.1Principles
o 2.2Core techniques
o 2.3Roles
o 2.4Critical success factors
 3Comparison to other development frameworks
 4See also
 5References
 6Further reading
 7External links

History of DSDM[edit]
In the early 1990s, rapid application development (RAD) was spreading across the IT industry. The
user interfaces for software applications were moving from the old green screens to the graphical
user interfaces that are used today. New application development tools were coming on the market,
such as PowerBuilder. These enabled developers to share their proposed solutions much more
easily with their customers – prototyping became a reality and the frustrations of the classical,
sequential (waterfall) development methods could be put to one side.
However, the RAD movement was very unstructured: there was no commonly agreed definition of a
suitable process and many organisations came up with their own definition and approach. Many
major corporations were very interested in the possibilities but they were also concerned that they
did not lose the level of quality in the end deliverables that free-flow development could give rise to.
The DSDM Consortium was founded in 1994 by an association of vendors and experts in the field
of software engineering and was created with the objective of "jointly developing and promoting an
independent RAD framework" by combining their best practice experiences. The origins were an
event organised by the Butler Group in London. People at that meeting all worked for blue-
chip organisations such as British Airways, American Express, Oracle and Logica (other companies
such as Data Sciences and Allied Domecq have since been absorbed by other organisations).
In July 2006, DSDM Public Version 4.2[7] was made available for individuals to view and use;
however, anyone reselling DSDM must still be a member of the not-for-profit consortium.
In 2014, the DSDM handbook was made available online and public.[8] Additionally, templates for
DSDM can be downloaded.[9]
In October 2016 the DSDM Consortium rebranded as the Agile Business Consortium.[10] The Agile
Business Consortium is a not-for-profit, vendor-independent organisation which owns and
administers the DSDM framework.[11]