Adaptation and agile - Revision history

S183653 at 20:53, 9 May 2023

2023-05-09T20:53:09Z

← Older revision		Revision as of 20:53, 9 May 2023
Line 123:		Line 123:
	Although Agile brings the possibility of a constant change in work focus, the values do not prescribe how a project manager should adapt to the values in their daily management, but only prescribes the direction and goal. Thus, in addition to the Agile values, an organization must expect having to educate and experiment in their management form when striving to follow the Agile values.		Although Agile brings the possibility of a constant change in work focus, the values do not prescribe how a project manager should adapt to the values in their daily management, but only prescribes the direction and goal. Thus, in addition to the Agile values, an organization must expect having to educate and experiment in their management form when striving to follow the Agile values.

			=Annotated bibliography=

			Manifesto for Agile Software Development - The webpage is a declaration of the values ratifying the meaning of Agile. The webpage is written by one of the authors behind the manifesto and member of the Agile Aliance. The source is written in an informal language. The interests of the author, as a member of the Agile Aliance, must be considered by the reader when studying the page, given that it does provide a subjective opinion on alternative to working Agile and does not back-up arguments with relevant references. The webpage must be considered fundamental to study if wanting to adopt the Agile values.

			State of Agile Report, 16th Edition - The report is a part of an annual conference on software development, explaining a status-quo perspective on the development of Agile throughout the software industry. The report is written by an independent consultancy firm, without any interests in the topic, yet is sponsored by interest organizations within Agile development. The report is based on statistics from pro-Agile companies, meaning the data describes popular trends and downsides to the values from users perspective, but does not reflect on alternatives to Agile development. The report is relevant to read for individuals interested in following the latest trends within Agile software development.

			Prince2 Agile Practical Implementation Guide - Step-by-step Advice for Every Project Type, Second Edition - For readers interested in further studying the adaptation of Agile values, this book presents a step-by-step guide of how to and important considerations one must do in the transition to ensure success. The credibility of the PRINCE2 organization, alongside the acknowledgement within modern management of PRINCE2 certification, makes this book a strong reference, given the PRINCE2 organization having an interest of maintaining their highly thought of reputation, by only publishing quality products. The book does diverge from other perspectives on the Agile values, by acknowledging the potential of the philosophy being relevant to not just software development but to projects in dynamic environments in general.


	=Key references;=		=Key references;=
	<references/>		<references/>

S183653 at 20:13, 9 May 2023

2023-05-09T20:13:39Z

Show changes

S183653 at 19:41, 9 May 2023

2023-05-09T19:41:53Z

← Older revision		Revision as of 19:41, 9 May 2023
Line 7:		Line 7:
	Although the term Agile was manifested in February 2001, Agile methods and approaches goes even further back, with Agile software development frameworks such as XP <ref>Beck, K. (2000). Extreme programming explained : embrace change. Addison-Wesley</ref>, SCRUM, DSDM etc. <ref name = "Agile Manifesto"> Beck, K. Beedle, Mike (2001). Manifesto for Agile Software Development. Retrieved 1. May 2023 from https://agilemanifesto.org/</ref>		Although the term Agile was manifested in February 2001, Agile methods and approaches goes even further back, with Agile software development frameworks such as XP <ref>Beck, K. (2000). Extreme programming explained : embrace change. Addison-Wesley</ref>, SCRUM, DSDM etc. <ref name = "Agile Manifesto"> Beck, K. Beedle, Mike (2001). Manifesto for Agile Software Development. Retrieved 1. May 2023 from https://agilemanifesto.org/</ref>

	In the mid-nineties, software developers started questioning their current way of building software and as a response turned to start experimenting with old and new ideas to find a better way to work. From this, new methodologies emerged focusing on collaboration between the software developers and business stakeholders, more frequent value adding deliveries, team structuring, and new work methods within their development teams <ref name = "Agile Aliance"> Agile Aliance (2023). Agile 101. Retrieved 2. May 2023 from https://www.agilealliance.org/agile101/</ref>. Through open innovation, the above-mentioned frameworks emerged and the movement around working Agile started growing in the industry.		In the mid-nineties, software developers started questioning their current way of building software, with a high level documentation work, and as a response turned to start experimenting with old and new ideas to find a better way to work. From this, new methodologies emerged focusing on collaboration between the software developers and business stakeholders, more frequent value adding deliveries, team structuring, and new work methods within their development teams <ref name = "Agile Aliance"> Agile Aliance (2023). Agile 101. Retrieved 2. May 2023 from https://www.agilealliance.org/agile101/</ref>. Through open innovation, the above-mentioned frameworks emerged and the movement around working Agile started growing in the industry.

	The term Agile was defined in February 2001, when a group of 17 software developers formulated a called the Manifesto for Agile Software Development <ref name = "Agile Manifesto History"> Highsmith, J. (2001). History: The Agile Manifesto. Retrieved 1. May 2023 from https://agilemanifesto.org/history.html</ref>. The Agile Manifesto emerged from the recognition that conventional software development methodologies, such as the Waterfall model, were unsatisfactory and inflexible to meet the rapidly changing demands of the software industry in the 1990s. Thus, a webpage by Jim Highsmith was published in 2001, manifesting the mindset and values of Agile.		The term Agile was defined in February 2001, when a group of 17 software developers gathered in Utah and formulated a manifesto called the Manifesto for Agile Software Development <ref name = "Agile Manifesto History"> Highsmith, J. (2001). History: The Agile Manifesto. Retrieved 1. May 2023 from https://agilemanifesto.org/history.html</ref>. The Agile Manifesto emerged from the recognition that conventional software development methodologies, such as the Waterfall model, were unsatisfactory and inflexible to meet the rapidly changing demands of the software industry in the 1990s. Thus, a webpage by Jim Highsmith was published in 2001, manifesting the mindset and values of Agile.

	A-long side the Agile Manifesto a non-profit global organization, Agile Alliance, was founded by the same founders that signed the Agile Manifesto <ref name = "About Agile Aliance"> Agile Aliance (2023). About Agile Alliance. Retrieved 1. May 2023 from https://www.agilealliance.org/the-alliance/</ref>. The Agile Alliance has in 2023 more than 72,000 members and works as an interest organization to continue the work on ~~developing Agile~~ software ~~development~~.		A-long side the Agile Manifesto a non-profit global organization, Agile Alliance, was founded by the same founders that signed the Agile Manifesto <ref name = "About Agile Aliance"> Agile Aliance (2023). About Agile Alliance. Retrieved 1. May 2023 from https://www.agilealliance.org/the-alliance/</ref>. The Agile Alliance has in 2023 more than 72,000 members and works as an interest organization to continue the work on finding better ways to develop software.


	=What is Agile=		=What is Agile=
	Agile as defined in the manifesto <ref name="Agile Manifesto" /> goes broader than being a framework such as SCRUM, XP etc. and is more than a method such as daily stand-ups, sprints etc. Agile is by the Agile Alliance defined as an umbrella term <ref name="Agile Aliance" /> which groups a set of frameworks and practices through their overlapping values and principles ~~defined~~ in the Agile Manifesto <ref name="Agile Manifesto" />. The term agile comes from agility, and is by Qumer and Henderson-Sellers <ref> Qumer, A., & Henderson-Sellers, B. (2006). Comparative evaluation of XP and scrum using the 4d analytical tool (4-DAT). Proceedings of the European and Mediterranean Conference on Information Systems, Emcis 2006.</ref> understood as “the ability to accommodate and adapt to changes in a dynamic environment. Being agile means applying previous knowledge while learning from current experience to help deliver high-quality products, under budget constraints and in short time frames” <ref> Jyothi, V. E., & Rao, K. N. (2011). Effective Implementation of Agile Practices: Ingenious and Organized Theoretical Framework. International Journal of Advanced Computer Science and Applications, 2(3), 41–48. https://doi.org/10.14569/IJACSA.2011.020308</ref>.		Agile as defined in the manifesto <ref name="Agile Manifesto" /> goes broader than being a framework such as SCRUM, XP etc. and is more than a method such as daily stand-ups, sprints etc. Agile is by the Agile Alliance defined as an umbrella term <ref name="Agile Aliance" /> which groups a set of frameworks and practices through their overlapping values and principles, described in the Agile Manifesto <ref name="Agile Manifesto" />. The term agile comes from agility, and is by Qumer and Henderson-Sellers <ref> Qumer, A., & Henderson-Sellers, B. (2006). Comparative evaluation of XP and scrum using the 4d analytical tool (4-DAT). Proceedings of the European and Mediterranean Conference on Information Systems, Emcis 2006.</ref> understood as “the ability to accommodate and adapt to changes in a dynamic environment. Being agile means applying previous knowledge while learning from current experience to help deliver high-quality products, under budget constraints and in short time frames” <ref> Jyothi, V. E., & Rao, K. N. (2011). Effective Implementation of Agile Practices: Ingenious and Organized Theoretical Framework. International Journal of Advanced Computer Science and Applications, 2(3), 41–48. https://doi.org/10.14569/IJACSA.2011.020308</ref>.

	The umbrella term Agile and the adjective agile, must, based on these definitions, be distinguished from each other, having the umbrella term Agile refer to the Agile Manifesto <ref name="Agile Manifesto" /> and the adjective agile refer to the ability of adapting to change in a project context, by applying the values summarized by the Agile Manifesto.		The umbrella term Agile and the adjective agile, must, based on these definitions, be distinguished from each other, having the umbrella term Agile refer to the Agile Manifesto <ref name="Agile Manifesto" /> and the adjective agile refer to the ability of adapting to change in a project context, by for instance applying the values summarized by the Agile Manifesto.

	==4 Values of Agile==		==4 Values of Agile==
	The Agile Manifesto is based on four main values ~~and principles~~: (I) Individuals and interactions (II) Working software (III)Customer collaboration (IV) Responding to change <ref name = "The Journal"> Campanelli, A. S., & Parreiras, F. S. (2015). Agile methods tailoring – A systematic literature review. Journal of Systems and Software, 110, 85–100. https://doi.org/10.1016/j.jss.2015.08.035</ref>.		The Agile Manifesto is based on four main values, which describes what a team adopting to the Agile values should strive after:
			*(I) Individuals and interactions over processes and tools.
			*(II) Working software over comprehensive documentation.
			*(III)Customer collaboration over contract negotiation.
			*(IV) Responding to change over following a plan. <ref name = "The Journal"> Campanelli, A. S., & Parreiras, F. S. (2015). Agile methods tailoring – A systematic literature review. Journal of Systems and Software, 110, 85–100. https://doi.org/10.1016/j.jss.2015.08.035</ref><ref name="Agile Manifesto" />

	==12 Principles of Agile==		==12 Principles of Agile==
	A more elaborate presentation of the values ~~was~~ presented in the Agile Manifesto a long side the 4 values, presenting 12 supporting principles. The principles each refers to the values in different ways, with the same goal of driving better software development.		A more elaborate presentation of the values is presented in the Agile Manifesto a long side the 4 values, presenting 12 supporting principles. The principles each refers to the values in different ways, with the same goal of driving better software development.

	1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.		1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

S183653 at 19:22, 9 May 2023

2023-05-09T19:22:57Z

← Older revision		Revision as of 19:22, 9 May 2023
Line 7:		Line 7:
	Although the term Agile was manifested in February 2001, Agile methods and approaches goes even further back, with Agile software development frameworks such as XP <ref>Beck, K. (2000). Extreme programming explained : embrace change. Addison-Wesley</ref>, SCRUM, DSDM etc. <ref name = "Agile Manifesto"> Beck, K. Beedle, Mike (2001). Manifesto for Agile Software Development. Retrieved 1. May 2023 from https://agilemanifesto.org/</ref>		Although the term Agile was manifested in February 2001, Agile methods and approaches goes even further back, with Agile software development frameworks such as XP <ref>Beck, K. (2000). Extreme programming explained : embrace change. Addison-Wesley</ref>, SCRUM, DSDM etc. <ref name = "Agile Manifesto"> Beck, K. Beedle, Mike (2001). Manifesto for Agile Software Development. Retrieved 1. May 2023 from https://agilemanifesto.org/</ref>

	In the mid-nineties, software developers started questioning their current way of building software and as a response turned to start experimenting with old and new ideas to find a better way to work. From this, new methodologies emerged focusing on collaboration between the software developers and business stakeholders, more frequent value adding deliveries, team structuring, and new work methods within their development teams <ref name = "Agile Aliance"> Agile Aliance (2023). Agile 101. Retrieved 2. May 2023 from https://www.agilealliance.org/agile101/</ref>. Through open innovation, the above-mentioned frameworks emerged and the movement around working Agile started growing.		In the mid-nineties, software developers started questioning their current way of building software and as a response turned to start experimenting with old and new ideas to find a better way to work. From this, new methodologies emerged focusing on collaboration between the software developers and business stakeholders, more frequent value adding deliveries, team structuring, and new work methods within their development teams <ref name = "Agile Aliance"> Agile Aliance (2023). Agile 101. Retrieved 2. May 2023 from https://www.agilealliance.org/agile101/</ref>. Through open innovation, the above-mentioned frameworks emerged and the movement around working Agile started growing in the industry.

	The term Agile was defined in February 2001, when a group of 17 software developers formulated a called the Manifesto for Agile Software Development <ref name = "Agile Manifesto History"> Highsmith, J. (2001). History: The Agile Manifesto. Retrieved 1. May 2023 from https://agilemanifesto.org/history.html</ref>. The Agile Manifesto emerged from the recognition that conventional software development methodologies, such as the Waterfall model, were unsatisfactory and inflexible to meet the rapidly changing demands of the software industry in the 1990s. Thus, a webpage by Jim Highsmith was published in 2001, manifesting the mindset and values of Agile.		The term Agile was defined in February 2001, when a group of 17 software developers formulated a called the Manifesto for Agile Software Development <ref name = "Agile Manifesto History"> Highsmith, J. (2001). History: The Agile Manifesto. Retrieved 1. May 2023 from https://agilemanifesto.org/history.html</ref>. The Agile Manifesto emerged from the recognition that conventional software development methodologies, such as the Waterfall model, were unsatisfactory and inflexible to meet the rapidly changing demands of the software industry in the 1990s. Thus, a webpage by Jim Highsmith was published in 2001, manifesting the mindset and values of Agile.

S183653 at 19:18, 9 May 2023

2023-05-09T19:18:27Z

← Older revision		Revision as of 19:18, 9 May 2023
Line 1:		Line 1:
	The term Agile refers to a set of 4 values and 12 supporting principles for software developers to adopt and work by, focusing on creating flexibility and taking an iterative approach in projects. Agile originates from the “Manifesto for Agile Software Development” (2001)<ref name="Agile Manifesto" />, written by a group of software developers. The Agile values are designed for software developers, and emphasizes collaboration, adaptability, and a high frequency of business-value adding deliveries ~~in their work~~. Working Agile equals embracing change, through encouraging teams to be flexible and adapt to changing circumstances. The Agile values prioritize working software over comprehensive documentation. Adopting to the Agile values is found as beneficial to implement in projects operating in dynamic environments with a frequent change in delivery requirements or to prompt a proactive approach to changes.		The term Agile refers to a set of 4 values and 12 supporting principles for software developers to adopt and work by, focusing on creating flexibility and taking an iterative approach in projects. Agile originates from the “Manifesto for Agile Software Development” (2001)<ref name="Agile Manifesto" />, written by a group of software developers. The Agile values are designed for software developers, and emphasizes collaboration, adaptability, and a high frequency of business-value adding deliveries throughout a project. Working Agile equals embracing change, through encouraging teams to be flexible and adapt to changing circumstances. The Agile values prioritize working software over comprehensive documentation. Adopting to the Agile values is found as beneficial to implement in projects operating in dynamic environments with a frequent change in delivery requirements or to prompt a proactive approach to changes.

	This article enlightens how adapting ~~to a change in circumstances and~~ Agile can be used in the context of project management, to help when the context of a project changes or proactively seek adaptation to the unknown factors within a dynamic project environment. The article explains the meaning of Agile and the 4 values of Agile a long side the 12 principles supporting the values <ref name="Agile Manifesto" />. ~~Additionally, how~~ to work Agile is presented, through different project frameworks, recommendable software platforms, methods for daily work, and criteria to help method tailoring.		This article enlightens how adapting the Agile value can be used in the context of project management, to help when the context of a project changes or proactively seek adaptation to the unknown factors within a dynamic project environment. The article explains the meaning of Agile and the 4 values of Agile a long side the 12 principles supporting the values <ref name="Agile Manifesto" />. How to work Agile is presented, through different project frameworks, recommendable software platforms, methods for daily work, and criteria to help method tailoring.

S183653 at 19:14, 9 May 2023

2023-05-09T19:14:54Z

← Older revision		Revision as of 19:14, 9 May 2023
Line 1:		Line 1:
	The term Agile refers to a set of 4 values and 12 supporting principles for software developers to adopt and work by, focusing on flexibility and taking an iterative approach in projects. Agile originates from the “Manifesto for Agile Software Development” (2001)<ref name="Agile Manifesto" />, written by a group of software developers. The Agile values are designed for software developers, and emphasizes collaboration, adaptability, and a high frequency of business-value adding deliveries in their work. Working Agile equals embracing change, through encouraging teams to be flexible and adapt to changing circumstances. The Agile values prioritize working software over comprehensive documentation. Adopting to the Agile values is found as beneficial to implement in projects operating in dynamic environments with a frequent change in delivery requirements or to prompt a proactive approach to changes.		The term Agile refers to a set of 4 values and 12 supporting principles for software developers to adopt and work by, focusing on creating flexibility and taking an iterative approach in projects. Agile originates from the “Manifesto for Agile Software Development” (2001)<ref name="Agile Manifesto" />, written by a group of software developers. The Agile values are designed for software developers, and emphasizes collaboration, adaptability, and a high frequency of business-value adding deliveries in their work. Working Agile equals embracing change, through encouraging teams to be flexible and adapt to changing circumstances. The Agile values prioritize working software over comprehensive documentation. Adopting to the Agile values is found as beneficial to implement in projects operating in dynamic environments with a frequent change in delivery requirements or to prompt a proactive approach to changes.

	This article enlightens how adapting to a change in circumstances and Agile can be used in the context of project management, to help when the context of a project changes or proactively seek adaptation to the unknown factors within a dynamic project environment. The article explains the meaning of Agile and the 4 values of Agile a long side the 12 principles supporting the values <ref name="Agile Manifesto" />. Additionally, how to work Agile is presented, through different project frameworks, recommendable software platforms, methods for daily work, and criteria to help method tailoring.		This article enlightens how adapting to a change in circumstances and Agile can be used in the context of project management, to help when the context of a project changes or proactively seek adaptation to the unknown factors within a dynamic project environment. The article explains the meaning of Agile and the 4 values of Agile a long side the 12 principles supporting the values <ref name="Agile Manifesto" />. Additionally, how to work Agile is presented, through different project frameworks, recommendable software platforms, methods for daily work, and criteria to help method tailoring.

S183653 at 19:14, 9 May 2023

2023-05-09T19:14:06Z

← Older revision		Revision as of 19:14, 9 May 2023
Line 1:		Line 1:
	Agile refers to a set of values and 12 supporting principles ~~with the goal of driving a flexible~~ and iterative approach ~~to project management and software development, originating~~ from the “Manifesto for Agile Software Development” (2001)<ref name="Agile Manifesto" />, ~~novel~~ by a group of software developers. The Agile values are designed for software developers, and emphasizes collaboration, adaptability, and a high frequency of business-value adding deliveries in their work. Agile ~~principles embrace~~ change ~~and encourage~~ teams to be flexible and adapt to changing circumstances. Agile ~~principles~~ prioritize working software over comprehensive documentation.		The term Agile refers to a set of 4 values and 12 supporting principles for software developers to adopt and work by, focusing on flexibility and taking an iterative approach in projects. Agile originates from the “Manifesto for Agile Software Development” (2001)<ref name="Agile Manifesto" />, written by a group of software developers. The Agile values are designed for software developers, and emphasizes collaboration, adaptability, and a high frequency of business-value adding deliveries in their work. Working Agile equals embracing change, through encouraging teams to be flexible and adapt to changing circumstances. The Agile values prioritize working software over comprehensive documentation. Adopting to the Agile values is found as beneficial to implement in projects operating in dynamic environments with a frequent change in delivery requirements or to prompt a proactive approach to changes.

	~~This article enlightens how adapting~~ to ~~a change in circumstances and Agile can be used in~~ the context of project management, to help when the context of a project changes or proactively seek adaptation to the unknown factors within a dynamic project environment. The article presents the 4 values of Agile ~~a long side the 12 principles supporting the~~ values <ref name="Agile Manifesto" />. Additionally, how to work Agile is presented, through different project frameworks, recommendable software platforms, methods for daily work, and criteria to help method tailoring. The approach is found as beneficial to implement in projects operating in dynamic environments.

			This article enlightens how adapting to a change in circumstances and Agile can be used in the context of project management, to help when the context of a project changes or proactively seek adaptation to the unknown factors within a dynamic project environment. The article explains the meaning of Agile and the 4 values of Agile a long side the 12 principles supporting the values <ref name="Agile Manifesto" />. Additionally, how to work Agile is presented, through different project frameworks, recommendable software platforms, methods for daily work, and criteria to help method tailoring.

S183653 at 16:51, 9 May 2023

2023-05-09T16:51:46Z

← Older revision		Revision as of 16:51, 9 May 2023
Line 78:		Line 78:


	==Agile techniques in daily work==		==Agile techniques for daily work==
	On a more day to day level in a development team or project team, research was carried out to determine the most used techniques to adhere the Agile principles in such work <ref name="Annual report" />. The five techniques are presented bellow in order of popularity:		On a more day to day level in a development team or project team, research was carried out to determine the most used techniques to adhere the Agile principles in such work <ref name="Annual report" />. The five techniques are presented bellow in order of popularity:

S183653 at 16:51, 9 May 2023

2023-05-09T16:51:10Z

← Older revision		Revision as of 16:51, 9 May 2023
Line 62:		Line 62:
	From an employee point of view, of those who are happy with working Agile, statistics shows that 7 out of 10 report they are satisfied due to an ‘increased collaboration’ at the workplace <ref name = "Annual report"> Regina Corso Consulting (2022). State of Agile Report, 16th Edition. State of Agile.</ref>. More than half of the same employee group report that they are satisfied due to ‘better alignment to business needs’ and 39% report it helps to a better working environment.		From an employee point of view, of those who are happy with working Agile, statistics shows that 7 out of 10 report they are satisfied due to an ‘increased collaboration’ at the workplace <ref name = "Annual report"> Regina Corso Consulting (2022). State of Agile Report, 16th Edition. State of Agile.</ref>. More than half of the same employee group report that they are satisfied due to ‘better alignment to business needs’ and 39% report it helps to a better working environment.

	=~~How is this tool usable – how~~ to ~~adapt~~ Agile?=		=Adopting to Agile=
	While the Agile Manifesto defines the values to the term, it does not include an elaborate guide of how to achieve the values in a project.		While the Agile Manifesto defines the values to the term, it does not include an elaborate guide of how to achieve the values in a project.
	When adapting the Agile practice into a project, as stated in the Manifesto for Agile Software development, the practice involves “…uncovering better ways of developing software…” <ref name="Agile Manifesto" />, meaning one must test and tailor methods and theories according to their context to adopt the Agile values.		When adapting the Agile practice into a project, as stated in the Manifesto for Agile Software development, the practice involves “…uncovering better ways of developing software…” <ref name="Agile Manifesto" />, meaning one must test and tailor methods and theories according to their context to adopt the Agile values.

S183653 at 16:49, 9 May 2023

2023-05-09T16:49:15Z

Show changes