Imagine, if you will, that as a new project manager, you find that you are also a "matchmaker." You are tasked with a project seeking its "better half." No, not a husband or a wife, but a project management method compatible with its requirements. Without knowing exactly what you’re looking for, it is challenging to find the perfect "marriage" for your project.
There are multiple methodologies available for project management, but not all projects are created equal. It is imperative to understand your options to best determine not only what suits your project, but also what suits your product owner. We can resolve part of this conundrum by comparing two of the most popular tried and true project management methods: Agile and Waterfall.
Continuing with our "matchmaking" scenario, we present behind the first door, the Agile Methodology, here to explain what allows them to thrive in project management.
Agile Methodology
I am an iterative project management method known as "Agile." Yes, as in the word agility, meaning “able to move quickly and easily [5].” If your project requires a great deal of elasticity while continuing to make progress, my method will pique your interest. Through my method, I also promote product owner satisfaction, communication, collaboration, reflection, and improvement [7]. My key strengths are best applied to projects whose requirements, timeline, and budgets may not be well-established up front [1].
A major factor that sets me apart from my acquaintance-in-management, Waterfall, is that I incorporate a concept known as "sprints." A sprint is a small portion of work within the larger project that can last from one to four weeks [4].
Graphic: Allison Dunny | References: [6, p. 75] | Created using LucidChart
Teams meet to determine what tasks need to be accomplished for the sprint’s specified duration. Then they work simultaneously on their chosen task or tasks until the end of the sprint. After each sprint, teams meet again to review the results, reflect on strengths and weaknesses, and plan the next sprint [1] [2].
Unlike Waterfall, sprinting allows feedback from the project stakeholders throughout the course of the project [1]. I focus on progress on a granular level, thus improving upon the stagnant, often extensive phases surrounding Waterfall. In Waterfall projects, the project stakeholders are typically included in checkpoints later in the process.
In my experience as Agile, the project stakeholders benefit from their involvement throughout the process, as the direction of the project may change at any time. The earlier this is discovered, however, the less costly it is to the project stakeholders. In response to the deficiencies of Waterfall, my method strives to deliver a high-quality result in the shortest amount of time [4].
Agile: The Solution to Strict
With being a new project manager, the Agile Methodology is a powerful choice to implement in many different types of projects. Agile exists with Waterfall in mind [1]. It performs where Waterfall struggles. This is why pitting these two against each other helps improve our understanding of project management as a whole.
Next, in our "matchmaking" setting, we introduce the Waterfall Methodology behind the second door, here to explain why it will not be phased out.
Waterfall Methodology
I am a linear project management method created by Winston W. Royce in 1970. I am known as "Waterfall. [1]" This is primarily because my projects are completed in sequential steps, one step (or phase), at a time. Having this structure in place allows my projects to boast a strict timeline and budget. My colleague in project management, Agile, critiques and contrasts this, but my project stakeholders appreciate their ability to plan [1].
My method is ideal for projects that have defined requirements, as well as a set beginning and end. This indicates the project stakeholders and the project management team already know what the end result needs to be. For example, due to safety requirements, my method is necessary for many projects concerning government, construction, or manufacturing [3] [4].
It is the responsibility of the project management team to work comprehensively through each of my five phases to achieve the desired end result [3] [4].
Graphic: Allison Dunny | References: [3] [6, p. 65]
Graphic: Allison Dunny | References: [3] [6, p. 65] | Created using LucidChart
With my method, team members perform specific roles throughout the course of the project, rather than take on different types of tasks, as performed with Agile [7]. Once again, this helps maintain the consistency and expectations established from the beginning of the project.
Team progress throughout the phases is continuously measured with detailed documentation, and we concern our project stakeholders with progress reports when necessary [7]. Because my process is generally predictable, project management teams employing my methods will typically withhold smaller details from our stakeholders until we have a product or service that is nearly complete [3].
While my largest critique by Agile (and its users) is my lack of flexibility, this proves necessary in certain instances. It is why I am still a relevant method in project management today. With some projects, my method can save time and reduce costs, but with others, having to troubleshoot and shift back to a previous phase can be costly [1][3]. I have stressed that my method is a proponent of preparation. To deliver the highest quality result using my Waterfall method, a thorough understanding of the project is crucial to resolving many superficial problems before they occur.
The Key Takeaway: Know Your Project
Waterfall is applicable in the right scenario. Its biggest weakness in comparison with Agile is also its major strength. Seasoned project managers respect and comprehend the differences between Agile and Waterfall. They select the method or methods that will achieve the best possible outcome for their project, rather than attach themselves strictly to one method [3].
With knowing how the Agile and Waterfall Methodologies operate, you are better equipped as a new project manager to evaluate your own projects. You can “marry” your projects to the perfect project management method with confidence. And best of all, you can achieve customer satisfaction through the success of your projects.
References
[1] L. Hoory, C. Bottorff. “Agile Vs. Waterfall: Which Project Management Methodology Is Best For You?” Forbes. https://www.forbes.com/advisor/business/agile-vs-waterfall-methodology/ (Accessed January 27, 2024).
[2] L. Davis. “What is Agile Project Management? The Ultimate Guide.” Forbes. https://www.forbes.com/advisor/business/what-is-agile-project-management/ (Accessed January 27, 2024).
[3] L. Hoory, C. Bottorff. “What is Waterfall Methodology? Here’s How It Can Help Your Project Management Strategy.” Forbes. https://www.forbes.com/advisor/business/what-is-waterfall-methodology/ (Accessed January 27, 2024).
[4] No Author. “Agile vs. Waterfall.” ProductPlan. https://www.productplan.com/learn/agile-vs-waterfall/ (Accessed January 27, 2024).
[5] No Author. “Agile Methodology Basics.” Wrike. https://www.wrike.com/project-management-guide/agile-methodology-basics/#agile-vs-waterfall-project-management (Accessed January 26, 2024).
[6] K. Schwalbe, et al, Information Technology Project Management, 9th ed., Boston, MA, USA: Cengage, 2019. [Online]. Available: https://ebooks.cenreader.com/#!/reader/b2aef31a-bf2f-4c23-a0fa-63a64a662287/page/758a39896cdf87baf7a6aadddffd418f Accessed January 27, 2024.
[7] L. Lockhart. “Agile vs. Waterfall: 10 Key Differences Between the Two Methods.” Float. https://www.float.com/resources/agile-vs-waterfall/ (Accessed January 27, 2024)
댓글