Dynamic Systems Development Method (DSDM)

Dynamic Systems Development Method (DSDM) is an agile project management framework that provides a comprehensive approach to software development.

The DSDM Agile Project Framework can be used either stand-alone or combined with other recognized methods such as PRINCE2®, MSP, and PMI.

It is also ideal as a wrapper for more limited Agile approaches to ensure that the whole project lifecycle is addressed.

Dynamic Systems Development Method was developed in the 1990s in the UK by a consortium of software development organizations, which included British Airways, BT, Oracle, and others.

The development of DSDM was a response to the traditional, rigid, and bureaucratic approach to software development that often led to late deliveries and poor-quality software.

The consortium aimed to develop an agile approach to software development that was more flexible and could deliver high-quality software within the time and budget constraints of organizations. The development of DSDM was led by a team of software development experts, including Arie van Bennekum, Dolf Reijers, and others.

In 1994, the first version was released, which included principles and best practices for software development. Over the years, it has evolved and been refined, with the latest version being DSDM Agile Project Framework, which was released in 2014.

DSDM emphasizes the importance of collaboration and teamwork between the business stakeholders and the development team, with a focus on delivering high-quality software on time and within budget.

It involves an iterative and incremental approach to software development, with continuous feedback and adaptation throughout the development process.

DSDM provides a set of principles, best practices, and techniques to guide the development process.

These include timeboxing, prioritization, frequent reviews, and testing throughout the development cycle.

The framework also encourages the involvement of end-users and stakeholders throughout the development process, to ensure that the software meets their needs and requirements.

The Dynamic Systems Development Method is organized around a set of core principles, best practices, and techniques that guide the development process.

How DSDM Is Organised

Roles: DSDM defines a set of roles for the development team, including the Business Visionary, the Business Ambassador, the Technical Coordinator, the Solution Developer, the Solution Tester, and others. Each role has specific responsibilities and is essential to the success of the project.

Process: DSDM follows an iterative and incremental development process that involves five stages: Feasibility Study, Business Study, Functional Model Iteration, Design and Build Iteration, and Implementation. Each stage has specific objectives and deliverables that must be met before progressing to the next stage.

Values: DSDM is built around eight core values that guide the development team’s behaviour and decision-making. These values include Focus on the Business Need, Deliver on Time, Collaborate, Never Compromise Quality, Build Incrementally from Firm Foundations, Develop Iteratively, Communicate Continuously and Clearly, and Demonstrate Control.

Techniques: DSDM includes a set of techniques to help the development team deliver high-quality software, such as Timeboxing, MoSCoW prioritization, Prototyping, Facilitated Workshops, and others. These techniques are designed to encourage collaboration, deliver incremental value, and manage risk throughout the development process.

Overall, DSDM provides a comprehensive framework for agile project management that emphasizes collaboration, flexibility, and continuous improvement.

By following the core principles, best practices, and techniques of DSDM, development teams can deliver high-quality software on time and within budget while meeting the needs of the business and end-users.

While Dynamic Systems Development Method has many benefits, there have been some criticisms of the framework.

Common Criticism

Complexity: DSDM can be quite complex and prescriptive, which can make it challenging to implement and maintain. Some organizations may find it difficult to adopt all the principles and practices of DSDM.

Overhead: DSDM requires a lot of upfront planning and documentation, which can add overhead to the development process. This overhead may be unnecessary for smaller, less complex projects.

Limited flexibility: While DSDM provides a flexible and adaptive approach to software development, it may not be as flexible as other agile frameworks, such as Scrum or Kanban. This lack of flexibility can be problematic for organizations that need to adapt quickly to changing requirements or market conditions.

Emphasis on collaboration: While collaboration is a core principle of DSDM, it may not always be practical or feasible in all organizations. Some teams may work remotely or have limited opportunities for face-to-face collaboration, which can make it challenging to fully implement the DSDM approach.

Resource-intensive: DSDM requires a significant investment of time, resources, and training to implement successfully. This investment may be too costly for smaller organizations or teams with limited budgets.

It’s worth noting that many of these criticisms can be addressed with proper training, implementation, and customization of DSDM to meet the needs of the organization.

In conclusion, Dynamic Systems Development Method is a comprehensive and well-established agile project management framework that offers a structured approach to software development.

While DSDM is not as widely known or used as other agile frameworks like Scrum and Kanban, it provides a set of core principles, best practices, and techniques that can help development teams deliver high-quality software on time and within budget.

By emphasizing collaboration, flexibility, and continuous improvement, it enables development teams to respond quickly to changing requirements and market conditions while delivering incremental value to the business and end-users.

While DSDM may not be suitable for every organization, it is worth considering as a framework for managing complex software development projects.

I am incredibly grateful that you have taken the time to read this post.

Do you want to get new content in your Email?

Check my main categories of content below:

Navigate between the many topics covered in this website:

Do you want to check previous posts about Project Management? Check these from the last couple of weeks:

Support my work by sharing my content with your network using the sharing buttons below.

Want to show your support tangibly? A virtual coffee is a small but nice way to show your appreciation and give me the extra energy to keep crafting valuable content! Pay me a coffee: