The Waterfall Model
(→Application of the Waterfall model) |
(→Application of the Waterfall model) |
||
| Line 17: | Line 17: | ||
[[File:WaterfallorAgile.png|thumb|right|500px|Figure 3: Application of the Waterfall model]] | [[File:WaterfallorAgile.png|thumb|right|500px|Figure 3: Application of the Waterfall model]] | ||
| − | '''A project are close to certainty''' when "How" is well known for example if a similar project, decision or issue have been done before and therefor the effect and cause relationship is well known. Because then there will be some experiences and learnings there can be used to predict the "How" and set up the needed requirements from the beginning. <ref | + | '''A project are close to certainty''' when "How" is well known for example if a similar project, decision or issue have been done before and therefor the effect and cause relationship is well known. Because then there will be some experiences and learnings there can be used to predict the "How" and set up the needed requirements from the beginning. <ref name= "Agile Principles"/> <ref> Stacey RD. Strategic management and organisational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref> |
| − | '''A project are far from certainty''' if the project is new to the project manager for example if it is about something new or it is an innovative project. Then it can be hard to set up the needed requirements from the beginning and therefor there will be a lot of uncertainties about the "How" and the unclear relationship between cause and effect. <ref | + | '''A project are far from certainty''' if the project is new to the project manager for example if it is about something new or it is an innovative project. Then it can be hard to set up the needed requirements from the beginning and therefor there will be a lot of uncertainties about the "How" and the unclear relationship between cause and effect. <ref name= "Agile Principles"/> <ref> Stacey RD. Strategic management and organisational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref> |
| − | '''A projects level of agreement''' is a measurement of the level of agreement about decisions and issues within the project group, the management team and the stakeholders. This is important because the project manager function varies based on the level of agreement. <ref | + | '''A projects level of agreement''' is a measurement of the level of agreement about decisions and issues within the project group, the management team and the stakeholders. This is important because the project manager function varies based on the level of agreement. <ref name= "Agile Principles"/> <ref> Stacey RD. Strategic management and organisational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002 </ref> |
Revision as of 20:54, 16 February 2022
Contents |
Abstract
The waterfall model is a Software Development Life Cycle model (SDLC) and was the first process model to be introduced. The waterfall model is easy to understand and use, it is a stage gate model which means that the model consists of stages and gates. Each phase consists of one stage and one gate. Each phase has some pre-determined activities and requirements. The current phase must be completed before the next phase can begin and to end a phase it must pass a gate. A stage is the activities, and the gate is the requirement and the review that determine whether a project can continue. The waterfall model consists of six different stages, 1) Requirements Gathering and Analysis, 2) Systems Development, 3) Systems Implementation and Coding, 4) Testing, 5) Deployment, 6) Systems Operations and Maintenance.
The waterfall model is widely used for software development, but it is also a widely criticized model. The model is often criticized for the late detection of defects in the process and how to handle change requests among other things. It is most optimal to use the waterfall model for simple projects with clear reqirements and projects that do not change through the development process.
About
The first description of the Waterfall model was written by Winston W. Royce in 1970. Back then he did not call it the Waterfall model. [1] Later it got the name because all the phases are done one by one and flows downwards like a waterfall. It is the finest and oldest known Software Development Life Cycle model (SDLC). There are defined and designed various Software Development Life Cycle models such as Spiral model, Big Bang Model, Iterative model etc. These models are also called Software Development Process Models and are all "process consisting of a sequence of planned phases to develop or to amend the software products." [2]
Application of the Waterfall model
To be a good project manager it is important to be familiar with a list of different project life cycle models and be aware of where and when to use which project life cycle whether it is a predictive or an adaptive lifecycle. To understand where and when the waterfall model potentially works best an adapted version of Stacey's matrix from Domain I: Agile Principles and Mindset by Sumanta Boral [3] is used. The Stacey Matrix is published and developed by Ralph Douglas Stacey. It is developed to give an understanding of which factors there contributes to complexity and how to address the different degrees of complexity and with that knowledge choose the best suited project life cycle. [4] The Stacey matrix is a two dimensional matrix where uncertainty of the requirements are plottet against the perceived disagreement of the stakeholders. [3]
A project are close to certainty when "How" is well known for example if a similar project, decision or issue have been done before and therefor the effect and cause relationship is well known. Because then there will be some experiences and learnings there can be used to predict the "How" and set up the needed requirements from the beginning. [3] [5]
A project are far from certainty if the project is new to the project manager for example if it is about something new or it is an innovative project. Then it can be hard to set up the needed requirements from the beginning and therefor there will be a lot of uncertainties about the "How" and the unclear relationship between cause and effect. [3] [6]
A projects level of agreement is a measurement of the level of agreement about decisions and issues within the project group, the management team and the stakeholders. This is important because the project manager function varies based on the level of agreement. [3] [7]
This article introduces
- The waterfall model
- When to use it
- Where to use it
- What each phase consists of
- Best practice
- Pros and cons.
Ref
Petersen K., Wohlin C., Baca D. (2009) The Waterfall Model in Large-Scale Development. In: Bomarius F., Oivo M., Jaring P., Abrahamsson P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29
Kramer, Mitch, Best Practices in Systems Development Lifecycle: An Analyses Based on the Waterfall Model (2018). Review of Business & Finance Studies, v. 9 (1) p. 77-84, Available at SSRN: https://ssrn.com/abstract=3131958
http://tryqa.com/what-is-waterfall-model-advantages-disadvantages-and-when-to-use-it/
References
- ↑ Petersen K., Wohlin C., Baca D. (2009) The Waterfall Model in Large-Scale Development. In: Bomarius F., Oivo M., Jaring P., Abrahamsson P. (eds) Product-Focused Software Process Improvement. PROFES 2009. Lecture Notes in Business Information Processing, vol 32. Springer, Berlin, Heidelberg. https://doi-org.proxy.findit.cvt.dk/10.1007/978-3-642-02152-7_29
- ↑ Dubey A.; Jain A.; Mantri A., "Comparative Study: Waterfall v/s Agile Model", International Journal of Engineering Sciences & Research Technology (IJESRT), 2015
- ↑ 3.0 3.1 3.2 3.3 3.4 Boral S.,"Domain I: Agile Principles and Mindset", Ace the Pmi-acp pp. 1-27, 2016
- ↑ Stacey RD. Strategic management and organisational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002
- ↑ Stacey RD. Strategic management and organisational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002
- ↑ Stacey RD. Strategic management and organisational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002
- ↑ Stacey RD. Strategic management and organisational dynamics: the challenge of complexity. 3rd ed. Harlow: Prentice Hall, 2002
