A Quick Comparison for In-House Teams

Lucy Walker

Agile and Waterfall Methodologies

Overview

The waterfall methodology was first introduced as a computer software technique in 1970. This approach was new and is based on the belief that all required work must be completely finished in one department before the next department begins their work on the project. 

  • The waterfall methodology is a linear project management approach.
Things can get murky when a project moves downstream without collaboration.

The agile methodology was introduced around 2000, also as a technique for software development. Instead of a sequence of work moving through departments, agile emphasizes the importance of collaboration and a cross-functional team at every stage of the project. Change and feedback are given throughout the project process. The risk of project failure or underwhelming results is decreased as problems are addressed at each stage–as opposed to just at the final stage evaluation in a waterfall process. 

  • Agile methodology focuses on continuous improvement at each stage of a project through regular checkpoints with the team.  
Things get rocking when the team is united at every point in the process.

The Agile Process has its own words/definitions: 

This quick video defines some of the key concepts of Agile. https://www.youtube.com/watch?v=g04FLZ2v3G8 

  • Product roadmap: high-level view of the requirements needed to achieve. This provides a general time framework for the project. 
  • Product backlog: full list of what needs to be completed/what needs to go into the project–items are listed in order. 
  • (Daily) Scrum: a coordinated meeting held daily where each team explains what they finished the day before, what they are planning on finishing today, and if they have any questions/other feedback
  • Sprint: a short project cycle where the team completes a mini goal set to keep the project on track

Analysis: 

In the last 20 years, Agile has grown from a software process to a widely adopted, proven methodology for many types of businesses and internal teams. Agile is an excellent process for creative departments. The fluid nature of the creative process involves many revisions, many meetings, much feedback, and can include internal and external testing. Creative departments have specialty departments of graphics, copy, research, and more. The collaborative strength and goal of improvement at each stage makes agile a good fit for innovation and creativity, as well as staying customer-focused. 

Agile MethodologyWaterfall Methodology
Allows all teams to collaborate and
fully understand the scope of the project.

Used when the project requirements are unknown/not specific.

Changes are welcomed throughout the project.

Client feedback is
important
throughout the project

Allows for there to be a
partial success at any
point in the
project– helps the team
to stay on the right track (decreases risk)

Provides more flexibility (time
allotted for certain teams to take more
time than others)
Each team is only responsible for
their role in the project. 

Works, when the requirements of the project are straightforward and know fully beforehand.

Changes aren’t allowed to be made in the overall process once begun

Client feedback is only
allowed at certain milestones 

Doesn’t allow for partial
success– would have to start
over (increases risk)

Flexibility is limited (each
team has deadlines they
are required to meet in
order for the next team to
start working)

Sources: 

https://www.dummies.com/careers/project-management/agile-project-management-for-dummies-cheat-sheet/
https://www.projectmanager.com/software/use-cases/waterfall-methodology