Dynamic Systems Development Method(DSDM) - Revision history

Tkokotas at 18:43, 17 November 2018

2018-11-17T18:43:21Z

← Older revision		Revision as of 18:43, 17 November 2018
Line 1:		Line 1:
			''Developed by Iason Divanis''


	==Introduction==		==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.<ref name="a"> [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)</ref>		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 name="a"> [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)</ref>

Manolis at 16:37, 2 October 2017

2017-10-02T16:37:38Z

← Older revision		Revision as of 16:37, 2 October 2017
Line 1:		Line 1:
	==Introduction==		==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.<ref name="a"> [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)</ref>		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 name="a"> [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)</ref>
	~~troll~~
	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 evolution can be adapted in any technical environment for any kind of project.<ref name="b"> 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 name="a"/>		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 evolution can be adapted in any technical environment for any kind of project.<ref name="b"> 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 name="a"/>

Manolis at 16:37, 2 October 2017

2017-10-02T16:37:11Z

← Older revision		Revision as of 16:37, 2 October 2017
Line 1:		Line 1:
	==Introduction==		==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.<ref name="a"> [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)</ref>		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 name="a"> [https://www.agilebusiness.org/content/introduction-0] The DSDM Agile Project Framework (2014 Onwards)</ref>
			troll
	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 evolution can be adapted in any technical environment for any kind of project.<ref name="b"> 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 name="a"/>		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 evolution can be adapted in any technical environment for any kind of project.<ref name="b"> 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 name="a"/>

Iason Divanis at 19:54, 1 October 2017

2017-10-01T19:54:37Z

← Older revision		Revision as of 19:54, 1 October 2017
Line 97:		Line 97:

	==Core Practices==		==Core Practices==
	In order to ensure and support the whole DSDM process, different practices and tools are used. These are the timeboxing, the MoSCow prioritization, facilitated workshops, iterative development, Modeling and prototyping techniques. Below it would be really brief presented the three most common and used practices from the DSDM framework which are <ref name="a"/>,<ref name="d"/>,<ref name="g">Voigt, B.(2004). Dynamic System Development Method"https://files.ifi.uzh.ch/rerg/arvo/courses/seminar_ws03/14_Voigt_DSMD_Ausarbeitung.pdf"</ref>:		In order to ensure and support the whole DSDM process, different practices and tools are used. These are the timeboxing, the MoSCow prioritization, facilitated workshops, iterative development, Modeling and prototyping techniques. Below it would be really brief presented the three most common and used practices from the DSDM framework which are <ref name="a"/>,
			<ref name="d"/>,
			<ref name="g">Voigt, B.(2004). Dynamic System Development Method "https://files.ifi.uzh.ch/rerg/arvo/courses/seminar_ws03/14_Voigt_DSMD_Ausarbeitung.pdf"</ref>:

	'''1.Timeboxing'''<br>		'''1.Timeboxing'''<br>

Iason Divanis: /* Annotated Bibliography */

2017-10-01T19:46:42Z

Annotated Bibliography

← Older revision		Revision as of 19:46, 1 October 2017
Line 132:		Line 132:
	==Annotated Bibliography==		==Annotated Bibliography==
	'''Craddock, A., Richards, K., Tudor, D., Roberts, B., & Godwin, J. , The DSDM Agile Project Framework for Scrum (2012)'''<br>		'''Craddock, A., Richards, K., Tudor, D., Roberts, B., & Godwin, J. , The DSDM Agile Project Framework for Scrum (2012)'''<br>

	This is a pocketbook which describes a DSDM version which is designed to complement the Scrum method.In the beginning, there is a brief description of the SCRUM and then it is described the whole DSDM framework and how DSDM supplement in each focus point supplement this methodology. For instance, which characteristics can SCRUM borrow from the DSDM process, in which phases and how these can be adapted.<br>		This is a pocketbook which describes a DSDM version which is designed to complement the Scrum method.In the beginning, there is a brief description of the SCRUM and then it is described the whole DSDM framework and how DSDM supplement in each focus point supplement this methodology. For instance, which characteristics can SCRUM borrow from the DSDM process, in which phases and how these can be adapted.<br>

Iason Divanis: /* Annotated Bibliography */

2017-10-01T19:46:25Z

Annotated Bibliography

← Older revision		Revision as of 19:46, 1 October 2017
Line 141:		Line 141:
	Moran in his book examines the agile from a management perspective by focusing on matters of strategy, implementation, organization and people. A broad survey of the agile methodologies has been conducted and a comparison between of them. Then there is a more detail discussion and analysis on the agile programme and project management using the DSDM framework as a basis, and different aspects have been discussed like the governance, quality, risk, and configuration topics. Furthermore, there is an analysis on how agile can be implemented in wider organizations and which is the role of the people. From this book has mainly used the chapter about the DSDM framework.<br>		Moran in his book examines the agile from a management perspective by focusing on matters of strategy, implementation, organization and people. A broad survey of the agile methodologies has been conducted and a comparison between of them. Then there is a more detail discussion and analysis on the agile programme and project management using the DSDM framework as a basis, and different aspects have been discussed like the governance, quality, risk, and configuration topics. Furthermore, there is an analysis on how agile can be implemented in wider organizations and which is the role of the people. From this book has mainly used the chapter about the DSDM framework.<br>

	'''Flora, H. K., & Chande, S. V. ~~(2014).~~ A Systematic Study on Agile Software Development Methodologies and Practices'''		'''Flora, H. K., & Chande, S. V., A Systematic Study on Agile Software Development Methodologies and Practices(2014)'''<br>
	Flora and Chande in their article are presenting the agile software development methodologies and practices. Firstly, they are introducing you to the agile concept and its principles and then all the methods are analyzed based on some specific aspects. These are the background, the philosophy and scope, the features and benefits and finally the limitations of each one. In the end, the drawbacks of the agile software development are discussed based on the analysis of the methods.		Flora and Chande in their article are presenting the agile software development methodologies and practices. Firstly, they are introducing you to the agile concept and its principles and then all the methods are analyzed based on some specific aspects. These are the background, the philosophy and scope, the features and benefits and finally the limitations of each one. In the end, the drawbacks of the agile software development are discussed based on the analysis of the methods.<br>

	==References==		==References==
	<references />		<references />

Iason Divanis at 19:45, 1 October 2017

2017-10-01T19:45:31Z

← Older revision		Revision as of 19:45, 1 October 2017
Line 1:		Line 1:
	==Introduction==		==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.<ref name="a"> [''https://www.agilebusiness.org/content/introduction-0''] ''The DSDM Agile Project Framework (2014 Onwards)''</ref>		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 name="a"> [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 evolution can be adapted in any technical environment for any kind of project.<ref name="b"> ~~[''~~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 name="a"/>		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 evolution can be adapted in any technical environment for any kind of project.<ref name="b"> 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 name="a"/>

	The DSDM approach is based on the philosophy:<br><br>		The DSDM approach is based on the philosophy:<br><br>
Line 9:		Line 9:
	[[File:Composition_of_DSDM.PNG\|200px\|thumb\|right\|Fig.1 Constitution of DSDM (https://www.vanharen.net/Player/eKnowledge/integrating_dsdm_into_an_existing_prince2_environment.pdf)]]		[[File:Composition_of_DSDM.PNG\|200px\|thumb\|right\|Fig.1 Constitution of DSDM (https://www.vanharen.net/Player/eKnowledge/integrating_dsdm_into_an_existing_prince2_environment.pdf)]]

	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<ref name="a" /> ,<ref name="c">~~[''~~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.		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<ref name="a" /> ,<ref name="c">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 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.		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.
Line 15:		Line 15:
	==Principles==		==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 the full benefits of this framework to get exploit. 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.<ref name="a"/>		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 the full benefits of this framework to get exploit. 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.<ref name="a"/>
	<ref name="d"> ~~[''~~Moran, A. (2015). Managing Agile Strategy, Implementation, Organization and People~~''] ''''~~</ref>,		<ref name="d"> Moran, A. (2015). Managing Agile Strategy, Implementation, Organization and People</ref>,
	<ref name="b"/>		<ref name="b"/>
	<ref name="e"> [''http://www.mcpa.biz/2011/10/dsdm-atern-principals-overview/''] ''DSDM Atern Principals – Overview''</ref>		<ref name="e"> [''http://www.mcpa.biz/2011/10/dsdm-atern-principals-overview/''] ''DSDM Atern Principals – Overview''</ref>
Line 97:		Line 97:

	==Core Practices==		==Core Practices==
	In order to ensure and support the whole DSDM process, different practices and tools are used. These are the timeboxing, the MoSCow prioritization, facilitated workshops, iterative development, Modeling and prototyping techniques. Below it would be really brief presented the three most common and used practices from the DSDM framework which are <ref name="a"/>,<ref name="d"/>,<ref name="g">["Voigt, B.(2004). Dynamic System Development Method"]"https://files.ifi.uzh.ch/rerg/arvo/courses/seminar_ws03/14_Voigt_DSMD_Ausarbeitung.pdf"</ref>:		In order to ensure and support the whole DSDM process, different practices and tools are used. These are the timeboxing, the MoSCow prioritization, facilitated workshops, iterative development, Modeling and prototyping techniques. Below it would be really brief presented the three most common and used practices from the DSDM framework which are <ref name="a"/>,<ref name="d"/>,<ref name="g">Voigt, B.(2004). Dynamic System Development Method"https://files.ifi.uzh.ch/rerg/arvo/courses/seminar_ws03/14_Voigt_DSMD_Ausarbeitung.pdf"</ref>:

	'''1.Timeboxing'''<br>		'''1.Timeboxing'''<br>
Line 118:		Line 118:
	Although DSDM is presented as a mature and well-defined method which can be applied to all the kind of projects and business, this method has some limitations which are:		Although DSDM is presented as a mature and well-defined method which can be applied to all the kind of projects and business, this method has some limitations which are:

	•The DSDM framework is more suitable for big organizations where all the roles and practices can be assigned and found, and the whole lifecyle process can be implemented. <ref name="f"/>For instance, it is not possible to implement this framework for a project management to start-ups since the size of team and the multile roles that are needed, cannot be found.<ref name="h">["Abdelrehim, A., & Ibrahim, S. (2017). A Dynamic System development Method for Startups Migrate to C loud~~"]""~~</ref><br>		•The DSDM framework is more suitable for big organizations where all the roles and practices can be assigned and found, and the whole lifecyle process can be implemented. <ref name="f"/>For instance, it is not possible to implement this framework for a project management to start-ups since the size of team and the multile roles that are needed, cannot be found.<ref name="h">Abdelrehim, A., & Ibrahim, S. (2017). A Dynamic System development Method for Startups Migrate to C loud</ref><br>

	•The big number of different roles can create administration problems during the project development process which has as a result misunderstanding on who is the decision maker.<br>		•The big number of different roles can create administration problems during the project development process which has as a result misunderstanding on who is the decision maker.<br>
Line 139:		Line 139:

	'''Moran A.,Managing Agile Strategy, Implementation, Organization and People(2015)'''<br>		'''Moran A.,Managing Agile Strategy, Implementation, Organization and People(2015)'''<br>
	Moran in his book examines the agile from a management perspective by focusing on matters of strategy, implementation, organization and people. A broad survey of the agile methodologies has been conducted and a comparison between of them. Then there is a more detail discussion and analysis on the agile programme and project management using the DSDM framework as a basis, and different aspects have been discussed like the governance, quality, risk, and configuration topics. Furthermore, there is an analysis on how agile can be implemented in wider organizations and which is the role of the people. From this book has mainly used the chapter about the DSDM framework.		Moran in his book examines the agile from a management perspective by focusing on matters of strategy, implementation, organization and people. A broad survey of the agile methodologies has been conducted and a comparison between of them. Then there is a more detail discussion and analysis on the agile programme and project management using the DSDM framework as a basis, and different aspects have been discussed like the governance, quality, risk, and configuration topics. Furthermore, there is an analysis on how agile can be implemented in wider organizations and which is the role of the people. From this book has mainly used the chapter about the DSDM framework.<br>

			'''Flora, H. K., & Chande, S. V. (2014). A Systematic Study on Agile Software Development Methodologies and Practices'''
			Flora and Chande in their article are presenting the agile software development methodologies and practices. Firstly, they are introducing you to the agile concept and its principles and then all the methods are analyzed based on some specific aspects. These are the background, the philosophy and scope, the features and benefits and finally the limitations of each one. In the end, the drawbacks of the agile software development are discussed based on the analysis of the methods.

	==References==		==References==
	<references />		<references />

Iason Divanis: /* Limitations */

2017-10-01T19:36:42Z

Limitations

← Older revision		Revision as of 19:36, 1 October 2017
Line 124:		Line 124:
	•There are relatively high barrier to adopt this framework since switching to DSDM is neither cheap nor fast and requires a significant cultural change so as the organization to be in the position to implement this framework. In addition, one more barrier is that this framework requires a high maturity level from the organization. One more barrier is that DSDM is based on the user involvement and the close collaboration which is not always possible.<ref name="g"/><ref name="i"/><br>		•There are relatively high barrier to adopt this framework since switching to DSDM is neither cheap nor fast and requires a significant cultural change so as the organization to be in the position to implement this framework. In addition, one more barrier is that this framework requires a high maturity level from the organization. One more barrier is that DSDM is based on the user involvement and the close collaboration which is not always possible.<ref name="g"/><ref name="i"/><br>

	•DSDM is really strict regarding the philosophy and the eight principles which has as a result to be restrictive, not flexible enough and difficult to work with comparing with other agile methods.<ref name="i">~~[""]"~~Flora, H. K., & Chande, S. V. (2014). A Systematic Study on Agile Software Development Methodologies and Practices"</ref>		•DSDM is really strict regarding the philosophy and the eight principles which has as a result to be restrictive, not flexible enough and difficult to work with comparing with other agile methods.<ref name="i">Flora, H. K., & Chande, S. V. (2014). A Systematic Study on Agile Software Development Methodologies and Practices</ref>

	==Conclusion==		==Conclusion==

Iason Divanis: /* Limitations */

2017-10-01T19:36:18Z

Limitations

← Older revision		Revision as of 19:36, 1 October 2017
Line 124:		Line 124:
	•There are relatively high barrier to adopt this framework since switching to DSDM is neither cheap nor fast and requires a significant cultural change so as the organization to be in the position to implement this framework. In addition, one more barrier is that this framework requires a high maturity level from the organization. One more barrier is that DSDM is based on the user involvement and the close collaboration which is not always possible.<ref name="g"/><ref name="i"/><br>		•There are relatively high barrier to adopt this framework since switching to DSDM is neither cheap nor fast and requires a significant cultural change so as the organization to be in the position to implement this framework. In addition, one more barrier is that this framework requires a high maturity level from the organization. One more barrier is that DSDM is based on the user involvement and the close collaboration which is not always possible.<ref name="g"/><ref name="i"/><br>

	•DSDM is really strict regarding the philosophy and the eight principles which has as a result to be restrictive, not flexible enough and difficult to work with comparing with other agile methods.<ref name="i">["Flora, H. K., & Chande, S. V. (2014). A Systematic Study on Agile Software Development Methodologies and Practices~~"]"~~"</ref>		•DSDM is really strict regarding the philosophy and the eight principles which has as a result to be restrictive, not flexible enough and difficult to work with comparing with other agile methods.<ref name="i">[""]"Flora, H. K., & Chande, S. V. (2014). A Systematic Study on Agile Software Development Methodologies and Practices"</ref>

	==Conclusion==		==Conclusion==

Iason Divanis: /* Limitations */

2017-10-01T19:35:27Z

Limitations

← Older revision		Revision as of 19:35, 1 October 2017
Line 124:		Line 124:
	•There are relatively high barrier to adopt this framework since switching to DSDM is neither cheap nor fast and requires a significant cultural change so as the organization to be in the position to implement this framework. In addition, one more barrier is that this framework requires a high maturity level from the organization. One more barrier is that DSDM is based on the user involvement and the close collaboration which is not always possible.<ref name="g"/><ref name="i"/><br>		•There are relatively high barrier to adopt this framework since switching to DSDM is neither cheap nor fast and requires a significant cultural change so as the organization to be in the position to implement this framework. In addition, one more barrier is that this framework requires a high maturity level from the organization. One more barrier is that DSDM is based on the user involvement and the close collaboration which is not always possible.<ref name="g"/><ref name="i"/><br>

	•DSDM is really strict regarding the philosophy and the eight principles which has as a result to be restrictive, not flexible enough and difficult to work with comparing with other agile methods.<ref name="i">["Flora, H. K., & Chande, S. V. (2014). A Systematic Study on Agile Software Development Methodologies and Practices"] ""</ref>		•DSDM is really strict regarding the philosophy and the eight principles which has as a result to be restrictive, not flexible enough and difficult to work with comparing with other agile methods.<ref name="i">["Flora, H. K., & Chande, S. V. (2014). A Systematic Study on Agile Software Development Methodologies and Practices"]""</ref>

	==Conclusion==		==Conclusion==