![\"Waterfall](\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/08\/Waterfall-Project-Management-An-Overview-Header.jpg\")
<\/p>\n<\/p>\n
Waterfall project management is regarded as one of the O.G.s of software development methodologies. It’s commonly known as a strict process that doesn’t allow for any changes to occur, which kind of gives it a reputation for not being the most ideal approach. But without it, we wouldn’t have other methods such as Agile<\/a> and Scrum<\/a>.<\/strong><\/p>\n In this article, we’ll provide an overview of Waterfall project management, its pros and cons, and discuss when it’s best to use it.<\/strong><\/p>\n In this article, we’ll provide an overview of Waterfall project management and discuss when it’s best to use it.<\/strong><\/p>\n Here are some of the things you\u2019ll learn:<\/p>\n Waterfall project management is one of the more traditional software development methodologies. It follows a linear, sequential design approach where progress flows downwards in one direction, like a waterfall (hence the name!).<\/span><\/p>\n A project is delivered through a set of ordered stages and until all activity within the current stage has been completed and approved, advancing to the next stage or any later stages is not possible.<\/p>\n Known for their emphasis on documentation, Gantt charts<\/a> and resource scheduling and allocation are popular Waterfall project management tools.<\/p>\n The Waterfall methodology has its origins within the manufacturing and construction industries, to which you could ascribe its stringent process. Due to the structured physical environments, the process leaves little room for changes as any changes made would result in high costs.<\/span> (Think about it, once you construct a building, it would be pretty difficult to go back and make changes.)<\/span><\/p>\n It was first formally introduced as a method for software development in an article written by Winston W. Royce<\/a> in 1970, however, the term \u201cWaterfall\u201d wasn\u2019t used. It wouldn’t be until 1976 when a paper was written <\/span>by <\/span>T.E. Bell and T.A. Thayer<\/span><\/a> that the term may have been first used.<\/span><\/p>\n There are six phases within the Waterfall methodology. You can only move on to the next phase once the current one is completed, reviewed, and approved.<\/span><\/p>\n
\n\n
\nWhat Is Waterfall Project Management?<\/strong><\/h2>\n
\nThe History of Waterfall Project Management<\/strong><\/h2>\n
![\"\"](\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/08\/waterfallprojectmanagement1.jpeg\")
<\/p>\n
\nThe Phases of Waterfall Project Management<\/strong><\/h2>\n
![\"\"](\"https:\/\/zenkit.com\/wp-content\/uploads\/2019\/08\/giphy-1.gif\")