DSDM
Dynamic Systems
Development Method
DSDM Methodology

Goals



On time
Within budget
Of desired quality
DSDM Consortium


Founded 1994 by business-oriented
people representing 16 UK companies
Goal: develop and promote a standard
framework for systems development
based on the best practices of the rapid
application development (RAD)
approach
DSDM Consortium


Owns and promotes DSDM framework
New releases (on time of course)



Atern
Licenses resellers
Offers Certifications
DSDM Framework



Incorporate techniques and tools
Combine with other methodologies
Follow Core Principles
Core Principles





Deliverable “good enough” to satisfy
business need
Team cooperation and collaboration
Users involvement critical
Team has decision-making authority
High-level requirements are defined
early in the project; details are
addressed during development
Core Principles




Process is iterative and is structured to
support frequent product releases
Core functionality delivered early and
additional features delivered in later
releases
Testing early and ongoing
Changes are reversible
Development Process

Pre-project Phase


Feasibility Study


Visualized and selected
DSDM is a good fit ?
Business Study

Documents the functions and information
requirements at a high level, resulting in a
list of prioritized requirements
Development Process

Functional Model Iterative Phase (FMI)


Design and Build Iterative Phase (DBI)


Each component is designed, programmed, and
reviewed
Implementation Iterative Phase


Develops and refines prototypes
Documentation, training, user approval
Post-project Phase

performance monitoring and ongoing maintenance
Key Techniques

MoSCoW Prioritation


Prioritize functions honestly so ‘Must Have’
mission critical functions can be delivered
quickly in early releases.
Prototyping


Address process, usability, performance,
and business aspects
Suitable design and common
understanding
Key Techniques

Facilitated Workshops


Getting the right people face-to-face to
share information
TimeBoxing



Period of time – 6 weeks or less
Set of tasks resulting in a deliverable
Tasks fixed, not deliverable
Best Applications

DSDM is best applied in projects where
time is the fixed factor and functionality
can be varied



Poor choice – safety, security, reuse
Cultural shift for most businesses
Consultants

pineywoodstech.com/Services/Methodology.aspx
DSDM Conclusion

While other methodologies are similar
to DSDM, among them XP, SCRUM, and
RUP, DSDM’s strength lies in its:



Framework structure which permits a
choice of tools and techniques
Best practices roots
Emphasis on timely product delivery