Dynamic Systems Development Method(DSDM)

Revision as of 09:19, 20 September 2017

Introduction

The Dynamic Systems Development Method (DSDM) is a framework for Agile project management and delivery, helping to deliver results quickly and effectively. It was created in 1994 through a collaboration of project practitioners among many companies and from that point there is a continuous evolution. Firstly, in 2008 updated in DSDM Atern and in 2014 rebranded to DSDM Agile Project Framework.^[1]

DSDM is a continual and incremental approach which embrace the values and the principles of the Agile development. These values are the empowerment and collaboration between the individuals and the teams, adapt and respond to the changes and continuous collaboration between project team and the business-customer. The DSDM approach always focuses on making people working more effectively towards achieving their goals. It is an approach while initially was used only for software development through the years and its revolution can be adapted in any technical environment for any kind of project.^[2] The DSDM framework is trying to face well-known problems that project managers have to address in any kind of project like ineffective communication, late delivery, unmet need through the desired solution, delayed or late Return of Investment etc.^[1]

The DSDM approach is based on the philosophy:

“Best business value emerges when projects are aligned to clear business goals,
deliver frequently and involve the collaboration of motivated and empowered people”

Furthermore, one of the main assumptions in DSDM approach is that nothing can be perfected planned from the first time and instead of setting unrealistic and unreasonable expectations, a perfection of 80% could be enough at least in the beginning^[1] ,^[3].This makes DSDM to differentiate with the other traditional approaches. For instance, other traditional methods like the ‘Waterfall’ approach needs 100% perfection in order to move forward to the next step or activity which has as a result wasted time, additional effort and back and forth steps. While with iterative DSDM approach is confronted these problems, since it is not aiming for the perfection from the initial phase.

Fig.1 Constitution of DSDM (https://www.vanharen.net/Player/eKnowledge/integrating_dsdm_into_an_existing_prince2_environment.pdf)

Below, it would be briefly described the basic elements of the DSDM framework which compromise the constitution of DSDM(Fig.1). In particular, it would be mentioned the fundamental principle of the DSDM philosophy. Next, these principles are supported by a lifecycle process of 3 phases, the roles and the responsibilities, artefacts and some main techniques that are used from this approach, like Timeboxing, facilitated workshops and MoSCoW prioritization.

Principles

The DSDM philosophy is supported by 8 core principles which are focused on the business need, on-time delivery, collaboration and communication, incremental and iterative work practices, a non-compromising stance on quality and the need to demonstrate control. These principles are trying to embrace the Agile values and create a mindset to people-teams’ attitude toward to deliver consistently while remaining flexible. These principles are really critical and should be strictly followed and adopted in order the DSDM approach to succeed and exploit the full benefits of this approach. Otherwise, it cannot be delivered the best business solutions.These principles are supporting with the DSDM lifecycle process, the appropriate set of roles and responsibilities, the artefacts-products and some main practices. Below there is a brief description of these principles.^{[1] [4]}, ^{[2] [5] [6]}

1. Focus on the Business Need
When DSDM approach is following, it is important all the teams that are involved in the project to understand and focus on the business priorities and needs, since all the decisions that are making regarding the project are around how to fulfill the business needs and understand what and when to be delivered.

2. Deliver on Time
One of the main goals and success factor of a project is the delivering on time. For this reason, in DSDM approach the teams should follow and meet deadlines by setting timeboxes which are a planned in advance timeframe but at the same time have a more variable and flexible scope in the in the pre-set deliverable.

3. Collaborate
Through collaboration can be achieved increased understanding, more efficient way of working, shared ownership which all of that will lead to increased performance. In order to be achieved a greater collaboration and fulfilled this principle, according to DSDM approach the teams firstly should empower their team members to take decision regarding the project, then engage the right stakeholder throughout the project at the right moment and finally build one team culture. In addition, all of these will be accomplished by setting the right roles and responsibilities to the right people and through facilitated workshops where their knowledge can be shared effectively with other members of the project team.

4. Never Compromise Quality
Quality is really important for a project and level of quality and expectations should be agreed in the beginning. Everyone has to aim at achieving that level of quality. So as to accomplish this goal and principle, the teams that are involved in the project should firstly agree on the level of quality of the project before its deployment, then, guarantee that quality cannot be a variable, design, and document appropriately and lastly continuously testing from an early stage of the project.

5. Build Incrementally from Firm Foundations
One thing that differentiates the DSDM approach from the rest Agile one is the concept of establishing firm foundations for the project in advance of the incremental development. According to the DSDM approach, it is really important first to understand the scope of the business problem and the proposed solution(firm foundations) but not in that detail which may cause delays due to an over-detailed analysis of requirements. Then, after the firm foundations have established, it is followed the incremental delivery of the project so as to deliver real business benefit as soon as possible.

6. Develop Iteratively
According to this principle it is really rare an accurate business solution to developed and delivered at first without applied any changes and revaluation of the project. For that reason, it is needed a continuous process of development with which more details that are emerging later can be recognized, the creativity and the learning is encouraged, and embrace change since a lot of changes are needed in order to reach the desire result.

7. Communicate Continuously and Clearly
It is usual that there are project failures because of poor communication between the teams and individuals. The DSDM aim to improve communication and its effectiveness and in order this to succeed different methods and practices are used from this framework, like stand-up meetings(scrum), facilitated workshops, visual communication. Additionally, teams are encouraged to informal communication and keeping lean and timely documentation.

8. Demonstrate Control
The involved teams need to understand the value of project governance and the need to demonstrate control. According to the DSDM approach in order to fulfill this principle, the plans and the progress should be visible to all, the project to be managed proactively, the project viability continuously to get evaluated based on the business targets and the progress should be measured by focusing on the delivery of products and not in the completion of the activities.

DSDM Process

Fig.2 DSDM Lifecycle Process (https://www.agilebusiness.org/content/process)

The DSDM approach is to development and delivery can be characterized both iterative and incremental, having as a primary goal to meet the business need and then to deliver the required features. In order to support the DSDM approach and adopt the principles that described above a process model is used. This model (Fig.2) consists of 3 main phases the pre-project, project lifecycle and the post-project. The project lifecycle is divided into 4 sub-phases which are the feasibility, foundations, evolutionary and the deployment phase.^[1],^[2],^[4]

1. Pre-project Phase
In this phase, it is ensuring that everyone has understood of project objectives and it is defined which projects are going to start initially.
2. Project lifecycle Phase
2.1.Feasibility Phase
In the feasibility phase, the project is examined both for its technical feasibility and the business cost-effectiveness. So this phase is critical since decisions are taking regarding the undertaking and investment on the project or the cancellation of it.
2.2.Foundations Phase
Once the feasibility phase has finished, it is further developed in order in that phase to be evaluated the business reasons behind the project, the potential solution that will be developed and how development and delivery will be handled from a managerial point of view. In this phase, it is not needed a high degree of details in the recording of requirements and less than few weeks will be needed even for big and with high complexity projects. Finally, the aim of foundations is everyone to understand the scope of the work and the way the project will be carried out.

2.3.Evolutionary Development Phase
The next phase is the evolutionary development in which the main focus is in the iterative and incremental development of a solution which will get towards the business’ requirements and objectives.
2.4.Deployment Phase
The last sub-phase in lifecycle process is the deployment one where it is tried to get the solution into an operational use and to be ready to get launched into the market.For example, in order to be clearer, the launch of a new tablet where multiple projects which run in different locations should be merged and deployed into one solution and launch in a single release. In this phase, there are also three sub-phases the assemble, the review and the deploy.
•Assemble: Gather and assemble of all artefacts which are relevant to the development of the solution.
•Review: Evaluate and review that there is the required quality based on the predefined objectives.
•Deploy: Get the solution into an operational use by training users, configuration of a software package etc.

3. Post-project
In the last main phase, there is an evaluation of the whole project and it is checked in which extent and how well the predefine business objectives and benefits have been met. Of course, the benefits will be visible after a pre-defined period.

Roles and Responsibilities

DSDM Roles and Responsibilities (https://www.agilebusiness.org/content/roles-and-responsibilities)

Artefacts

Table 1 Classification of DSDM Artefacts^[4]

Core Practices

Conclusion

References

1. ↑ ^{1.0 1.1 1.2 1.3 1.4} [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)
2. ↑ ^{2.0 2.1 2.2} [Craddock, A., Richards, K., Tudor, D., Roberts, B., & Godwin, J. (2012). The DSDM Agile Project Framework for Scrum.] '
3. ↑ [Sunner, D. (2016). Agile : Adapting to need of the hour] '
4. ↑ ^{4.0 4.1 4.2} [Moran, A. (2015). Managing Agile Strategy, Implementation, Organization and People] '
5. ↑ [http://www.mcpa.biz/2011/10/dsdm-atern-principals-overview/] DSDM Atern Principals – Overview
6. ↑ ["https://books.google.dk/books?id=MnRKjkaIdYwC&pg=PA16&lpg=PA16&dq=dsdm+principles&source=bl&ots=hoLrE4UXM-&sig=KGSq9dSoxtVKy6A_UKaG9HApqgU&hl=en&sa=X&ved=0ahUKEwjoy8K6w6_WAhVDIJoKHVUWBsQ4FBDoAQgnMAA#v=onepage&q=dsdm principles&f=false"]"Richards, K. (2007). Agile project management: running PRINCE2 projects with DSDM Atern"