Career & Craft
Scrum
A specific Agile framework structuring work into fixed-length sprints with defined roles (Product Owner, Scrum Master, team) and ceremonies — planning, daily stand-up, review and retrospective. It gives delivery a predictable cadence. Done poorly it becomes meeting overhead and status theatre, so the retrospective — actually improving — is the part that matters most.
Purpose
Scrum is the most widely adopted Agile framework: fixed-length sprints (usually two weeks), three roles (Product Owner prioritising the backlog, Scrum Master tending the process, the team building), and a fixed set of ceremonies — planning, daily stand-up, sprint review, retrospective. It gives iterative delivery a predictable, inspectable rhythm.
When to Use It
Teams that benefit from cadence and explicit prioritisation, and organisations that need a shared vocabulary for planning across many teams. It suits product work where a backlog can be ordered by value and delivered in slices.
Trade-offs
Its ceremonies are load-bearing or dead weight depending on execution: stand-ups become status recitals, sprints become mini-waterfalls, velocity becomes a weapon. Kanban's continuous flow often fits interrupt-heavy or operations work better than sprint boundaries do.
Implementation
Keep the backlog genuinely ordered by value; enter sprints with a clear goal, not a grab-bag; keep stand-ups to coordination (blockers, not narration). Guard the retrospective most fiercely — a team that actually acts on retro items improves every other ceremony; one that skips it fossilises. Adapt the framework to the team, never the reverse.