01 / 04
What Agile, Scrum and Kanban are, and why a team picks one over another.
Agile is an approach that suggests developing software in small, working pieces at short intervals rather than in one large delivery.1 After every delivery the plan is updated according to the feedback. Agile is not a tool or a list of rules but a way of thinking about work. In practice, teams mostly put that thinking into effect with Scrum or Kanban.
Scrum is a working framework that splits the work into fixed stretches of time called sprints. The team holds three accountabilities: the Product Owner, who decides what gets done and in what order, the Scrum Master, who helps the team apply Scrum properly, and the Developers, who build the work.2 What will be done in a sprint is settled at its start, and the team stays focused on that work until the sprint ends.
A sprint is a fixed stretch of time in which the team plans and builds by forecasting how much work it can finish. It usually lasts 1 to 4 weeks and can be no longer than a month.23 In this lesson the examples run on a 2-week sprint. The aim is to deliver, by the end of that time, a working and concrete piece of the product the user can experience directly. If the goal is a user profile page, for example, the page's code and tests are finished before the sprint ends and the page is made ready to use.
Kanban is a working method in which the work flows continuously across a board rather than being split into fixed stretches of time. The board has columns that show the stages of the work, for example To Do, In Progress and Done.4 When one piece of work is finished, the next one is pulled from the To Do column. The number of items in progress at once is capped (a WIP limit, a limit on work in progress), so half-finished work does not pile up.4
Scrum is usually preferred on teams that are building a new product or feature and want to deliver at regular intervals. Kanban suits teams dealing with work whose arrival cannot be known in advance, such as production bugs and support requests, better, because new work can be taken on without waiting for a sprint to end.5 Many teams use both together: they work in sprints but also cap the number of items in progress on the board.4
Sources
Delivering working software frequently, from a couple of weeks to a couple of months, and welcoming changing requirements.
The three accountabilities and the sprint lasting no longer than a month. Ken Schwaber and Jeff Sutherland, 2020.
That sprints are time-boxed and usually last 1 to 4 weeks.
Making the flow visible with a Kanban board, limiting WIP explicitly, and Kanban not removing the sprint.
Kanban suiting teams with many incoming requests whose priority and size change, and hybrids such as Scrumban.
Your progress is stored only in this browser.
Last updated: November 3, 2026