⚡ Agile / Scrum / Kanban
Agile is the philosophy. Scrum and Kanban are specific implementations. Scrum uses time-boxed sprints (usually 2 weeks) with defined roles (Product Owner, Scrum Master, Dev Team) and ceremonies (standups, retrospectives, planning). Kanban uses continuous flow with WIP (Work In Progress) limits and visual boards. Neither is universally better — the choice depends on your team, product, and context.
Methodology Comparison
Scrum
Fixed sprints, defined roles, predictable velocity, best for product development
Kanban
Continuous flow, WIP limits, flexible priorities, best for ops/support
Scrumban
Hybrid approach combining sprint cadence with Kanban flow and WIP limits
Real-World Example
Spotify famously evolved beyond pure Scrum into their "Squad" model — small cross-functional teams (Squads) grouped into Tribes, with Chapters and Guilds for knowledge sharing. This shows that mature organizations adapt methodologies rather than following them rigidly.