Kanplan

What is Kanplan?

Kanplan is a Jira board option from Atlassian that pairs a continuous-flow Kanban board with a separate ordered backlog, so upcoming work can be refined and prioritized before the team pulls it onto the board.

Updated November 2026 · 3 min read


Kanplan is a hybrid way of working that combines a Kanban board with a groomed backlog. Work flows continuously across the board without sprints, as in Kanban, but upcoming work is kept in a separate, ordered backlog where the team can refine, estimate and prioritize it before it reaches the board, as in Scrum. The term comes from Atlassian, which introduced Kanplan as a board option in Jira Software.

Kanplan addresses a practical problem with pure Kanban boards. When every idea sits in the first column of the board, that column grows into a long, unmanageable list, and it becomes hard to tell which items are ready to start. Kanplan moves that list into a backlog view, leaving the board for work the team is actually ready to pull.

How Kanplan works

  • Backlog. A prioritized list of items that are not yet on the board. The product owner or team lead keeps it ordered and refined.
  • Board. Columns such as Selected, In Progress, Review and Done. Work moves across the board as capacity frees up.
  • Pull, not push. When someone finishes an item, they pull the next top item from the backlog or the Selected column.
  • WIP limits. Each in-progress column has a maximum number of items to keep work flowing and expose bottlenecks.
  • No sprints. There is no fixed iteration or sprint commitment. Releases and reviews happen on a cadence the team chooses.

Kanplan vs. Kanban vs. Scrum vs. Scrumban

KanbanKanplanScrumbanScrum
Fixed iterationsNoNoOptionalYes
Separate backlog viewUsually notYesOftenYes
WIP limitsYesYesYesNot required
Planning triggerContinuousContinuous, from the backlogWhen the ready queue runs lowStart of each sprint

Kanplan is essentially a tool configuration for a common practice; Scrumban is a broader method with its own planning rules. Other work-tracking tools, such as Azure Boards, also pair a backlog view with a Kanban board, even if they do not use the name.

When Kanplan fits

  • Teams with a steady flow of varied work, such as platform, support or maintenance teams, that still need to plan upcoming items.
  • Scrum teams that find sprint commitments artificial but want to keep backlog refinement and estimation.
  • Kanban teams whose "To Do" column has grown too long to manage.

A hypothetical example

Consider a hypothetical internal tools team of four engineers whose Kanban board has 140 cards in its To Do column. Nobody can see what is next, and engineers spend time picking through old requests. The team switches to Kanplan: it moves all 140 items to a backlog, closes 55 that are obsolete or duplicates, and leaves 85 ranked items. It adds a Selected column limited to 6 items and an In Progress limit of 5, a little more than one item per engineer to allow for review waits. Each week, the lead and a stakeholder spend 30 minutes refining the top of the backlog and refilling Selected. Within a month, the team can tell a requester roughly where their item sits and when it is likely to start.

Common pitfalls

  • Backlog as a graveyard. Moving items off the board does not make them less stale. Prune the backlog regularly.
  • Skipping WIP limits. Without them, Kanplan becomes a to-do list with a backlog attached.
  • No refinement rhythm. Without sprints to force it, refinement can slip. Schedule it.
  • Losing forecasting. Without sprints there is no velocity, so track throughput and cycle time instead.

Kanplan builds on Kanban and its use of WIP limits, while borrowing the product backlog from Scrum. Teams deciding between approaches often start with Kanban vs. Scrum.

Frequently asked questions

How is Kanplan different from Scrumban?

Kanplan is essentially a Jira board configuration for a common practice: a Kanban board plus a separate, ordered backlog, with no fixed iterations. Scrumban is a broader method with its own planning rules, such as planning when the ready queue runs low, and it can optionally use iterations. Both use WIP limits.

When should a team use Kanplan?

Kanplan suits teams with a steady flow of varied work, such as platform, support or maintenance teams, that still need to plan upcoming items. It also fits Scrum teams that find sprint commitments artificial but want to keep refinement and estimation, and Kanban teams whose To Do column has grown too long to manage.

Does Kanplan use sprints?

No. In Kanplan, work flows continuously across the board without a sprint commitment, and team members pull the next top item from the backlog or Selected column as they finish work. WIP limits keep flow steady. Releases and reviews still happen, but on a cadence the team chooses rather than at the end of each sprint.