Agile (adaptive) model - Revision history

Marcolombardo: /* History */

2022-03-26T12:26:37Z

History

← Older revision		Revision as of 12:26, 26 March 2022
Line 30:		Line 30:
	#Working software over comprehensive documentation		#Working software over comprehensive documentation
	#Customer collaboration over contract negotiation		#Customer collaboration over contract negotiation
	#Responding to change over following a plan" <ref name="Manifesto for Agile Software Development">Manifesto for Agile Software Development, 2001 http://agilemanifesto.org </ref>		#Responding to change over following a plan." <ref name="Manifesto for Agile Software Development">Manifesto for Agile Software Development, 2001 http://agilemanifesto.org </ref>

	The twelve principles are the conceptualization of how teams and companies need to work if they want to follow the agile model.		The twelve principles are the conceptualization of how teams and companies need to work if they want to follow the agile model.

Marcolombardo: /* History */

2022-03-26T12:26:25Z

History

← Older revision		Revision as of 12:26, 26 March 2022
Line 30:		Line 30:
	#Working software over comprehensive documentation		#Working software over comprehensive documentation
	#Customer collaboration over contract negotiation		#Customer collaboration over contract negotiation
	#Responding to change over following a plan		#Responding to change over following a plan" <ref name="Manifesto for Agile Software Development">Manifesto for Agile Software Development, 2001 http://agilemanifesto.org </ref>

	~~And the~~ twelve principles are:		The twelve principles are the conceptualization of how teams and companies need to work if they want to follow the agile model.
	~~#Our highest~~ priority is to ~~satisfy~~ the ~~customer through early and continuous delivery of valuable software.~~
	~~#Welcome changing requirements~~, even ~~late~~ in development. ~~Agile processes harness change for~~ the ~~customer's competitive advantage.~~		The model is based on high priority of customer satisfaction; in order to achieve this, the people involved in the project need to share the deliveries of each iteration with the other team members and with the clients, in order to keep a high relation between them and, at the same time, if there is a need to make changes in the project, it is possible to do so even if the project is in the final stage of development. The reason why it is possible to have such a flexibility is that all the timelines are organized in order to have a short timescale, and all the deliveries are set within a time schedule ranging from two weeks to a couple of months. All the teams working on the project should work together having daily meetings, because the development of an agile project is based on trust between teams and companies. In fact, it is important that everyone is supported and motivated, keeping a good environment and giving people high motivation. Transparency and face to face conversation are the base to gather all the information needed to design the whole project. The agile model is based on software which reduces the weight of the tasks, and thanks to which it is possible to measure the daily progress. The processes of the agile model promote the sustainable development, and everyone involved shall respect the environment and the work done individually. The agility gives the possibility to have good design and excellent technical procedures thanks to the continuous attention of details. Having a very organized teamwork and individuals help designing the best architecture fulfilling the requirements. After each iteration, the teams share their ideas on how to be more effective. <ref name="Manifesto for Agile Software Development">Manifesto for Agile Software Development, 2001 http://agilemanifesto.org </ref>
	~~#Deliver working software frequently~~, from ~~a couple of~~ weeks to a couple of months~~, with a preference to~~ the ~~shorter timescale.~~
	~~#Businesspeople and developers must~~ work together daily ~~throughout~~ the project.
	~~#Build projects around~~ motivated ~~individuals. Give them the~~ environment and ~~support they need~~ and ~~trust them~~ to ~~get~~ the ~~job done~~.
	#The ~~most efficient~~ and ~~effective method of conveying information~~ to ~~and within a development team~~ is ~~face-~~to~~-face conversation.~~
	~~#Working software is~~ the ~~primary measure of~~ progress.
	~~#Agile~~ processes promote sustainable development~~. The sponsors, developers~~, and ~~users should be able to maintain a constant pace indefinitely~~.
	~~#Continuous attention~~ to ~~technical excellence and~~ good design ~~enhances agility.~~
	~~#Simplicity--~~the ~~art~~ of ~~maximizing~~ the ~~amount of work not done--is essential.~~
	~~#The~~ best ~~architectures,~~ requirements~~, and designs emerge from self-organizing teams~~.
	~~#At regular intervals~~, the ~~team reflects~~ on how to ~~become~~ more effective~~, then tunes and adjusts its behaviour accordingly”~~. <ref name="Manifesto for Agile Software Development">Manifesto for Agile Software Development, 2001 http://agilemanifesto.org </ref>

	==== Sprints of the agile model ====		==== Sprints of the agile model ====

Marcolombardo: /* Adaptive (agile model) vs. predictive (waterfall model) */

2022-03-22T23:34:05Z

Adaptive (agile model) vs. predictive (waterfall model)

← Older revision		Revision as of 23:34, 22 March 2022
Line 69:		Line 69:
	A development approach is the method utilized to design and develop product, service, or the resource involved in the life cycle of a project. Each project is different compared to another, and the approach used can change considering the complexity and volatility of it. In fact, companies with projects with a high complexity are the ones which prefer working using a predictive model, while the ones with projects with a high volatility prefer the adaptive model. <ref name="PMBOK">Project Management Institute, Inc. (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) – 7th Edition and The Standard for Project Management. Project Management Institute, Inc. (PMI). Retrieved from		A development approach is the method utilized to design and develop product, service, or the resource involved in the life cycle of a project. Each project is different compared to another, and the approach used can change considering the complexity and volatility of it. In fact, companies with projects with a high complexity are the ones which prefer working using a predictive model, while the ones with projects with a high volatility prefer the adaptive model. <ref name="PMBOK">Project Management Institute, Inc. (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) – 7th Edition and The Standard for Project Management. Project Management Institute, Inc. (PMI). Retrieved from
	https://app.knovel.com/hotlink/toc/id:kpSPMAGPMP/guide-project-management/guide-project-management</ref>		https://app.knovel.com/hotlink/toc/id:kpSPMAGPMP/guide-project-management/guide-project-management</ref>


	The adaptive strategies change exactly as fast as the real constraints and idea might change; for this reason, this approach is very useful when the requirements to develop a product have a high level of uncertainty and there can be changes during the project. The model defines a clear vision of the full project in the early phase. The development of the project is based on the user feedback, and all changes are done in accordance with the stakeholders. Usually, the method utilizes iterative and incremental approaches with a duration from one to two weeks and where each team involved in the project should deliver and share with the other teams the work done. <ref name="PMBOK">Project Management Institute, Inc. (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) – 7th Edition and The Standard for Project Management. Project Management Institute, Inc. (PMI). Retrieved from		The adaptive strategies change exactly as fast as the real constraints and idea might change; for this reason, this approach is very useful when the requirements to develop a product have a high level of uncertainty and there can be changes during the project. The model defines a clear vision of the full project in the early phase. The development of the project is based on the user feedback, and all changes are done in accordance with the stakeholders. Usually, the method utilizes iterative and incremental approaches with a duration from one to two weeks and where each team involved in the project should deliver and share with the other teams the work done. <ref name="PMBOK">Project Management Institute, Inc. (PMI). (2021). A Guide to the Project Management Body of Knowledge (PMBOK ® Guide) – 7th Edition and The Standard for Project Management. Project Management Institute, Inc. (PMI). Retrieved from

Marcolombardo: /* Limitations - Pros and Cons */

2022-03-22T23:25:09Z

Limitations - Pros and Cons

← Older revision		Revision as of 23:25, 22 March 2022
Line 96:		Line 96:
	The pros of agile model are many. First, the model is based on transparency and great collaboration between teams and not only, in fact, it a creates a strong relationship between clients and the developing team. This is done thanks to the continuous delivery of a workable product which increases the customer satisfaction. Secondly, the functionality of the model is meant to be developed quickly by cutting overall development time (the deliveres of software are reduced at 1-2 weeks) and to be demonstrated; its adaptability makes it suitable both for fixed or changing requirements and the resource requirements are minimum. With regards to the types of teams it can be applied to, the model suits in a good team environment and improves the teamwork and cross training. Moreover, the agile model provides early partial working solutions, minimal rules, easily employed documentation. It is a good model for environments that are continuously changing and evolving, as it improves flexibility to developers, and it is easy to manage. Lastly, it requires very little planning, enables concurrent development and delivery within an overall planned context. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm, SDLC - Agile Model</ref>		The pros of agile model are many. First, the model is based on transparency and great collaboration between teams and not only, in fact, it a creates a strong relationship between clients and the developing team. This is done thanks to the continuous delivery of a workable product which increases the customer satisfaction. Secondly, the functionality of the model is meant to be developed quickly by cutting overall development time (the deliveres of software are reduced at 1-2 weeks) and to be demonstrated; its adaptability makes it suitable both for fixed or changing requirements and the resource requirements are minimum. With regards to the types of teams it can be applied to, the model suits in a good team environment and improves the teamwork and cross training. Moreover, the agile model provides early partial working solutions, minimal rules, easily employed documentation. It is a good model for environments that are continuously changing and evolving, as it improves flexibility to developers, and it is easy to manage. Lastly, it requires very little planning, enables concurrent development and delivery within an overall planned context. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm, SDLC - Agile Model</ref>

	However, the agile method is not optimal for all cases. Even though the principles of the model are meant to resolve some of the drawbacks that could arise from using the waterfall approach, it is not uncommon that companies and/or organizations do not achieve the expected advantages. This is due to at least one of the following reasons. <ref name="Usage of the agile model">Agile vs Waterfall SDLCs: What’s The Difference?, Muhammad Raza http://www.bmc.com/blogs/agile-vs-waterfall/ ~~Usage of the agile model~~</ref>		However, the agile method is not optimal for all cases. Even though the principles of the model are meant to resolve some of the drawbacks that could arise from using the waterfall approach, it is not uncommon that companies and/or organizations do not achieve the expected advantages. This is due to at least one of the following reasons. <ref name="Usage of the agile model">Agile vs Waterfall SDLCs: What’s The Difference?, Muhammad Raza http://www.bmc.com/blogs/agile-vs-waterfall/ </ref>

	In the first place, it is not suitable for handling complex dependencies, as it might pose more risk of sustainability, maintainability, and extensibility of the product, if this is too complex and it is hard and difficult to measure how much effort will be needed to start the life cycle of a larger project. Moreover, the model cannot be used by all companies because it requires a certain structure and guidelines to be in place: an overall plan, an agile leader and an agile project manager are a must, without which it will not work. For the successful implementation of the model, it is fundamental that all deliveries and deadlines are strictly managed, as they dictate the scope and guarantee the correct sequence of functionalities to be delivered. Additionally, there could be some misunderstanding among groups due to the fact the documentation is not explained well or because of a lack of emphasis and it is able to result in hard transitions among phases. Moreover, the model depends heavily on customer interaction, so if the customer is not clear or does not have well-defined goals, the team can be driven in the wrong direction or if the client and the team are in different pages the project will derail. For large companies, it could be a disadvantage to use the agile model due to the fact that it entails a very high individual dependency, since it generates minimum documentation. Due to this lack of documentation, the transfer of technology to new team members may be quite challenging; this means that an agile model requires senior developers and there is no space for people without good knowledge of programming skills. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm SDLC - Agile Model </ref> Sometimes, the structure of a project becomes too complex forcing the companies to follow the waterfall model. This happens because the teams involved have not enough knowledge of how the model works or due to the fact that there is not any kind of system design.		In the first place, it is not suitable for handling complex dependencies, as it might pose more risk of sustainability, maintainability, and extensibility of the product, if this is too complex and it is hard and difficult to measure how much effort will be needed to start the life cycle of a larger project. Moreover, the model cannot be used by all companies because it requires a certain structure and guidelines to be in place: an overall plan, an agile leader and an agile project manager are a must, without which it will not work. For the successful implementation of the model, it is fundamental that all deliveries and deadlines are strictly managed, as they dictate the scope and guarantee the correct sequence of functionalities to be delivered. Additionally, there could be some misunderstanding among groups due to the fact the documentation is not explained well or because of a lack of emphasis and it is able to result in hard transitions among phases. Moreover, the model depends heavily on customer interaction, so if the customer is not clear or does not have well-defined goals, the team can be driven in the wrong direction or if the client and the team are in different pages the project will derail. For large companies, it could be a disadvantage to use the agile model due to the fact that it entails a very high individual dependency, since it generates minimum documentation. Due to this lack of documentation, the transfer of technology to new team members may be quite challenging; this means that an agile model requires senior developers and there is no space for people without good knowledge of programming skills. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm SDLC - Agile Model </ref> Sometimes, the structure of a project becomes too complex forcing the companies to follow the waterfall model. This happens because the teams involved have not enough knowledge of how the model works or due to the fact that there is not any kind of system design.

Marcolombardo: /* Limitations - Pros and Cons */

2022-03-22T23:24:01Z

Limitations - Pros and Cons

← Older revision		Revision as of 23:24, 22 March 2022
Line 96:		Line 96:
	The pros of agile model are many. First, the model is based on transparency and great collaboration between teams and not only, in fact, it a creates a strong relationship between clients and the developing team. This is done thanks to the continuous delivery of a workable product which increases the customer satisfaction. Secondly, the functionality of the model is meant to be developed quickly by cutting overall development time (the deliveres of software are reduced at 1-2 weeks) and to be demonstrated; its adaptability makes it suitable both for fixed or changing requirements and the resource requirements are minimum. With regards to the types of teams it can be applied to, the model suits in a good team environment and improves the teamwork and cross training. Moreover, the agile model provides early partial working solutions, minimal rules, easily employed documentation. It is a good model for environments that are continuously changing and evolving, as it improves flexibility to developers, and it is easy to manage. Lastly, it requires very little planning, enables concurrent development and delivery within an overall planned context. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm, SDLC - Agile Model</ref>		The pros of agile model are many. First, the model is based on transparency and great collaboration between teams and not only, in fact, it a creates a strong relationship between clients and the developing team. This is done thanks to the continuous delivery of a workable product which increases the customer satisfaction. Secondly, the functionality of the model is meant to be developed quickly by cutting overall development time (the deliveres of software are reduced at 1-2 weeks) and to be demonstrated; its adaptability makes it suitable both for fixed or changing requirements and the resource requirements are minimum. With regards to the types of teams it can be applied to, the model suits in a good team environment and improves the teamwork and cross training. Moreover, the agile model provides early partial working solutions, minimal rules, easily employed documentation. It is a good model for environments that are continuously changing and evolving, as it improves flexibility to developers, and it is easy to manage. Lastly, it requires very little planning, enables concurrent development and delivery within an overall planned context. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm, SDLC - Agile Model</ref>

	However, the agile method is not optimal for all cases. Even though the principles of the model are meant to resolve some of the drawbacks that could arise from using the waterfall approach, it is not uncommon that companies and/or organizations do not achieve the expected advantages. This is due to at least one of the following reasons. <ref name="Usage of the agile model">http://www.bmc.com/blogs/agile-vs-waterfall/ Usage of the agile model</ref>		However, the agile method is not optimal for all cases. Even though the principles of the model are meant to resolve some of the drawbacks that could arise from using the waterfall approach, it is not uncommon that companies and/or organizations do not achieve the expected advantages. This is due to at least one of the following reasons. <ref name="Usage of the agile model">Agile vs Waterfall SDLCs: What’s The Difference?, Muhammad Raza http://www.bmc.com/blogs/agile-vs-waterfall/ Usage of the agile model</ref>

	In the first place, it is not suitable for handling complex dependencies, as it might pose more risk of sustainability, maintainability, and extensibility of the product, if this is too complex and it is hard and difficult to measure how much effort will be needed to start the life cycle of a larger project. Moreover, the model cannot be used by all companies because it requires a certain structure and guidelines to be in place: an overall plan, an agile leader and an agile project manager are a must, without which it will not work. For the successful implementation of the model, it is fundamental that all deliveries and deadlines are strictly managed, as they dictate the scope and guarantee the correct sequence of functionalities to be delivered. Additionally, there could be some misunderstanding among groups due to the fact the documentation is not explained well or because of a lack of emphasis and it is able to result in hard transitions among phases. Moreover, the model depends heavily on customer interaction, so if the customer is not clear or does not have well-defined goals, the team can be driven in the wrong direction or if the client and the team are in different pages the project will derail. For large companies, it could be a disadvantage to use the agile model due to the fact that it entails a very high individual dependency, since it generates minimum documentation. Due to this lack of documentation, the transfer of technology to new team members may be quite challenging; this means that an agile model requires senior developers and there is no space for people without good knowledge of programming skills. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm SDLC - Agile Model </ref> Sometimes, the structure of a project becomes too complex forcing the companies to follow the waterfall model. This happens because the teams involved have not enough knowledge of how the model works or due to the fact that there is not any kind of system design.		In the first place, it is not suitable for handling complex dependencies, as it might pose more risk of sustainability, maintainability, and extensibility of the product, if this is too complex and it is hard and difficult to measure how much effort will be needed to start the life cycle of a larger project. Moreover, the model cannot be used by all companies because it requires a certain structure and guidelines to be in place: an overall plan, an agile leader and an agile project manager are a must, without which it will not work. For the successful implementation of the model, it is fundamental that all deliveries and deadlines are strictly managed, as they dictate the scope and guarantee the correct sequence of functionalities to be delivered. Additionally, there could be some misunderstanding among groups due to the fact the documentation is not explained well or because of a lack of emphasis and it is able to result in hard transitions among phases. Moreover, the model depends heavily on customer interaction, so if the customer is not clear or does not have well-defined goals, the team can be driven in the wrong direction or if the client and the team are in different pages the project will derail. For large companies, it could be a disadvantage to use the agile model due to the fact that it entails a very high individual dependency, since it generates minimum documentation. Due to this lack of documentation, the transfer of technology to new team members may be quite challenging; this means that an agile model requires senior developers and there is no space for people without good knowledge of programming skills. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm SDLC - Agile Model </ref> Sometimes, the structure of a project becomes too complex forcing the companies to follow the waterfall model. This happens because the teams involved have not enough knowledge of how the model works or due to the fact that there is not any kind of system design.

Marcolombardo: /* Companies which adopted the agile model */

2022-03-22T23:22:01Z

Companies which adopted the agile model

← Older revision		Revision as of 23:22, 22 March 2022
Line 83:		Line 83:

	==== Companies which adopted the agile model ====		==== Companies which adopted the agile model ====
	The agile model is an uncommon method and sometimes a challenge for big companies, because it requires strong ability of the teams, flexibility, and fast response to changes; something that does not seem to be compatible with the rigid structures of large companies. But there are some big companies like CISCO (IT), Lego (IT), Barclays (Finance), Panera Bread (IT), Ericsson (Mobile network), PlayStation (Gaming), John Deere (IT), Fitbit (technology), OpenLink (Finance), Royal Philips (medical technology company) which adopted the agile model and they got positive results from it. <ref name="Big companies associated with agile model">10 companies killing it at scaling agile,Christopher Null https://techbeacon.com/app-dev-testing/10-companies-killing-it-scaling-agile ~~Big companies associated with agile model~~</ref>		The agile model is an uncommon method and sometimes a challenge for big companies, because it requires strong ability of the teams, flexibility, and fast response to changes; something that does not seem to be compatible with the rigid structures of large companies. But there are some big companies like CISCO (IT), Lego (IT), Barclays (Finance), Panera Bread (IT), Ericsson (Mobile network), PlayStation (Gaming), John Deere (IT), Fitbit (technology), OpenLink (Finance), Royal Philips (medical technology company) which adopted the agile model and they got positive results from it. <ref name="Big companies associated with agile model">10 companies killing it at scaling agile,Christopher Null https://techbeacon.com/app-dev-testing/10-companies-killing-it-scaling-agile </ref>

	==== Examples of agile software ====		==== Examples of agile software ====

Marcolombardo: /* Companies which adopted the agile model */

2022-03-22T23:21:04Z

Companies which adopted the agile model

← Older revision		Revision as of 23:21, 22 March 2022
Line 83:		Line 83:

	==== Companies which adopted the agile model ====		==== Companies which adopted the agile model ====
	The agile model is an uncommon method and sometimes a challenge for big companies, because it requires strong ability of the teams, flexibility, and fast response to changes; something that does not seem to be compatible with the rigid structures of large companies. But there are some big companies like CISCO (IT), Lego (IT), Barclays (Finance), Panera Bread (IT), Ericsson (Mobile network), PlayStation (Gaming), John Deere (IT), Fitbit (technology), OpenLink (Finance), Royal Philips (medical technology company) which adopted the agile model and they got positive results from it. <ref name="Big companies associated with agile model">https://techbeacon.com/app-dev-testing/10-companies-killing-it-scaling-agile Big companies associated with agile model</ref>		The agile model is an uncommon method and sometimes a challenge for big companies, because it requires strong ability of the teams, flexibility, and fast response to changes; something that does not seem to be compatible with the rigid structures of large companies. But there are some big companies like CISCO (IT), Lego (IT), Barclays (Finance), Panera Bread (IT), Ericsson (Mobile network), PlayStation (Gaming), John Deere (IT), Fitbit (technology), OpenLink (Finance), Royal Philips (medical technology company) which adopted the agile model and they got positive results from it. <ref name="Big companies associated with agile model">10 companies killing it at scaling agile,Christopher Null https://techbeacon.com/app-dev-testing/10-companies-killing-it-scaling-agile Big companies associated with agile model</ref>

	==== Examples of agile software ====		==== Examples of agile software ====

Marcolombardo: /* History */

2022-03-22T23:18:00Z

History

← Older revision		Revision as of 23:18, 22 March 2022
Line 44:		Line 44:
	#Simplicity--the art of maximizing the amount of work not done--is essential.		#Simplicity--the art of maximizing the amount of work not done--is essential.
	#The best architectures, requirements, and designs emerge from self-organizing teams.		#The best architectures, requirements, and designs emerge from self-organizing teams.
	#At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly”. <ref name="Manifesto for Agile Software Development">http://agilemanifesto.org ~~Manifesto for Agile Software Development, 2001~~</ref>		#At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly”. <ref name="Manifesto for Agile Software Development">Manifesto for Agile Software Development, 2001 http://agilemanifesto.org </ref>

	==== Sprints of the agile model ====		==== Sprints of the agile model ====

Marcolombardo: /* Abstract */

2022-03-22T23:17:18Z

Abstract

← Older revision		Revision as of 23:17, 22 March 2022
Line 4:		Line 4:


	Agile model is a new way of riding the development approach and the life cycle performance domain of a Project, Program and Portfolio Management (PPPM). The focus of the model is on process adaptability and customer satisfaction. The model is based on iterative and incremental processes combined to achieve a rapid delivery of working software product. <ref name="SDLC - Agile Model">https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm ~~SDLC - Agile Model~~ </ref>		Agile model is a new way of riding the development approach and the life cycle performance domain of a Project, Program and Portfolio Management (PPPM). The focus of the model is on process adaptability and customer satisfaction. The model is based on iterative and incremental processes combined to achieve a rapid delivery of working software product. <ref name="SDLC - Agile Model">SDLC - Agile Model https://www.tutorialspoint.com/sdlc/sdlc_agile_model.htm </ref>

	Although there are some adaptive methods dating back to before 2000’s, it is possible to date the concept of agile in 2001, when it was signed the “Agile Manifesto”. The Agile Manifesto outlines four Core Values (individuals and interactions; working software; customer collaboration; and responding to change) and twelve Guiding Principles which are of key importance for any team aiming at using an agile model.		Although there are some adaptive methods dating back to before 2000’s, it is possible to date the concept of agile in 2001, when it was signed the “Agile Manifesto”. The Agile Manifesto outlines four Core Values (individuals and interactions; working software; customer collaboration; and responding to change) and twelve Guiding Principles which are of key importance for any team aiming at using an agile model.

	The agile model is an adaptive model that uses iterations called also sprints to divide the project life cycle to work with a short-term planning. It is possible to define each sprint as the sum of 5 phases: gathering, design, construction, testing, close, and after each iteration the teams receive feedback, <ref name="Agile Processes and Methodologies"> Sharma, Sheetal & Sarkar, Darothi & Gupta, Divya. (2012). Agile Processes and Methodologies: A Conceptual Study. International Journal on Computer Science and Engineering. 4. https://www.researchgate.net/publication/267706023_Agile_Processes_and_Methodologies_A_Conceptual_Study </ref> whereas the traditional models are based on a predictive approach (e.g., waterfall model). Both typologies of modelling have their pros and cons and the best approach to follow depends on the project/product.		The agile model is an adaptive model that uses iterations called also sprints to divide the project life cycle to work with a short-term planning. It is possible to define each sprint as the sum of 5 phases: gathering, design, construction, testing, close, and after each iteration the teams receive feedback, <ref name="Agile Processes and Methodologies"> Sharma, Sheetal & Sarkar, Darothi & Gupta, Divya. (2012). Agile Processes and Methodologies: A Conceptual Study. International Journal on Computer Science and Engineering. 4. https://www.researchgate.net/publication/267706023_Agile_Processes_and_Methodologies_A_Conceptual_Study </ref> whereas the traditional models are based on a predictive approach (e.g., waterfall model). Both typologies of modelling have their pros and cons and the best approach to follow depends on the project/product.

	The goal of the agile model is to assist companies in providing value more frequently to their clients, reacting quicker to changes, and eventually improving the business. <ref name="Agile Body of Knowledge">https://kanbanize.com/agile ~~Agile Body of Knowledge~~</ref> It is utilized when it is necessary to divide a large project into more reasonable tasks and complete them in short iterations throughout the project life cycle, defined as the set of phases from the start to the end of a project.		The goal of the agile model is to assist companies in providing value more frequently to their clients, reacting quicker to changes, and eventually improving the business. <ref name="Agile Body of Knowledge">Agile Body of Knowledge https://kanbanize.com/agile </ref> It is utilized when it is necessary to divide a large project into more reasonable tasks and complete them in short iterations throughout the project life cycle, defined as the set of phases from the start to the end of a project.

	The model can be applied to almost any project, but for high complexity of design and scale of projects, companies prefer to use the predictive models. It is also important that the companies adopting the agile model make sure that their employees are aware of the rules and methodologies to successfully work with such a model.		The model can be applied to almost any project, but for high complexity of design and scale of projects, companies prefer to use the predictive models. It is also important that the companies adopting the agile model make sure that their employees are aware of the rules and methodologies to successfully work with such a model.

Marcolombardo: /* Sprints of the agile model */

2022-03-22T23:16:24Z

Sprints of the agile model

← Older revision		Revision as of 23:16, 22 March 2022
Line 59:		Line 59:
	#'''Construction''': this phase is focusing on deliveries and particularly on the requirements and the constraints that the teams should follow. It is important to have a good collaboration between teams and a good interaction with customers and stakeholders.		#'''Construction''': this phase is focusing on deliveries and particularly on the requirements and the constraints that the teams should follow. It is important to have a good collaboration between teams and a good interaction with customers and stakeholders.
	#'''Testing:''' in this phase teams analyse the results with what was planned. Teams can adapt or make changes in order to have a better product. The most important work is to receive and elaborate feedback.		#'''Testing:''' in this phase teams analyse the results with what was planned. Teams can adapt or make changes in order to have a better product. The most important work is to receive and elaborate feedback.
	#'''Close:''' the iteration is finished; each team should share the results and receive feedback from the customer in order to start the new iteration. <ref name="Agile model software engineering">https://www.javatpoint.com/software-engineering-agile-model</ref> The most important thing to do in this phase is to analyse all the key-points of the project and save all the knowledge gathered.		#'''Close:''' the iteration is finished; each team should share the results and receive feedback from the customer in order to start the new iteration. <ref name="Agile model software engineering">Agile model software engineering https://www.javatpoint.com/software-engineering-agile-model</ref> The most important thing to do in this phase is to analyse all the key-points of the project and save all the knowledge gathered.

	Overall, agile is about adaptive planning, getting earlier deliveries and ensuring a steady improvement throughout every sprint. Key concepts to realize this are rapid response and adaptation to change. <ref name="Introduction to agile and waterfall">https://www.blueoceanworkshops.com/agile-adaptive-vs-waterfall-predictive-project-management/ ~~Introduction to agile and waterfall~~</ref>		Overall, agile is about adaptive planning, getting earlier deliveries and ensuring a steady improvement throughout every sprint. Key concepts to realize this are rapid response and adaptation to change. <ref name="Introduction to agile and waterfall">Introduction to agile and waterfall https://www.blueoceanworkshops.com/agile-adaptive-vs-waterfall-predictive-project-management/ </ref>

	== Applications ==		== Applications ==