Scrum vs. Kanban
Both are ways of running Agile teams, and 'Agile' on a resume could mean either. Scrum works in fixed sprints (usually two weeks) with planning, stand-ups, reviews and a Scrum Master. Kanban has no sprints: work flows continuously across a board, with a limit on how much is in progress at once. Kanban is common in support, operations and platform teams; Scrum in product teams.
How to tell them apart on a resume
Scrum
Sprints, sprint planning, story points, velocity, retrospectives, Scrum Master, CSM or PSM certification — product delivery teams.
Kanban
WIP limits, cycle time, lead time, continuous flow, service desk or ops teams, ticket queues — work that arrives unpredictably.
The question that settles it
“Did your team plan work in fixed sprints, or pull tickets continuously from a board — and why did that suit the kind of work you did?”
Read the full definitions
Open the full tool for the other look-alike pairs, role profiles, and the JD decoder.