Dynamic Systems Development Method(DSDM)
(Created page with "==Abstract==") |
|||
Line 1: | Line 1: | ||
==Abstract== | ==Abstract== | ||
+ | DSDM is a framework for Agile project management and delivery, helping to deliver results quickly and effectively. Over the years, has been applied to a wide range of projects - from small software developments all the way up to full-scale business process change. DSDM was created in 1994 through a collaboration of a large number of project practitioners across many companies and it was evolved through the years. Firstly, DSDM changed into an updated version DSDM Atern in 2008 and into DSDM Agile Project Framework in 2014. The DSDM philosophy is that any kind of project should have clearly defined and aligned business goals, deliver frequently and empower motivated people. <ref> [''https://www.agilebusiness.org/content/introduction-0''] ''The DSDM Agile Project Framework (2014 Onwards)''</ref>, <ref>[''https://www.agilebusiness.org/sites/default/files/the_dsdm_agile_project_framework_v1_11.pdf?token=yqzXtW1a1''] "The DSDM Agile Project Framework for Scrum" </ref> In the following article, it would be described and analyzed the iterative life-cycle process that is used, how and what kind of roles and responsibilities are defined, the basic principles in which is based and some core techniques that are used, like timeboxing, prototyping, MoSCow prioritization.<ref>[''Peldzius, S., Ragaisis, S., & Vytaunas, V. (2013). Seeking Process Maturity with DSDM Atern.''] '''' </ref>,<ref>[''Stapleton, J. (2003). DSDM Business Focused Development. | ||
+ | ''] ''Name of link'' </ref> | ||
+ | |||
+ | ==Principles== | ||
+ | |||
+ | ==DSDM Process== | ||
+ | |||
+ | ==Roles and Responsibilities== | ||
+ | |||
+ | ==Core Techniques== | ||
+ | |||
+ | ==Advantages/Limitations== | ||
+ | |||
+ | ==References== | ||
+ | <references /> |
Revision as of 18:36, 18 September 2017
Contents |
Abstract
DSDM is a framework for Agile project management and delivery, helping to deliver results quickly and effectively. Over the years, has been applied to a wide range of projects - from small software developments all the way up to full-scale business process change. DSDM was created in 1994 through a collaboration of a large number of project practitioners across many companies and it was evolved through the years. Firstly, DSDM changed into an updated version DSDM Atern in 2008 and into DSDM Agile Project Framework in 2014. The DSDM philosophy is that any kind of project should have clearly defined and aligned business goals, deliver frequently and empower motivated people. [1], [2] In the following article, it would be described and analyzed the iterative life-cycle process that is used, how and what kind of roles and responsibilities are defined, the basic principles in which is based and some core techniques that are used, like timeboxing, prototyping, MoSCow prioritization.[3],[4]
Principles
DSDM Process
Roles and Responsibilities
Core Techniques
Advantages/Limitations
References
- ↑ [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)
- ↑ [https://www.agilebusiness.org/sites/default/files/the_dsdm_agile_project_framework_v1_11.pdf?token=yqzXtW1a1] "The DSDM Agile Project Framework for Scrum"
- ↑ [Peldzius, S., Ragaisis, S., & Vytaunas, V. (2013). Seeking Process Maturity with DSDM Atern.] '
- ↑ [Stapleton, J. (2003). DSDM Business Focused Development. ] Name of link