Dynamic Systems Development Method(DSDM)
| Line 1: | Line 1: | ||
| − | == | + | ==Introduction== |
| − | DSDM is a framework for Agile project management and delivery, helping to deliver results quickly and effectively. | + | 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.<ref> [''https://www.agilebusiness.org/content/introduction-0''] ''The DSDM Agile Project Framework (2014 Onwards)''</ref> |
| − | ''] '' | + | |
| + | 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.<ref> [''Craddock, A., Richards, K., Tudor, D., Roberts, B., & Godwin, J. (2012). The DSDM Agile Project Framework for Scrum.''] ''''</ref> 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.<ref> [''https://www.agilebusiness.org/content/introduction-0''] ''The DSDM Agile Project Framework (2014 Onwards)''</ref> | ||
| + | |||
| + | The DSDM approach is based on philosophy is that any kind of project should have clearly defined and aligned business goals, deliver frequently and empower motivated people. 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<ref> [''https://www.agilebusiness.org/content/introduction-0''] ''The DSDM Agile Project Framework (2014 Onwards)''</ref>,<ref>[''Sunner, D. (2016). Agile : Adapting to need of the hour''] '''' </ref>.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. | ||
| + | |||
| + | Below, it would be briefly described the basic elements of the DSDM framework. 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, artifacts and some main techniques that are used from this approach, like Timeboxing, facilitated workshops and MoSCoW prioritization. | ||
| + | |||
==Principles== | ==Principles== | ||
| + | 1. Focus on the Business Need<br> | ||
| + | |||
| + | 2. Deliver on Time<br> | ||
| + | |||
| + | 3. Collaborate<br> | ||
| + | |||
| + | 4. Never Compromise Quality<br> | ||
| + | |||
| + | 5. Build Incrementally from Firm Foundations<br> | ||
| + | |||
| + | 6. Develop Iteratively<br> | ||
| + | |||
| + | 7. Communicate Continuously and Clearly<br> | ||
| + | |||
| + | 8. Demonstrate Control<br> | ||
| + | |||
| + | <ref> [''https://www.agilebusiness.org/content/introduction-0''] ''The DSDM Agile Project Framework (2014 Onwards)''</ref> | ||
| + | <ref> [''Moran, A. (2015). Managing Agile Strategy, Implementation, Organization and People''] ''''</ref> | ||
| + | <ref> [''Craddock, A., Richards, K., Tudor, D., Roberts, B., & Godwin, J. (2012). The DSDM Agile Project Framework for Scrum.''] ''''</ref> | ||
| + | |||
==DSDM Process== | ==DSDM Process== | ||
| + | [[File:DSDM_Process.png|200px|thumb|right]] | ||
| + | |||
==Roles and Responsibilities== | ==Roles and Responsibilities== | ||
Revision as of 09:28, 19 September 2017
Contents |
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.[3]
The DSDM approach is based on philosophy is that any kind of project should have clearly defined and aligned business goals, deliver frequently and empower motivated people. 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[4],[5].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.
Below, it would be briefly described the basic elements of the DSDM framework. 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, artifacts and some main techniques that are used from this approach, like Timeboxing, facilitated workshops and MoSCoW prioritization.
Principles
1. Focus on the Business Need
2. Deliver on Time
3. Collaborate
4. Never Compromise Quality
5. Build Incrementally from Firm Foundations
6. Develop Iteratively
7. Communicate Continuously and Clearly
8. Demonstrate Control
DSDM Process
Roles and Responsibilities
Core Techniques
Advantages/Limitations
References
- ↑ [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)
- ↑ [Craddock, A., Richards, K., Tudor, D., Roberts, B., & Godwin, J. (2012). The DSDM Agile Project Framework for Scrum.] '
- ↑ [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)
- ↑ [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)
- ↑ [Sunner, D. (2016). Agile : Adapting to need of the hour] '
- ↑ [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)
- ↑ [Moran, A. (2015). Managing Agile Strategy, Implementation, Organization and People] '
- ↑ [Craddock, A., Richards, K., Tudor, D., Roberts, B., & Godwin, J. (2012). The DSDM Agile Project Framework for Scrum.] '
