Difference between Waterfall Vs Agile Vs DevOps

  Waterfall Agile DevOps
Basic philosophy

Systems are fully predictable and can be specified in advance.

Assumes business needs remain broadly similat throught project

Adjust schedule to preserve scope

Integrate business,dev and QA for rapid delivery of software

Iterative 'sprint' cycle

Assumes priority of business need may changes

Adjust scope to preserve schedule

Cross-functional teams utilize automation to enable continuous deployment of change .Constant feedback loop

Adjust scope to preserve schedule

Documentation Level Comprehensive Light Light
Automation Level Low Varied High
Delivery of Value Slow-Only at major milestones(3-6 months) Rapid(daily/Weekly) Continuous
Business ownership of Project No(Typical) Yes Yes
Response to new business needs (flexible requirements) Extremely limited due to detailed specification Responsive-iterative delivery enables prioritization High Responsive-cross-functional teams define business needs more precisely
Collaboration Low-teams operate in functional silos Improved-business is highly engaged, short dev cycle High-all stackholders involved from project start
Quality Low-issue not identified until testing phase Improved- issues identified after every sprint High-automated unit testing during development
Risk Increases as project progresses Decreases as project progress Decreases as project progresses
Customer Feedback Infrequent-at project completion Frequent-after every sprint Continuous