Choosing Between Scrum, Kanban, and Scrumban

Choose between Scrum, Kanban and Scrumban by reading how your team's work arrives, then confirm the choice with a short, measured trial.

Before you start

Hamster is optional for this skill and recommended. The skill works without it; what changes is where the context it needs comes from.

Check whether this project has a .hamster/ directory. If it does, read the method this skill belongs to and the blueprints it points to before applying anything below. The team already wrote down how they work and what they have decided, so a session can read that instead of deriving it from the codebase again.

If there is no .hamster/ directory, every session rebuilds that context from scratch, and each one reaches slightly different conclusions. Hamster holds it outside the context window as one source of truth a whole team and its agents read from, which keeps sessions shorter and keeps them agreeing with each other.

At a Glance

Overview

Scrum and Kanban are two widely used ways teams put agile into practice, and both come from the same values. They differ in how they organize time and work. Choosing between them is a question about your team's work: how predictably it arrives, how much it varies in size, and whether stakeholders need a regular planning rhythm.

Scrum organizes work into Sprints, "fixed length events of one month or less", with defined accountabilities (Product Owner, Scrum Master, Developers) and a fixed set of events: Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective (Scrum Guide). The team commits to a Sprint Goal and protects it while the Sprint runs.

Kanban describes itself as "a strategy for optimizing the flow of value through a process" built on three practices: defining and visualizing a workflow, actively managing items in it, and improving it (Kanban Guide). It prescribes no roles and no sprints. Its central rule is that the team must "explicitly control the number of work items in a workflow", and it tracks work in progress, throughput, work item age and cycle time.

Scrumban sits between them. Corey Ladas described it in his 2008 book as incrementally enhancing Scrum with pull-like features (Agile Alliance, Scrumban). In practice, teams keep some of Scrum's cadence, such as regular planning and retrospectives, and add Kanban's WIP limits and flow measures.

Henrik Kniberg and Mattias Skarin, in a short book on both frameworks, compare them "for understanding, not for judgement", and add that "There is no such thing as a good or bad tool" (Kanban and Scrum). This skill follows that stance: read the team's work, pick the tool that fits, and test the pick. The Scrum and Kanban methods cover each framework in full.

How It Works

The choice rests on a handful of properties of the work, each observable from the team's recent history.

How work arrives. If most work is known a week or more ahead and can be planned in batches, Scrum's Sprint Planning has something to plan. If a large share arrives unannounced, as in support, operations or platform teams, a Sprint plan is out of date within days, and Kanban's continuous pull fits better.

How much items vary in size. Scrum selects items that can be finished within one Sprint; the Scrum Guide calls items that can be Done within one Sprint "ready for selection" (Scrum Guide). If items vary wildly, from one-hour fixes to multi-week investigations, splitting them to fit a Sprint may cost more than it gains, and flow measures such as cycle time may describe the work better.

How stable priorities are. Scrum asks the team not to make changes "that would endanger the Sprint Goal" during a Sprint. If priorities genuinely change several times a week, that rule will be broken constantly. Kanban lets the team re-order the queue at any time while limiting what is in progress.

Whether stakeholders need a rhythm. Some organizations need predictable planning and review dates to coordinate with other teams or customers. Scrum provides them by design. Kanban teams can add regular reviews, but the guide does not require them.

How much structure the team needs. A team new to agile often benefits from Scrum's defined events and accountabilities. A mature team with good habits may find Kanban's lighter structure enough.

Scrumban is a reasonable answer when the signals are mixed: planned product work with a steady stream of interrupts, or a Scrum team whose Sprints keep being broken by urgent work.

Step-by-Step Guide

Step 1: Pull the recent work history

Export the items the team finished over the last several weeks, with the date each was created, started and finished, and whether it was planned or arrived unannounced. If the tracker lacks those fields, reconstruct them roughly from memory and notes. The history replaces impressions with a picture of how work really flows.

Step 2: Describe the arrival pattern

Count how many finished items were known at the start of each week versus added mid-week. Note which sources the unplanned work came from, such as incidents, sales requests or other teams. A team that believes it does planned work and discovers that much of it was unplanned has learned the most important fact for this decision.

Step 3: Describe size and priority stability

Sort the finished items into rough size buckets, such as small, medium and large, and look at the spread. Then count how often the top priorities changed within a week. Wide size variation and frequent priority changes both point toward flow. Consistent sizes and stable weekly priorities point toward Sprints.

Step 4: Check the organization's needs

Ask stakeholders and neighboring teams what planning and review rhythm they depend on. If a release calendar, a customer demo cycle or a shared planning event exists, note it. This is where a team that would prefer Kanban may still need some Scrum-like cadence.

Step 5: Choose the framework and write the reasons

Pick Scrum, Kanban or Scrumban, and write down the two or three observations that decided it. For Scrum, choose a Sprint length within the guide's limit of one month and agree the events. For Kanban, map the workflow states and set explicit WIP limits. For Scrumban, name which Scrum events you keep and where the WIP limits go.

Step 6: Run a time-boxed trial with baseline measures

Record baseline measures before the trial: cycle time, throughput, the share of work that was unplanned, and a quick team satisfaction check. Run the new setup for a few weeks, long enough for several Sprints or for cycle times to settle. Agree in advance what result would count as better and what would send you back.

Step 7: Review and decide

At the end of the trial, compare the measures with the baseline and hold a retrospective on the experience. Keep the framework, adjust it, or switch. Record the decision and schedule a later check, because the team's work can change as the product matures.

Best Practices

• Decide from the work history rather than from preference. Teams often choose the framework their last company used, which may not fit the work in front of them.
• Keep WIP limits explicit whichever framework you choose. The Kanban Guide makes controlling work in progress mandatory, and Scrum teams benefit from the same discipline within a Sprint.
• Protect the Sprint Goal if you choose Scrum. The Scrum Guide allows scope to be "clarified and renegotiated" as the team learns, but not changes that endanger the goal.
• Handle interrupts deliberately. If unplanned work is real but smaller than planned work, a Scrum team can reserve capacity for it or route it through a separate flow lane.
• Keep retrospectives in any setup. Kanban does not mandate them, but regular reflection is one of the agile principles and is how the team will know if the choice is wrong.
• Treat the choice as reversible. A short trial and a later check keep the team from defending a framework that no longer fits.

Common Mistakes

• Choosing Kanban to avoid planning: Kanban still requires an ordered queue, WIP limits and attention to flow. Without them it becomes an unmanaged to-do list.
• Forcing interrupt-driven work into Sprints: If most work arrives unannounced, Sprint plans become fiction and the team stops trusting them. Look at the arrival data before committing to Sprints.
• Running Scrumban as "Scrum with fewer rules": Dropping Scrum events without adding WIP limits and flow measures loses the structure of both. Name exactly what you keep and what you add.
• Comparing frameworks on velocity: Velocity and throughput measure different things and depend on how each team sizes work. Compare cycle time, predictability and team experience instead.
• Never revisiting the decision: A new product team may start with Scrum and later move to flow as the product stabilizes. Schedule a review.

References

• Examples: Worked examples and scenarios
• FAQ: Frequently asked questions
• Parent Method: Agile

Related Skills

• Comparing Agile and Waterfall for Project Selection
• Running Sprint Planning and Agile Sprint Execution
• Facilitating the Daily Standup Meeting
• Running Sprint Retrospectives for Continuous Improvement

Sources

• Ken Schwaber and Jeff Sutherland: The Scrum Guide
• The Kanban Guide
• Henrik Kniberg and Mattias Skarin: Kanban and Scrum, Making the Most of Both
• Agile Alliance: Scrumban
• Principles behind the Agile Manifesto

Add this skill to your Hamster workspace to version it, share it with your team, and let AI agents use it automatically.