Agile model - Revision history

S202256: /* Scrum */

2022-03-20T11:36:56Z

Scrum

← Older revision		Revision as of 11:36, 20 March 2022
Line 98:		Line 98:
	* '''Scrum master''': responsible for organizing the team, removing obstacles to progress and establishing the Scrum methodology.		* '''Scrum master''': responsible for organizing the team, removing obstacles to progress and establishing the Scrum methodology.
	* '''Product owner''': responsible for maximizing the value of the product resulting from the work of the Scrum team and for the delivery of the functionality at each iteration. It also creates and updates the product backlog and prioritizes the tasks.		* '''Product owner''': responsible for maximizing the value of the product resulting from the work of the Scrum team and for the delivery of the functionality at each iteration. It also creates and updates the product backlog and prioritizes the tasks.
	* '''Scrum team''': small cross-functional team of people developing the project. It consists of one ~~scrum mater~~, one product owner and developers. There aren’t hierarchies within the team and it is typically formed by 10 or fewer people.		* '''Scrum team''': small cross-functional team of people developing the project. It consists of one Scrum master, one product owner and developers. There aren’t hierarchies within the team and it is typically formed by 10 or fewer people.

	Sprints are divided into four different stages. First, the '''Sprint planning''', is the beginning of the sprint where the work to be done is defined and planned. It is created by the entire Scrum team and the outcome is the sprint backlog, which includes the items from the product backlog selected to be implemented in the sprint and the plan for delivering them.		Sprints are divided into four different stages. First, the '''Sprint planning''', is the beginning of the sprint where the work to be done is defined and planned. It is created by the entire Scrum team and the outcome is the sprint backlog, which includes the items from the product backlog selected to be implemented in the sprint and the plan for delivering them.

S202256: /* Scrum */

2022-03-20T11:35:43Z

Scrum

← Older revision		Revision as of 11:35, 20 March 2022
Line 91:		Line 91:
	The requirements and attributes of the product are defined in the '''Product backlog'''. It is a repository of what needs to be done to improve the product and is continuously updated during the development of the project. It defines the '''Product goal''', which is the long-term objective for the Scrum team.		The requirements and attributes of the product are defined in the '''Product backlog'''. It is a repository of what needs to be done to improve the product and is continuously updated during the development of the project. It defines the '''Product goal''', which is the long-term objective for the Scrum team.

	The items in the product backlog are grouped into '''Sprint backlogs'''. Each sprint has a sprint ~~Backlog~~ which defines the '''Sprint goal''', the set of selected items from the product backlog that would be implemented in the sprint, as well as the actionable plan for delivering. It is also updated throughout the process by the developers.		The items in the product backlog are grouped into '''Sprint backlogs'''. Each sprint has a sprint backlog which defines the '''Sprint goal''', the set of selected items from the product backlog that would be implemented in the sprint, as well as the actionable plan for delivering. It is also updated throughout the process by the developers.

	The goal of each sprint is to add value and functionalities to the project, which are called '''Increments'''. Increments are concrete steps towards the product goal. Each increment is additive, meaning that all the increments should work together. Multiple increments can be created within a sprint.		The goal of each sprint is to add value and functionalities to the project, which are called '''Increments'''. Increments are concrete steps towards the product goal. Each increment is additive, meaning that all the increments should work together. Multiple increments can be created within a sprint.

S202256: /* Scrum */

2022-03-20T11:35:03Z

Scrum

← Older revision		Revision as of 11:35, 20 March 2022
Line 87:		Line 87:
	Scrum <ref>Maximini, Dominik (2015) [https://link.springer.com/book/10.1007/978-3-319-11827-7 The Scrum Culture]. Springer International Publishing.</ref> is an agile development method that concentrates specifically on the project management point of view. As the agile philosophy indicates, it employs an iterative and incremental approach and aims to understand customer needs and deliver value to them in short cycles, prioritizing the most valuable features. It is mainly used in product management.		Scrum <ref>Maximini, Dominik (2015) [https://link.springer.com/book/10.1007/978-3-319-11827-7 The Scrum Culture]. Springer International Publishing.</ref> is an agile development method that concentrates specifically on the project management point of view. As the agile philosophy indicates, it employs an iterative and incremental approach and aims to understand customer needs and deliver value to them in short cycles, prioritizing the most valuable features. It is mainly used in product management.

	Each iteration of Scrum is known as '''Sprint'''. At the end of each sprint, the team delivers a product functionality. ~~sprints~~ have fixed lengths, typically a maximum of one month, and a new sprint starts immediately after the conclusion of the previous one. Each sprint could be considered as a short project.		Each iteration of Scrum is known as '''Sprint'''. At the end of each sprint, the team delivers a product functionality. Sprints have fixed lengths, typically a maximum of one month, and a new sprint starts immediately after the conclusion of the previous one. Each sprint could be considered as a short project.

	The requirements and attributes of the product are defined in the '''Product backlog'''. It is a repository of what needs to be done to improve the product and is continuously updated during the development of the project. It defines the '''Product goal''', which is the long-term objective for the Scrum team.		The requirements and attributes of the product are defined in the '''Product backlog'''. It is a repository of what needs to be done to improve the product and is continuously updated during the development of the project. It defines the '''Product goal''', which is the long-term objective for the Scrum team.

S202256: /* Agile vs. Traditional methods */

2022-03-20T11:34:02Z

Agile vs. Traditional methods

← Older revision		Revision as of 11:34, 20 March 2022
Line 73:		Line 73:
	Traditional methods follow a sequential process where each stage needs to be completed before the next one can begin. On the other hand, agile breaks down the project development into smaller and adaptive iterations. For this reason, agile doesn't require a detailed planning as there is the opportunity to adapt the work in previous iterations. The team is able to adapt to changing product requirements dynamically and the release and feedback through iterations help to minimize the risk of any major failures in the future and more likely, better align the outcome with the expectations. This fact can, however, lead to the risk of changes not being communicated effectively and cause problems in changing priorities. On the other hand, it requires the customer to be available during the whole development process.		Traditional methods follow a sequential process where each stage needs to be completed before the next one can begin. On the other hand, agile breaks down the project development into smaller and adaptive iterations. For this reason, agile doesn't require a detailed planning as there is the opportunity to adapt the work in previous iterations. The team is able to adapt to changing product requirements dynamically and the release and feedback through iterations help to minimize the risk of any major failures in the future and more likely, better align the outcome with the expectations. This fact can, however, lead to the risk of changes not being communicated effectively and cause problems in changing priorities. On the other hand, it requires the customer to be available during the whole development process.

	The two different methods also differ in the way in which the work of the project is delivered<ref>Managing Successful Projects with PRINCE2 6th Edition (2017). TSO</ref>. While traditional methods development steps take place in sequences and the project is delivered at the end of the development process, agile ~~deliver~~ smaller projects more frequently at the end of each iteration.		The two different methods also differ in the way in which the work of the project is delivered<ref>Managing Successful Projects with PRINCE2 6th Edition (2017). TSO</ref>. While traditional methods development steps take place in sequences and the project is delivered at the end of the development process, agile delivers smaller projects more frequently at the end of each iteration.

	In conclusion, agile can be defined as a project management approach that provides flexibility, while traditional methods offer a better pre-defined and more specific framework that follows a sequential process.		In conclusion, agile can be defined as a project management approach that provides flexibility, while traditional methods offer a better pre-defined and more specific framework that follows a sequential process.

S202256: /* Agile vs. Traditional methods */

2022-03-20T11:32:05Z

Agile vs. Traditional methods

← Older revision		Revision as of 11:32, 20 March 2022
Line 69:		Line 69:
	== Agile vs. Traditional methods ==		== Agile vs. Traditional methods ==

	Agile was born as an alternative to traditional development methods, such as the Waterfall, which are based on a predictive rather than an adaptive approach. Predictive methods focus on up front planning with requirements fully defined at the beginning of the project development meaning that they are less flexible. Sometimes this could become a challenge for more complex and long-term projects where it is difficult to clearly define the requirements in earlier stages. Furthermore, possible changes in the future require a more strict change control management and prioritization. However, it can be efficient for very specific and well-defined projects. Therefore, these methods demand a high level of engagement from the customer at the initial stages when defining the project scope and requirements.		Agile was born as an alternative to traditional development methods, such as the Waterfall, which are based on a predictive rather than an adaptive approach. Predictive methods focus on up front planning with requirements fully defined at the beginning of the project development meaning that they are less flexible. Sometimes this could become a challenge for more complex and long-term projects where it is difficult to clearly define the requirements in earlier stages. Furthermore, possible changes in the future require a more strict change control management and prioritization. However, this approach can be efficient for very specific and well-defined projects. Therefore, these methods demand a high level of engagement from the customer at the initial stages when defining the project scope and requirements.

	Traditional methods follow a sequential process where each stage needs to be completed before the next one can begin. On the other hand, agile breaks down the project development into smaller and adaptive iterations. For this reason, agile doesn't require a detailed planning as there is the opportunity to adapt the work in previous iterations. The team is able to adapt to changing product requirements dynamically and the release and feedback through iterations help to minimize the risk of any major failures in the future and more likely, better align the outcome with the expectations. This fact can, however, lead to the risk of changes not being communicated effectively and cause problems in changing priorities. On the other hand, it requires the customer to be available during the whole development process.		Traditional methods follow a sequential process where each stage needs to be completed before the next one can begin. On the other hand, agile breaks down the project development into smaller and adaptive iterations. For this reason, agile doesn't require a detailed planning as there is the opportunity to adapt the work in previous iterations. The team is able to adapt to changing product requirements dynamically and the release and feedback through iterations help to minimize the risk of any major failures in the future and more likely, better align the outcome with the expectations. This fact can, however, lead to the risk of changes not being communicated effectively and cause problems in changing priorities. On the other hand, it requires the customer to be available during the whole development process.

S202256: /* Agile Manifesto */

2022-03-20T11:30:29Z

Agile Manifesto

← Older revision		Revision as of 11:30, 20 March 2022
Line 43:		Line 43:
	In the 1990’s, because of the fast-changing new technologies, the software development industry realized that it couldn’t move fast enough to meet customers’ demands and requirements. On February 2001, a group of software developers, who formed the Agile Alliance <ref>[https://www.agilealliance.org/the-alliance/ Agile Alliance]</ref>, gathered to discuss the main industry practices aiming to find a better approach to the traditional development process, such as the Waterfall methodology <ref>[https://en.wikipedia.org/wiki/Waterfall_model Waterfall model]</ref>. They ended up creating the Agile Manifesto <ref>Beck, K., et al (2001) [https://agilemanifesto.org/ "Manifesto for Agile Software Development"]</ref>, that marked the birth of agile as a methodology.		In the 1990’s, because of the fast-changing new technologies, the software development industry realized that it couldn’t move fast enough to meet customers’ demands and requirements. On February 2001, a group of software developers, who formed the Agile Alliance <ref>[https://www.agilealliance.org/the-alliance/ Agile Alliance]</ref>, gathered to discuss the main industry practices aiming to find a better approach to the traditional development process, such as the Waterfall methodology <ref>[https://en.wikipedia.org/wiki/Waterfall_model Waterfall model]</ref>. They ended up creating the Agile Manifesto <ref>Beck, K., et al (2001) [https://agilemanifesto.org/ "Manifesto for Agile Software Development"]</ref>, that marked the birth of agile as a methodology.

	This document contains the four basic values and twelve principles that are characteristic of agile philosophy.		This document contains the four basic values and twelve principles that are characteristic of the agile philosophy.

	Agile main values defined in the Agile Manifesto:		Agile main values defined in the Agile Manifesto:

S202256: /* Agile Manifesto */

2022-03-20T11:30:21Z

Agile Manifesto

← Older revision		Revision as of 11:30, 20 March 2022
Line 43:		Line 43:
	In the 1990’s, because of the fast-changing new technologies, the software development industry realized that it couldn’t move fast enough to meet customers’ demands and requirements. On February 2001, a group of software developers, who formed the Agile Alliance <ref>[https://www.agilealliance.org/the-alliance/ Agile Alliance]</ref>, gathered to discuss the main industry practices aiming to find a better approach to the traditional development process, such as the Waterfall methodology <ref>[https://en.wikipedia.org/wiki/Waterfall_model Waterfall model]</ref>. They ended up creating the Agile Manifesto <ref>Beck, K., et al (2001) [https://agilemanifesto.org/ "Manifesto for Agile Software Development"]</ref>, that marked the birth of agile as a methodology.		In the 1990’s, because of the fast-changing new technologies, the software development industry realized that it couldn’t move fast enough to meet customers’ demands and requirements. On February 2001, a group of software developers, who formed the Agile Alliance <ref>[https://www.agilealliance.org/the-alliance/ Agile Alliance]</ref>, gathered to discuss the main industry practices aiming to find a better approach to the traditional development process, such as the Waterfall methodology <ref>[https://en.wikipedia.org/wiki/Waterfall_model Waterfall model]</ref>. They ended up creating the Agile Manifesto <ref>Beck, K., et al (2001) [https://agilemanifesto.org/ "Manifesto for Agile Software Development"]</ref>, that marked the birth of agile as a methodology.

	This document contains the basic principles that are characteristic of agile philosophy ~~in project management. It outlines 4 values and 12 principles that guide agile~~.		This document contains the four basic values and twelve principles that are characteristic of agile philosophy.

	Agile main values defined in the Agile Manifesto:		Agile main values defined in the Agile Manifesto:

S202256: /* Agile Manifesto */

2022-03-20T11:29:33Z

Agile Manifesto

← Older revision		Revision as of 11:29, 20 March 2022
Line 43:		Line 43:
	In the 1990’s, because of the fast-changing new technologies, the software development industry realized that it couldn’t move fast enough to meet customers’ demands and requirements. On February 2001, a group of software developers, who formed the Agile Alliance <ref>[https://www.agilealliance.org/the-alliance/ Agile Alliance]</ref>, gathered to discuss the main industry practices aiming to find a better approach to the traditional development process, such as the Waterfall methodology <ref>[https://en.wikipedia.org/wiki/Waterfall_model Waterfall model]</ref>. They ended up creating the Agile Manifesto <ref>Beck, K., et al (2001) [https://agilemanifesto.org/ "Manifesto for Agile Software Development"]</ref>, that marked the birth of agile as a methodology.		In the 1990’s, because of the fast-changing new technologies, the software development industry realized that it couldn’t move fast enough to meet customers’ demands and requirements. On February 2001, a group of software developers, who formed the Agile Alliance <ref>[https://www.agilealliance.org/the-alliance/ Agile Alliance]</ref>, gathered to discuss the main industry practices aiming to find a better approach to the traditional development process, such as the Waterfall methodology <ref>[https://en.wikipedia.org/wiki/Waterfall_model Waterfall model]</ref>. They ended up creating the Agile Manifesto <ref>Beck, K., et al (2001) [https://agilemanifesto.org/ "Manifesto for Agile Software Development"]</ref>, that marked the birth of agile as a methodology.

	This document contains the basic principles that are characteristic of agile philosophy in project management. It outlines 4 values and 12 principles that guide ~~the~~ agile ~~philosophy~~.		This document contains the basic principles that are characteristic of agile philosophy in project management. It outlines 4 values and 12 principles that guide agile.

	Agile main values defined in the Agile Manifesto:		Agile main values defined in the Agile Manifesto:

S202256: /* What is Agile? */

2022-03-20T11:24:32Z

What is Agile?

← Older revision		Revision as of 11:24, 20 March 2022
Line 17:		Line 17:
	=== What is Agile? ===		=== What is Agile? ===

	Agile methodology is a project management process that is based on breaking down the project development into more manageable tasks, which are completed in short iterations. At the end of each iteration, it is expected to deliver smaller projects, that could be fragments of functionality. It is also an incremental process, meaning that each iteration includes the functionalities of all the previous and current iterations. Therefore, the final delivery contains all the required functionalities. The iterations normally last around two weeks, depending on the size of the project. <ref>Pimonova S. (2020) [https://doi.org/10.1007/978-3-030-10576-1_214 Agile Methodology in Education of IT Students], Application of. In: Tatnall A. (eds) Encyclopedia of Education and Information Technologies. Springer, Cham.</ref>		Agile methodology is a project management process that is based on breaking down the project development into more manageable tasks, which are completed in short iterations. At the end of each iteration, it is expected to deliver smaller projects, that could be fragments of functionality. It is also an incremental process, meaning that each iteration includes the functionalities of all the previous and current iterations. Therefore, the final delivery contains all the required project functionalities. The iterations normally last around two weeks, depending on the size of the project. <ref>Pimonova S. (2020) [https://doi.org/10.1007/978-3-030-10576-1_214 Agile Methodology in Education of IT Students], Application of. In: Tatnall A. (eds) Encyclopedia of Education and Information Technologies. Springer, Cham.</ref>

	The agile philosophy stresses the importance of centering the project development on the customers' needs. It mainly focuses on the collaboration between the development team and their customers. After each of the deliveries, it comes to a testing process together with customers so that they provide feedback to the team. This feedback will allow the team to make changes and improvements through the following iteration. <ref>Torgeir Dingsøyr, Sridhar Nerur, VenuGopal Balijepally, Nils Brede Moe (2012) [https://www.sciencedirect.com/science/article/pii/S0164121212000532?via%3Dihub A decade of agile methodologies: Towards explaining agile software development]. Journal of Systems and Software</ref> <ref>da Silva, Tiago Silva; Estácio, Bernardo (2017) [https://link.springer.com/book/10.1007/978-3-319-55907-0 Agile Methods]. Springer International Publishing.</ref>		The agile philosophy stresses the importance of centering the project development on the customers' needs. It mainly focuses on the collaboration between the development team and their customers. After each of the deliveries, it comes to a testing process together with customers so that they provide feedback to the team. This feedback will allow the team to make changes and improvements through the following iteration. <ref>Torgeir Dingsøyr, Sridhar Nerur, VenuGopal Balijepally, Nils Brede Moe (2012) [https://www.sciencedirect.com/science/article/pii/S0164121212000532?via%3Dihub A decade of agile methodologies: Towards explaining agile software development]. Journal of Systems and Software</ref> <ref>da Silva, Tiago Silva; Estácio, Bernardo (2017) [https://link.springer.com/book/10.1007/978-3-319-55907-0 Agile Methods]. Springer International Publishing.</ref>

S202256: /* Abstract */

2022-03-20T11:23:54Z

Abstract

← Older revision		Revision as of 11:23, 20 March 2022
Line 9:		Line 9:
	Agile first appeared in the early 1990s within the software development industry and is based on the Agile Manifesto and its 12 principles. Since then, many agile frameworks have emerged such as Scrum and Extreme Programming (XP). Nowadays, agile has become very popular within many organizations.		Agile first appeared in the early 1990s within the software development industry and is based on the Agile Manifesto and its 12 principles. Since then, many agile frameworks have emerged such as Scrum and Extreme Programming (XP). Nowadays, agile has become very popular within many organizations.

	This article introduces the agile concept and presents the main values and principles defined in the Agile Manifesto. Next, it compares agile over the traditional project management methods and then describes the different agile frameworks, Scrum and Extreme Programming and its applications. The ~~last part of the~~ article ~~mentions~~ possible limitations of agile.		This article introduces the agile concept and presents the main values and principles defined in the Agile Manifesto. Next, it compares agile over the traditional project management methods and then describes the different agile frameworks, Scrum and Extreme Programming and its applications. The article concludes by analyzing possible limitations of agile.

	__TOC__		__TOC__