The document compares the Waterfall and Agile project management methodologies. Waterfall follows a sequential design process with distinct stages and heavy documentation, while Agile uses short iterative cycles, embraces change, and values team collaboration and customer feedback. Some advantages of Waterfall are its structure and clear expectations, while disadvantages include inflexibility. Agile allows for changes and prioritizes delivering working software frequently for customer input, though the dynamic process may lack formal planning. The document recommends selecting the methodology based on the project's needs and characteristics.

1. Linkedin.com/in/jonathandonadoJONATHAN DONADO
Waterfall
vs.
Agile
… in plain English

2. Analysis
Design
Implementation
Testing
Evaluation
- Waterfall is also called the traditional project planning
method
- It relies on heavy up-front analysis and documentation of the
need and problems of the client
- A plan is formed and as a solution is constructed, it is
compared to the original plan
- The best methodology is the Systems Development Life Cycle
(SDLC):
Waterfall
Jonathan Donado Linkedin.com/in/jonathandonado

3. Waterfall
• It is easy to understand and manage as stages are
clearly defined
• Meticulous record keeping and documentation
• Client knows what to expect. Client will have an
idea of the size, cost, and timeline for the project.
Client will have a definite idea of what their
product will do in the end
• In the case of employee turnover, waterfall’s strong
documentation allows for minimal project impact
ADVANTAGES
Jonathan Donado Linkedin.com/in/jonathandonado

4. Waterfall
• It often becomes rigid and resistant to change.
• It relies heavily on initial requirements. However, if
these requirements are faulty in any manner, the
project is doomed.
• The whole product is only tested at the end. If
errors are discovered late in the process, their
existence may have affected the rest of the project.
• The plan does not take into account a client’s
evolving needs throughout the project cycle.
DISADVANTAGES
Jonathan Donado Linkedin.com/in/jonathandonado

5. Analysis
Design
Implementation
Testing
Analysis
Design
Implementation
Testing
Analysis
Design
Implementation
Testing
- Agile is method that breaks down a project into multiple
independent iterations. A set of iterations make a release of
the product to the customer.
Agile (part 1)
Analysis
Design
Implementation
Testing
Project
Linkedin.com/in/jonathandonadoJonathan Donado
Iteration 1 Iteration 2 Iteration N

6. - The project is dynamic and embraces change as it occurs during
the project
- Agile relies in the team “as a whole” for the decision making. There
is no hierarchy inside the team, and it is coordinated by a project
leader.
- Work is distributed by consensus, not by authority.
- Customer is heavily involved during the project. He participates
throughout the project to make sure that his requirements are
always met.
- Worked is delivered to the customer in small but frequent releases,
so it allows ongoing feedback.
Project
Linkedin.com/in/jonathandonadoJonathan Donado
Iteration 2Iteration 1 Iteration N
Agile (part 2)

7. • It allows for changes to be made after the initial planning
stage. It follows client’s requirements changes
• It is easier to add features that will keep the product up to
date with the latest developments in the industry.
• At the end of each sprint, project priorities are evaluated.
This allows clients to add their feedback, so that they
ultimately get the product they desire.
• The testing at the end of each sprint ensures that the
errors are caught in each cycle.
ADVANTAGES
Jonathan Donado
Agile
Linkedin.com/in/jonathandonado

8. • This dynamic methodology is not suitable for processes
that required complex decision making or formal
planning such as construction or manufacturing.
• As the initial project does not have a definitive plan, the
final product can be grossly different than what was
initially intended.
DISADVANTAGES
Jonathan Donado
Agile
Linkedin.com/in/jonathandonado

9. DISADVANTAGES
Jonathan Donado
Waterfall vs Agile
Linkedin.com/in/jonathandonado
Waterfall
Formal and Hierarchical. Project Manager is in charge.
Project is based on one single cycle with the traditional
project management process
Anticipation: No changes throughout the project
Early planning and design is key to the success of the
project
Agile
Informal. Decision are made by the entire team.
Project is based on a repetitive number of iterations that
are in one cycle or release. The product has numerous
releases.
Adaptation: Embraces changes
Product evolves with customer feedback. Product
features are added as customers see it fit

10. 15
Let’s stay in touch
Linkedin.com/in/jonathandonado
Jonathan.L.Donado@gmail.com
www.branded.me/jonathandonado
twitter.com/donadosays
Jonathan Donado
Bilingual senior general management executive
with expertise in international business and
Mergers & Acquisitions (M&A).