3. Waterfall
A methodology where all the phases of a process occur in a sequence.
Each phase of the project has a start and end point, and work on the next phase
doesn’t begin until the current phase is complete - hence why it’s called “waterfall”.
In conventional software development, the product requirements are finalized
before proceeding with the development.
3
Definition and Traits
https://www2.novacura.com/blog/agile-vs.-waterfall-for-erp-implementation
4. Waterfall
PROS CONS
present a complete, finished product time consuming
clear start and end lines difficult to make changes to
requirements
gives your project structure does not allow integrated collaboration
between developers and testers.
easy for everyone to understand Rigidity => early delays can throw off the
entire project timeline
4
Pros and cons
https://www2.novacura.com/blog/agile-vs.-waterfall-for-erp-implementation
https://www.roberthalf.com/blog/salaries-and-skills/6-basic-sdlc-methodologies-
which-one-is-best
5. Agile
A methodology that helps continuous iteration of development and testing in the
software development process.
Constantly incorporating user feedback and continuous releases with every iteration
of software development project
5
Definition and Traits
https://www2.novacura.com/blog/agile-vs.-waterfall-for-erp-implementation
https://www.visual-paradigm.com/scrum/classical-vs-agile-project-management/
6. Agile
6
Pros and cons
PROS CONS
projects implemented faster not as structured
more flexibility with regards to features,
requirements - more focus on the high-
priority work
not as documented
more collaboration with the customer
higher chance of the customer being
pleased with the final product
https://www2.novacura.com/blog/agile-vs.-waterfall-for-erp-implementation
7. Comparison
7
Waterfall vs Agile
Waterfall Agile
Development Model linear planning Iterative
Customer
involvement
Requirements gathering and delivery
phases
On-site and constantly involved
Developers Work individually within teams Collaborative
Product Features All included Most important first
Testing End of development cycle Iterative and/or Drives code
https://www.visual-paradigm.com/scrum/classical-vs-agile-project-management/
8. Comparison
KEY DIFFERENCE:
Agile allows changes in project development requirement whereas Waterfall has no
scope of changing the requirements once the project development starts.
When Waterfall focuses on upfront planning where factors like cost, scope, and time
are given importance, Agile management gives prominence to teamwork, customer
collaboration, and flexibility.
Difference between waterfall and agile comes in the development and deployment
stages. Instead of trying to present a full, finished product all at once, the Agile
methodology focuses on what’s most important right now.
8
https://www.guru99.com/waterfall-vs-agile.html
https://www.visual-paradigm.com/scrum/classical-vs-agile-project-management/
Waterfall Agile
9. Comparison
9
https://dzone.com/articles/agile-vs-waterfall-methodology
The graph (2011 CHAOS Manifesto from the Standish Group) shows the
specific results reported from a study conducted based on small projects:
The graph (2011 CHAOS Manifesto from the Standish Group) shows the
specific results reported from a study conducted based on projects executed
from 2002 to 2012
https://www.visual-paradigm.com/scrum/classical-vs-agile-project-
management/
10. WHEN TO USE?
Waterfall approach is used where the end result is fixed.
Example: Such as the construction of a building or car or even a phone. These
products have a physical footprint and changes to these products can almost always
be labeled as a completely new project.
Nature of the Project:
- Enhancement to an Existing Product: ✅ Waterfall
Fixed & Firm Timeline: ✅ Waterfall
Fixed, Inflexible Budget: ✅ Waterfall
10
WATERFALL
https://www.macadamian.com/learn/when-to-use-waterfall-vs-agile/
https://www.roberthalf.com/blog/salaries-and-skills/6-basic-sdlc-methodologies-
which-one-is-best
11. WHEN TO USE…
Agile is best suited to projects where the problem is complex and may not even be
fully understood at the beginning of the process, in these cases, the solutions are
even less understood and thus a very nimble process is needed.
Documentation is not produced during an Agile software development project =>
cannot be applied in healthcare, where documentation is required.
Nature of the Project:
- Greenfield Product: ✅ Agile
Short, Flexible Timeline: ✅ Agile
Budget With Wiggle Room: ✅ Agile
11
AGILE
https://www.macadamian.com/learn/when-to-use-waterfall-vs-agile/
https://www.pmi.org/learning/library/integrating-agile-methodology-waterfall-
environment-6311
12. Conclusion
It’s not a matter of deciding which development methodology is “the best” in general, but
rather which is most suitable for your product’s development so that your team can adopt
the appropriate tools, technologies and processes that will result in successful product
delivery
12
Waterfall vs Agile
https://www.macadamian.com/learn/when-to-use-waterfall-vs-agile/
