DSDM (Dynamic Systems Development Method) - David-Lennuk/Buketov_Python GitHub Wiki

1. What is DSDM?

DSDM (Dynamic Systems Development Method) is an Agile project delivery framework that emphasizes the full project lifecycle—from planning and requirements gathering to delivery and maintenance. It was first released in 1994 in the UK to address the need for a structured yet flexible method for rapid application development (RAD). DSDM provides clear guidelines, principles, roles, and practices for delivering quality solutions on time and within budget.

DSDM is known for being highly business-focused, encouraging active user involvement, iterative development, and strict time management.

2. Core Philosophy of DSDM

At the heart of DSDM is the belief that:

• Nothing is built perfectly the first time.

• Projects must deliver products quickly and efficiently.

• Time, cost, and quality are fixed, but features are variable.

This approach allows the team to focus on high-priority functionality and deliver real value to the business quickly, while deferring lower-priority features.

3. Key Principles of DSDM

There are 8 core principles that guide all DSDM projects:

1. Focus on the business need

• Prioritize requirements based on their business value.

2. Deliver on time

• Use timeboxing and prioritization to ensure deadlines are met.

3. Collaborate

• Strong cooperation between stakeholders and the project team.

4. Never compromise quality

• Maintain pre-agreed quality standards throughout development.

5. Build incrementally from firm foundations

• Develop in small iterations that build upon validated previous work.

6. Develop iteratively

• Encourage feedback and adjust through constant iteration.

7. Communicate continuously and clearly

• Face-to-face communication and transparency are essential.

8. Demonstrate control

• Use metrics and planning tools to monitor progress.

4. The DSDM Project Lifecycle

DSDM includes 7 key phases in its lifecycle:

4.1. Pre-project

• Ensures that the project is viable and aligned with business strategy.

4.2. Feasibility Study

• Confirms whether the project is technically and financially viable.

• Defines key objectives and high-level requirements.

4.3. Foundations Phase

• Establishes a baseline plan and architecture for development.

• Agrees on the project approach, responsibilities, and standards.

4.4. Exploration Phase

• Iterative development of prioritized features.

• Detailed analysis and prototyping of high-priority items.

4.5. Engineering Phase

• Converts prototypes into deployable and tested components.

• Focuses on technical completeness and integration.

4.6. Deployment Phase

• Delivers the product to the operational environment.

• May be done incrementally or in a single release.

4.7. Post-project

• Reviews performance, collects feedback, and confirms long-term maintenance plans.

5. DSDM Roles and Responsibilities

DSDM defines clear and distinct roles to ensure responsibility and ownership:

5.1. Business Roles

• Business Sponsor: Provides funding and strategic direction.

• Business Visionary: Owns the product vision and aligns it with business goals.

• Business Ambassador: Represents the end users.

• Business Advisor: Provides specialist knowledge.

5.2. Solution Development Roles

• Solution Developer: Designs and develops the solution.

• Solution Tester: Verifies the solution meets requirements and quality.

5.3. Management Roles

• Project Manager: Coordinates activities and ensures adherence to schedule.

• Team Leader: Manages day-to-day development tasks.

5.4. Supporting Roles

• Technical Coordinator: Oversees technical consistency.

• DSDM Coach: Ensures correct implementation of DSDM practices.

6. MoSCoW Prioritization in DSDM

DSDM uses MoSCoW to prioritize requirements:

• M – Must Have: Critical requirements that must be delivered.

• S – Should Have: Important, but not vital; workarounds may exist.

• C – Could Have: Nice to have; low impact if omitted.

• W – Won’t Have (this time): Agreed as out of scope for now.

This system ensures that vital features are always delivered first, especially within fixed time and cost constraints.

7. Timeboxing and Iterative Development

Timeboxing

• A timebox is a fixed period (e.g., 2–4 weeks) during which a specific set of tasks must be completed.

• Each timebox includes planning, development, testing, and review.

• Prevents “scope creep” and ensures consistent progress.

Iteration

• Work is done in short, repeated cycles to gradually improve the product.

• Feedback is gathered at the end of each iteration for continuous refinement.

8. Prototyping and Modeling

• Prototyping is a core practice in DSDM.

• Allows stakeholders to see and interact with early versions of the product.

• Helps clarify requirements and catch issues early.

Modeling (e.g., diagrams, flowcharts) supports clear understanding and communication of systems and processes.

9. Quality and Testing in DSDM

• Quality is built-in from the beginning—not inspected in later.

• Testing is continuous and not a separate phase.

• Every feature must meet predefined quality standards before it's considered done.

10. DSDM vs Other Agile Methods

11. Advantages of DSDM

• Focuses on delivering business value early.

• Controls scope through MoSCoW prioritization.

• Provides clear structure and governance.

• Encourages strong stakeholder involvement.

• Reduces risk through iterative development and early feedback.

12. Limitations of DSDM

• Requires strong commitment from business users.

• May be too heavyweight for small projects.

• Can be difficult to implement in organizations unfamiliar with Agile.

13. Tools Commonly Used with DSDM

Although DSDM does not require specific tools, it often integrates with:

• JIRA or Trello (task and timebox tracking)

• Confluence, Notion (documentation)

• Balsamiq, Figma (prototyping)

• MS Project or Smartsheet (project management)

• Slack, MS Teams (communication)

14. When to Use DSDM

DSDM is a great choice when:

• You need Agile methods for large, complex projects.

• Time and budget are fixed, but scope can vary.

• High stakeholder involvement is possible.

• Quality and governance are important.

15. Conclusion

DSDM is a robust Agile framework designed for delivering business-focused, high-quality solutions within a structured and time-constrained environment. By balancing flexibility with governance, and focusing on continuous feedback, collaboration, and business value, DSDM supports sustainable project success—especially in enterprise settings.