Scribd
Upload
37 views6 pages

Agile Vs Waterfall Case Study

ABC Company assigned two teams to develop a web browser using different methodologies: Team A used the Waterfall model and missed the deadline, while Team B employed the Agile model and completed the project on time. The Agile approach allowed for flexibility, early feedback, and adaptability, leading to higher customer satisfaction. In contrast, the Waterfall model proved to be rigid and less responsive to changes, resulting in a delayed project completion.

Uploaded by

GORANTLA JAGADEEP
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
37 views6 pages

Agile Vs Waterfall Case Study

ABC Company assigned two teams to develop a web browser using different methodologies: Team A used the Waterfall model and missed the deadline, while Team B employed the Agile model and completed the project on time. The Agile approach allowed for flexibility, early feedback, and adaptability, leading to higher customer satisfaction. In contrast, the Waterfall model proved to be rigid and less responsive to changes, resulting in a delayed project completion.

Uploaded by

GORANTLA JAGADEEP
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Agile vs Waterfall Case Study Solution

Team A vs Team B - Web Browser Development at ABC Company


Problem Overview

Company ABC wants to build a web browser within 10 months.


Two teams assigned: Team A (Waterfall) and Team B (Agile).
Incentive: First team to finish wins a reward.
Team A - Waterfall Model

Approach: Sequential & rigid.

Phases:
- Requirement Analysis: 1.5 months
- Design: 2 months
- Coding: 4 months
- Integration & Testing: 2 months
- User Acceptance Testing: 5 weeks

Total: ~10.75 months (missed deadline)


Team B - Agile Model

Approach: Iterative & flexible.

Key Practices:
- Sprint-based development
- Frequent user feedback
- Continuous integration
- Adaptive to changes

Total: ~10 months or less (met deadline)


Outcome Comparison

Team A (Waterfall):
- Missed deadline
- Rigid structure
- Late feedback

Team B (Agile):
- Met deadline
- Flexible and adaptive
- Early and continuous feedback
Conclusion / Lessons Learned

Agile model provides:


- Greater flexibility
- Early error detection
- Higher customer satisfaction

Waterfall model is:


- Linear and rigid
- Less adaptable to change

You might also like