What is Kanban and Scrum?
Scrum is a structured agile framework with fixed-length sprints (typically 2 weeks), defined roles (Product Owner, Scrum Master, Development Team), and ceremonies (daily standup, sprint planning, retro, review). Work is committed for the sprint and not changed mid-sprint. Suits work that can be planned in batches. Kanban is a continuous-flow methodology — work moves through a board (To Do → In Progress → Done) with WIP (work-in-progress) limits per column to prevent bottlenecks. No fixed sprints; new work pulled as capacity opens. Suits work with continuous arrival of priorities. Many teams use ScrumBan (Scrum ceremonies + Kanban flow). Both methodologies emerged from agile/lean and have been widely adopted in software, marketing, and operations.
How Kanban and Scrum actually works
The framework breaks down into the following moving parts. Knowing what each piece is — and what it is not — is what separates a B-grade answer from an A-grade answer in a written assignment.
- Scrum — fixed sprints (2 weeks typical), defined roles, no mid-sprint change
- Kanban — continuous flow, WIP limits, pull-based
- ScrumBan — hybrid
- Match to work pattern (batch vs continuous)
- Both rooted in agile/lean
A worked example: Software dev (Scrum) vs IT support (Kanban)
Software product development teams typically use Scrum — features are planned for two-week sprints, the team commits to deliverables, the sprint ends with a working increment. The structure works because feature development can be planned in batches. IT support teams typically use Kanban — tickets arrive continuously, the team pulls the next ticket as capacity opens, WIP limits prevent agents from being overwhelmed. The structure works because support work cannot be batched into sprints (urgent issues interrupt). Same company, different methodologies for different work types — both correct.
Don't lose marks for these
- Forcing Scrum on continuously-arriving work
- Forcing Kanban on planned-batch work
- Skipping ceremonies in Scrum (becomes "scrumfall")
How to use this on the exam
Score-maximizing moves
- Distinguish both methodologies
- Match to work type
- Cite ScrumBan as hybrid
When to use Kanban and Scrum (and when not to)
Use Kanban and Scrum when your assignment asks you to analyze, structure, or recommend — and when you have at least two data points to populate every cell of the framework. Skip it when the question is asking for a numerical answer or a single recommendation, since Kanban and Scrum is a structuring tool, not a calculator.