Scrumban

Scrumban is a hybrid agile methodology that combines elements of Scrum and Kanban. It blends Scrum’s emphasis on iteration-based planning and reviews with Kanban’s focus on visualizing work, limiting work in progress (WIP), and flowing work through a system. The approach aims to provide the structure of Scrum while maintaining Kanban’s flexibility and focus on throughput.

Core practices in Scrumban include using a Kanban board to visualize the workflow, setting WIP limits to control capacity, and applying a pull-based system so that new work is started only when capacity becomes available. Teams typically maintain a backlog and use lightweight planning and replenishment rather than full, time-boxed sprints. Planning, review, and retrospective activities may be retained in a reduced or context-dependent form, while day-to-day work is managed through continuous flow and regular backlog refinement.

Origins and purpose: Scrumban was popularized as a practical bridge for teams transitioning from Scrum to Kanban, or for teams that need more flexibility to accommodate changing priorities, maintenance work, or varying demand. It is not a prescriptive framework but a set of practices that can be adopted gradually.

Benefits and challenges: Scrumban can improve predictability, reduce cycle times, and increase responsiveness by emphasizing flow and limiting work in progress. It can require discipline to maintain WIP limits and backlog management, and teams may need coaching to balance planning with continuous delivery.

Metrics and tooling: Common measurements include lead time, cycle time, throughput, and WIP, often visualized with a cumulative flow diagram. Common tools include Kanban boards in Jira, Trello, or similar platforms.