Scrumban
A hybrid agile approach combining Scrum's structure with Kanban's flow-based principles.
Also known as: Scrum-ban, Scrum + Kanban
Category: Frameworks
Tags: agile, frameworks, project-management, teams, hybrid-methods, workflow
Explanation
Scrumban emerged as a natural evolution for teams seeking the best of both agile worlds: Scrum's structured ceremonies and roles combined with Kanban's continuous flow and visual management. The term was first coined by Corey Ladas in 2008.
Scrumban typically retains from Scrum:
1. Regular retrospectives for continuous improvement
2. Daily standups for team synchronization
3. Optional sprint planning on a just-in-time basis
4. Product Owner role for prioritization
From Kanban, Scrumban adopts:
1. Visual workflow boards with columns representing work stages
2. Work-in-progress (WIP) limits to prevent overload
3. Pull-based system where work is pulled when capacity allows
4. Continuous flow rather than fixed sprint commitments
5. Focus on cycle time and throughput metrics
Scrumban is particularly well-suited for:
- Teams transitioning from Scrum to Kanban or vice versa
- Support and maintenance teams with unpredictable incoming work
- Teams wanting more flexibility than pure Scrum provides
- Projects where work items vary significantly in size
- Environments requiring rapid response to changing priorities
The approach allows teams to start with their current process and evolve incrementally. Teams often begin with Scrum and gradually incorporate Kanban principles as they mature, or start with Kanban and add Scrum ceremonies where beneficial.
Key metrics in Scrumban include lead time (total time from request to delivery), cycle time (time in active work), and throughput (items completed per time period).
Related Concepts
← Back to all concepts