The document compares the Waterfall and Agile models of software development. The Waterfall model follows sequential phases from requirements to deployment, while the Agile model emphasizes iterative development and frequent customer feedback. Waterfall aims for predictability and documentation but can face challenges from changes, while Agile enables adaptation but may lack up-front planning. Examples provided include using Waterfall for systems like healthcare apps and Agile for websites and social media.
2. Outline
2
What is Waterfall model?
Advantages and disadvantages?
What is Agile model?
Advantages and disadvantages?
Examples
Summary
References
3. What is Waterfall?
Waterfall Model followed in the sequential order, and so project
development team only moves to next phase of development or
testing if the previous step completed successfully.
3https://www.guru99.com/waterfall-vs-agile.html
4. What is Waterfall?
In waterfall model, resources and documentation are very important.
We need to plan every step (how many developers/what resources/what
position is suitable for them…)
Also, prepare all the possibilities that can happen during the process.
About documentation, there are multiple teams to create a product.
So, we should keep everything happened in each phase to be easy to keep
track on it.
After each phase, we have already learned some lessons.
The next step will be stronger than the previous step. This will save our
time a lot.
4https://www.youtube.com/watch?v=LxEmGNgqYJA&list=WL&index=40&t=10s
5. Waterfall
Developers and customers agree
on what will be delivered early
in the development lifecycle.
Throughout the development
effort, it’s possible for various
members of the team to be
involved or to continue with
other work.
Customer’s presence is not
strictly required after the
requirements phase.
5
Advantages
Customers are not always able to
visualize an application from a
requirements document.
Customer will be dissatisfied
with their delivered software
product.
As all deliverables are based
upon documented requirements,
a customer may not see what will
be delivered until it’s almost
finished. By that time, changes
can be difficult (and costly) to
implement.
Disadvantages
6. What is Agile?
Agile methodology is a practice that helps continuous iteration of
development and testing in the software development process. In this
model, development and testing activities are parallel. This process allows
more communication between customers, developers, managers, and
testers.
6https://www.guru99.com/waterfall-vs-agile.html
7. What is Agile?
4 key roles:
• Product owner: define features of product
• Scrum master: prioritize tasks of each sprint
• Team members: create and develop product
• Users: use product and give feedback.
7
https://www.youtube.com/watch?v=fDLuObNgPBM&list=WL&index=40
8. What is Agile?
Individuals and interactions − In Agile development, self-organization
and motivation are important, as are interactions like co-location and pair
programming.
Working software − Demo working software is considered the best means
of communication with the customers to understand their requirements.
Customer collaboration − continuous customer interaction is very
important to get proper product requirements.
Responding to change − Agile Development is focused on quick
responses to change and continuous development.
8
Values of Agile
9. Agile
The customer has frequent and
early opportunities to see the
work.
The customer gains a strong
sense of ownership.
This way of approach will bring
product faster to customers.
9
Advantages
The very high degree of
customer involvement may
present problems for some
customers.
Cost of implementing an agile
method is little more compared
to other development
methodologies.
The project can easily go off
track if the project manager is
not clear what outcome he/she
wants.
Disadvantages
10. Examples
Healthcare website:
• Sensitivity of people’s health
• Work right without problems
• Have support staff
• Prepare thousands of scenarios
for users.
Banking application:
• Money is a sensitive issue
• Application’s quality affects the
bank’s quality
• Work well anytime
10
Waterfall
Online store:
• Not life or death issue
• No worry about errors
• Users can go back when it is not
successful at the first time
Social media:
• Adapt to new users base quickly
• Get feedback, design new
features and deploy quickly
• No big deal when having errors
Agile
https://www.youtube.com/watch?v=LxEmGNgqYJA&list=WL&index=40&t=10s
11. Summary
Spending time on research and
preparing. Then, devote time to
develop the product.
Focus on quality, completeness,
testing.
Get it right for the first time
Large scale projects -> more
accurate estimations and high-
recommended quality product.
Clear expectation for the
product.
11
Waterfall
Small and fast sample then ask
for feedback to continue the
project.
Fast iteration, small product,
frequent updates.
Many changes during the
process.
Unclear expectation for the
product.
Agile
https://www.youtube.com/watch?v=LxEmGNgqYJA&list=WL&index=40&t=10s