Compare Agile Software Development (Scrum/Kanban) versus traditional Waterfall methodology.
❓ Interview Prompt: Compare Agile (iterative, 2-week sprints, adaptive) vs Waterfall (sequential phases, rigid planning) project delivery frameworks.
Evaluating software project delivery methodologies:
| Feature | Waterfall Methodology | Agile (Scrum / Kanban) |
|---|---|---|
| Workflow | Sequential phases (Requirements $\rightarrow$ Design $\rightarrow$ Dev $\rightarrow$ QA) | Iterative 2-week Sprints |
| Feedback | Customer sees working software late at end | Customer reviews working software every sprint |
| Flexibility | High cost of changing requirements late | Welcomes changing requirements dynamically |
| Risk | High risk of building wrong product | Low risk; early continuous value delivery |
Code Implementation Example
{
"framework": "Scrum",
"sprintDuration": "2 Weeks",
"ceremonies": ["Sprint Planning", "Daily Standup", "Sprint Review", "Retrospective"],
"artifact": "Potentially Shippable Product Increment"
}Agile delivers value iteratively in short sprints; Waterfall plans sequentially over long rigid release cycles.