Agile

Core Principles and Methodologies

• Scrum: Uses time-boxed sprints (2–4 weeks), daily standups, and roles like Scrum Master/Product Owner[1][3].
• Kanban: Focuses on visualizing workflows and limiting work in progress[1][6].
• Extreme Programming (XP): Prioritizes technical excellence through practices like test-driven development[3].

1. Concept: Identifying business opportunities and feasibility[1][2].
2. Inception: Forming teams, defining requirements, and setting timelines[1].
3. Iteration: Building software in cycles (2–4 weeks) with stakeholder feedback[1][2].
4. Release: Final testing and deployment[1].
5. Production: Ongoing support and user training[1].
6. Retirement: Phasing out outdated systems[1].

Rise to Prominence

• 58% faster delivery of business results compared to Waterfall[5].
• 40% reduction in defects at Cisco[4].
• Improved team morale and transparency[4][6].

Notable Adopters

Controversies and Criticisms

1. Misapplication: Superficial adoption (“pseudo-Agile”) without cultural buy-in leads to failed implementations [6] [9].
2. Scaling Challenges: Large organizations struggle with coordination; frameworks like SAFe introduce complexity [6] [9].
3. Overemphasis on Speed: Rapid iterations risk technical debt and unstable products [6] [9].
4. Cultural Resistance: Transitioning from hierarchical structures to self-organizing teams often meets internal pushback [5] [6].
5. Documentation Gaps: Minimal documentation complicates onboarding and long-term maintenance [6] [9].

Evidence and Research

• Pros: Agile projects report 14–58% faster delivery, 40% fewer defects, and higher customer satisfaction in dynamic environments[4][8][11].
• Cons: Traditional methods outperform Agile in regulated industries with fixed scopes[8]. Hybrid models (Agile + Waterfall) are increasingly popular for balancing flexibility and structure[8][11].
• ROI debates persist: Some studies show Agile’s benefit-to-cost ratio lags behind Waterfall, though it achieves business goals more consistently[5].