Waterfall methodology is a sequential process flow. In other words, it means we are planning in advance for an entire project. Much like a waterfall flowing from top to bottom, we start at the top by initiating a process, then planning, then executing, and finally monitoring and controlling the process before it’s completion. Waterfall is commonly used for projects including the mass production of tangible long-term work efforts (a fancy way of saying construction). Chances are, the scope of the project is well known in the beginning, making it easy to pre-plan and execute.

Waterfall has a very formal change control system. We move forward by planning on the scope of work and depending on the requirements collected at the very beginning of planning. This can also help us set an appropriate baseline for project costs.

1. Validation at the end

Like any project, there’s always a chance of carrying it out to completion, only for your customers to not validate your work. It’s frustrating to not produce the right end-result. Dreams are crushed and time and efforts can feel as if they’ve been wasted.

2. Change is difficult

In waterfall specifically, changes are difficult to make because we have the set plan already underway.

3. Drowning in documentation

Another downside of Waterfall methodology is all the tedious documentation. As a project manager, it’s your job to decide best practices on this. Note that the more you pre-plan, the more you’re probably documenting.

4. Possible Cancellation

If there are too many scope changes, a project can be cancelled and the team would have to start over. First they wanted bikes and now they want motorcycles? No one likes starting from scratch.

What is Agile?

Challenges to Agile

1. Difficult to select the right amount of requirements.

As we shift and change we try to produce something that meets the customers needs and provides them value.

2. Difficult to do if you’re using Scrum, XP, or feature driven development.

Any inexperience team members or even senior management that is not fully engaged can lead to chaotic and difficult implementation. This type of practice is hands on. It constantly needs to be reaffirmed and managed.

The Differences

The Differences

Agile has no clear picture of the final product
Waterfall does

2. Middle:

Agile expects change and adds features as needed
Waterfall has formally controlled change which can affects baselines

3. End:

Agile focuses on producing an increment quickly rather than quality
Waterfall focuses on quality rather than producing a result quickly