What It Is
A project management and software development approach emphasizing flexibility, collaboration, continuous improvement, and rapid delivery. Based on the Agile Manifesto (2001) but became mainstream in 2010s.
The Agile Manifesto Values
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Core Principles
- Deliver working software frequently (weeks, not months)
- Welcome changing requirements, even late in development
- Business and developers work together daily
- Build projects around motivated individuals
- Face-to-face conversation is most effective
- Working software is primary measure of progress
- Sustainable pace (no perpetual crunch time)
- Continuous attention to technical excellence
- Simplicity—maximize work not done
- Self-organizing teams
- Regular reflection and adjustment
Popular Frameworks
Scrum (Most Common):
- Sprints (typically 2 weeks)
- Daily stand-ups (15 min status sync)
- Sprint planning
- Sprint review/demo
- Sprint retrospective
- Roles: Product Owner, Scrum Master, Development Team
Kanban:
- Visual workflow board
- Work-in-progress (WIP) limits
- Continuous flow (no sprints)
- Pull-based system
XP (Extreme Programming):
- Pair programming
- Test-driven development (TDD)
- Continuous integration
- Frequent releases
Agile Transformation Challenges
Many organizations struggled with “Agile in name only”:
- Lip service to principles, same old practices
- Waterfall disguised as Agile (“Wagile”)
- Cargo cult Agile (rituals without understanding)
- Management resistance to self-organizing teams
- Forcing Agile on non-software teams awkwardly
“We’re doing Agile” often meant: We have stand-ups and use JIRA.
The Scaled Agile Debate
Frameworks for Agile at enterprise scale:
- SAFe (Scaled Agile Framework) - popular but controversial
- LeSS (Large-Scale Scrum)
- Spotify Model
- Disciplined Agile
Critics argued scaling frameworks contradicted Agile’s adaptive spirit.
When Agile Works Best
- Uncertain requirements
- Rapid market changes
- Close customer collaboration possible
- Team co-location (or good remote setup)
- Complex, innovative projects
- Empowered teams
When Traditional Works Better
- Fixed scope, budget, timeline
- Regulatory/compliance heavy
- Distributed teams with poor communication
- Simple, well-understood projects
- Sequential dependencies