Agile Software Development Methodologies Explained
What Agile Actually Says
The Agile Manifesto (2001) prefers individuals and interactions, working software, customer collaboration, and responding to change. Everything else — Scrum, Kanban, ceremonies — is a specific implementation, not the thing itself.
The Methodologies
Scrum
Time-boxed sprints (typically two weeks) with planning, daily stand-ups, review, and retrospective. Good for product teams with steady stakeholders. Fragile when interrupts dominate.
Kanban
Continuous flow with WIP limits. Less ceremony, more visualisation. Excellent for support, ops, and any team where work arrives unpredictably.
Extreme Programming (XP)
Pair programming, TDD, continuous integration, refactoring. Strong technical practices. Often blended into other methodologies rather than adopted whole.
Lean Software Development
Eliminate waste, amplify learning, defer decisions, deliver fast. Owes a lot to Toyota Production System. Strong on systems thinking and metrics.
Scaled Agile (SAFe, LeSS, Spotify Model)
Patterns for coordinating many teams. Useful in 200+ engineer organisations. Often over-applied — most companies don't need them.
Which Fits When
- Small product team, predictable cadence → Scrum
- Support, ops, or interrupt-heavy work → Kanban
- High-quality codebase, strong engineering culture → blend XP practices into anything
- Manufacturing-style optimisation → Lean
- Hundreds of engineers, multiple coordinated trains → SAFe (with caution)
Common Failure Modes
- Cargo-cult Scrum. Ceremonies without empowerment is theatre.
- Velocity worship. Velocity is a planning aid, not a performance metric.
- Estimation as commitment. Story points become deadlines, gaming begins.
- No retrospectives that change anything. A retro that produces no actions is wasted time.
What Actually Matters
- Short feedback loops — from idea to user
- Visible work — anyone can see what's in progress and why
- Empowered teams — decisions happen close to the work
- Measurable outcomes — ship-and-measure, don't ship-and-hope
The Bottom Line
Pick the lightest methodology that gives you visibility, feedback, and learning. Layer on practices when they earn their keep.
*We help teams adopt agile practices that fit their reality, not the consultant slide deck. Talk to us →*