DSDM Framework

https://ik.imagekit.io/beyondpmf/frameworks/dsdm-framework.png
The DSDM framework, emphasizing continuous user involvement and iterative development, primarily addresses friction related to delivery speed, implementation, and customer experience by focusing on iterative cycles and user feedback to ensure the delivered product meets user needs.

The Dynamic Systems Development Method (DSDM) Framework is a comprehensive agile project management and delivery framework that focuses on timely delivery of business solutions. The framework is built on collaboration and iterative progress through controlled project environments. It ensures that strategic goals are met within budget, on schedule, and with rigorous quality standards. DSDM is particularly effective in environments where requirements are likely to change, allowing for rapid adjustments without significant rework.

Steps / Detailed Description

Feasibility Study: Assess the project's viability and define the scope. | Business Study: Analyze business processes and user needs to develop a business model. | Functional Model Iteration: Create prototypes and designs to refine the system's functionality. | Design and Build Iteration: Develop and test the system iteratively, incorporating user feedback. | Implementation: Deploy the system in a live environment, with user training and support. | Post-Project: Review project outcomes and identify lessons learned for future projects.

Best Practices

Ensure active and continuous user involvement. | Maintain clear communication and frequent updates among all stakeholders. | Use modular development to manage complexity and facilitate changes.

Pros

High user involvement leads to more user-focused solutions. | Flexible and adaptable to changing requirements. | Emphasizes frequent delivery of products.

Cons

Requires a significant time commitment from user representatives. | Can be complex to manage if team members are not well-versed in the framework. | Potentially high overhead costs due to the iterative nature and frequent reviews.

When to Use

When rapid response to changing requirements is needed. | In projects where user involvement is critical for success.

When Not to Use

In projects with fixed requirements and scope. | Where there is limited availability of key stakeholders.

Related Frameworks

Categories

Lifecycle

Scope

Scope not defined

Maturity Level

Maturity level not specified

Time to Implement

2–4 Weeks
3–6 Months
1–2 Weeks
3–6 Months
1–2 Months
3–6 Months
1–2 Weeks
Less Than 1 Day
1–2 Weeks
Longer Than 6 Months
1–2 Weeks
Longer Than 6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Days
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Weeks
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
2–4 Weeks
1–2 Weeks
1–2 Days
1–2 Weeks
Longer Than 6 Months
Longer Than 6 Months
3–6 Months
Longer Than 6 Months
Longer Than 6 Months
Longer Than 6 Months
1–2 Weeks
Longer Than 6 Months
3–6 Months
Less Than 1 Day
3–6 Months
1–2 Months
3–6 Months
Longer Than 6 Months
3–6 Months
Less Than 1 Day
1–2 Weeks
3–6 Months
3–6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
1–2 Days
1–2 Weeks
1–2 Months
Longer Than 6 Months
1–2 Weeks
Longer Than 6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
Less Than 1 Day
1–2 Weeks
3–6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
Longer Than 6 Months
Less Than 1 Day
3–6 Months
Longer Than 6 Months
1–2 Months
1–2 Weeks
Longer Than 6 Months
1–2 Weeks
3–6 Months
1–2 Weeks
1–2 Weeks
3–6 Months
Less Than 1 Day
1–2 Weeks
1–2 Weeks
3–6 Months
3–6 Months
Less Than 1 Day
1–2 Weeks
Longer Than 6 Months
1–2 Months
1–2 Weeks
1–2 Weeks
1–2 Weeks
Longer Than 6 Months

Copyright Information

Autor:
DSDM Consortium
1994
Publication:
DSDM Consortium