Waterfall vs. Agile Methodology - Revision history

Tkokotas at 18:41, 17 November 2018

2018-11-17T18:41:35Z

← Older revision		Revision as of 18:41, 17 November 2018
Line 1:		Line 1:
			''Developed by Julian Ofenstein''


	There are two main software development methodologies: Waterfall and Agile. A development methodology is a procedure used by an engineering team in order to create the desired product.		There are two main software development methodologies: Waterfall and Agile. A development methodology is a procedure used by an engineering team in order to create the desired product.
	The Waterfall methodology represents the traditional approach, where the development process is conducted in a linear series of events. On its way toward the conclusion, the progress flows continuously through the phases of a project lifecycle (analysis, design, development, testing, release) like a waterfall. The entire project is planned in advance.		The Waterfall methodology represents the traditional approach, where the development process is conducted in a linear series of events. On its way toward the conclusion, the progress flows continuously through the phases of a project lifecycle (analysis, design, development, testing, release) like a waterfall. The entire project is planned in advance.

Bekis at 15:18, 2 October 2017

2017-10-02T15:18:08Z

← Older revision		Revision as of 15:18, 2 October 2017
Line 1:		Line 1:
	~~Most~~ software development ~~projects apply either the~~ Waterfall or Agile ~~methodology~~. A development methodology is a procedure used by an engineering team in order to create the desired product.		There are two main software development methodologies: Waterfall and Agile. A development methodology is a procedure used by an engineering team in order to create the desired product.
	The Waterfall methodology represents the traditional approach, where the development process is conducted in a linear series of events. On its way toward the conclusion, the progress flows continuously through the phases of a project (analysis, design, development, testing, release) like a waterfall. The entire project is planned in advance.		The Waterfall methodology represents the traditional approach, where the development process is conducted in a linear series of events. On its way toward the conclusion, the progress flows continuously through the phases of a project lifecycle (analysis, design, development, testing, release) like a waterfall. The entire project is planned in advance.
	Agile is a more recently developed software development methodology, where the linear approach is replaced by an incremental, iterative one. Instead of planning the whole project in advance, Agile enables the adaption of requirements during the whole project.		Agile is a more recently developed software development methodology, where the linear approach is replaced by an incremental, iterative one. Instead of planning the whole project in advance, Agile enables the adaption of requirements during the whole project.<BR>
	This article provides an introduction to each methodology, ~~a comparison~~, and examples of use, in order to facilitate the decision whether Agile or Waterfall is more suitable for the next project.		This article provides an introduction to each methodology, their pros and cons, and examples of use, in order to facilitate the decision whether Agile or Waterfall is more suitable for the next project.

	=Waterfall Methodology=		=Waterfall Methodology=

Bekis: /* Waterfall Methodology */

2017-09-29T19:03:30Z

Waterfall Methodology

← Older revision		Revision as of 19:03, 29 September 2017
Line 9:		Line 9:


	[[File:Waterfall.png\|thumb\|right\|500px\|Figure 2: Waterfall Model]]		[[File:Waterfall.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]

	'''Analysis'''		'''Analysis'''

Bekis: /* Waterfall Methodology */

2017-09-29T18:57:21Z

Waterfall Methodology

← Older revision		Revision as of 18:57, 29 September 2017
Line 9:		Line 9:


	[[File:~~Picture~~]]		[[File:Waterfall.png\|thumb\|right\|500px\|Figure 2: Waterfall Model]]

	'''Analysis'''		'''Analysis'''

Bekis: /* Waterfall Methodology */

2017-09-29T18:55:42Z

Waterfall Methodology

← Older revision		Revision as of 18:55, 29 September 2017
Line 9:		Line 9:


	[[File:~~NewModel.png\|thumb\|right\|500px\|Figure 1: Waterfall Model~~]]		[[File:Picture]]

	'''Analysis'''		'''Analysis'''

Bekis: /* Waterfall Methodology */

2017-09-29T18:54:14Z

Waterfall Methodology

← Older revision		Revision as of 18:54, 29 September 2017
Line 9:		Line 9:


	[[File:~~Waterfall~~.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]		[[File:NewModel.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]

	'''Analysis'''		'''Analysis'''

Bekis: /* Waterfall Methodology */

2017-09-29T18:50:11Z

Waterfall Methodology

← Older revision		Revision as of 18:50, 29 September 2017
Line 9:		Line 9:


	[[File:~~NewModel~~.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]		[[File:Waterfall.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]

	'''Analysis'''		'''Analysis'''

Bekis: /* Waterfall Methodology */

2017-09-29T18:49:30Z

Waterfall Methodology

← Older revision		Revision as of 18:49, 29 September 2017
Line 9:		Line 9:


	[[File:~~NewWaterfall~~.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]		[[File:NewModel.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]

	'''Analysis'''		'''Analysis'''

Bekis: /* Waterfall Methodology */

2017-09-29T18:47:28Z

Waterfall Methodology

← Older revision		Revision as of 18:47, 29 September 2017
Line 9:		Line 9:


	[[File:~~Waterfall~~.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]		[[File:NewWaterfall.png\|thumb\|right\|500px\|Figure 1: Waterfall Model]]

	'''Analysis'''		'''Analysis'''

Bekis: /* Findings and Conclusion */

2017-09-29T16:50:08Z

Findings and Conclusion

← Older revision		Revision as of 16:50, 29 September 2017
Line 203:		Line 203:
	=Findings and Conclusion=		=Findings and Conclusion=

	As already discussed, the Waterfall model is a linear model with a sequential set of processes where the development "flows" from the start point to the delivery of a working product with several stages in between. Waterfall is a plan-driven methodology and hence, the whole project strictly follows a clear plan, which requires extensive planning upfront. That allows an estimation of costs and timeline which can be discussed with the customer in advance. The existence of an elaborated plan and clear documentation also results in a more secure project as everyone exactly knows what to do.<BR>		As already discussed, the Waterfall model is a linear model with a sequential set of processes where the development "flows" from the start point to the delivery of a working product with several stages in between. Waterfall is a plan-driven methodology and hence, the whole project strictly follows a clear plan, which requires extensive planning upfront. That allows an estimation of costs and timeline which can be discussed with the customer in advance. The existence of an elaborated plan and clear documentation also results in a more secure project as everyone exactly knows what to do and new members can easily join the team.<BR>
	In comparison, the Agile methodology provides flexible models which enable adaptive planning and development. While the product delivery at Waterfall occurs at the very end of the process, Agile methods are divided into small releases which provide the customer with small increments of the final product. During several iterations, the team works on this small packages of the product what allows direct customer feedback at the end of every iteration. Thus, rapid and effective responses to changing customer requirements are possible. But in return, it also requires the permanent availability of the customer.<ref name= "Applying Agile Principles"/>		In comparison, the Agile methodology provides flexible models which enable adaptive planning and development. While the product delivery at Waterfall occurs at the very end of the process, Agile methods are divided into small releases which provide the customer with small increments of the final product. During several iterations, the team works on this small packages of the product what allows direct customer feedback at the end of every iteration. Thus, rapid and effective responses to changing customer requirements are possible. But in return, it also requires the permanent availability of the customer.<ref name= "Applying Agile Principles"/>

			Waterfall and Agile are two very different methodologies and it depends on the given conditions which approach is more suitable and promising. Thus, before chosing one methodology, the team/organization must analyse internal and external circumstances and estimate the eligibility of each approach.

	=Annotated Bibliography=		=Annotated Bibliography=