# Scrumban Scrumban is a hybrid methodology combining elements of [[Scrum]] and [[Kanban Methodology]], originally conceived by [[Corey Ladas]] around 2008. It emerged as a transition method for teams moving from Scrum to Kanban, but has since become a methodology in its own right. Scrumban takes Scrum's structure (sprints, planning, retrospectives) and adds Kanban's flow-based practices (WIP limits, pull system, continuous flow). This combination offers flexibility for teams that need more structure than pure Kanban but find strict Scrum too rigid. ## Key Characteristics - **WIP Limits**: Borrowed from Kanban to prevent overloading - **Pull System**: Work is pulled when capacity allows, not pushed - **On-Demand Planning**: Planning happens when needed (triggered by WIP), not on fixed schedules - **Optional Sprints**: Iterations can be used or abandoned based on team needs - **Continuous Improvement**: Regular retrospectives combined with flow metrics ## When to Use Scrumban Scrumban works well for: - Teams transitioning from Scrum to Kanban (or vice versa) - Maintenance and support teams with unpredictable work - Projects requiring both iteration structure and flow flexibility - Teams finding pure Scrum too prescriptive ## Scrumban vs Scrum vs Kanban | Aspect | Scrum | Kanban | Scrumban | |--------|-------|--------|----------| | Iterations | Fixed sprints | Continuous flow | Optional sprints | | Roles | Defined roles | No prescribed roles | Flexible roles | | Planning | Sprint planning | Just-in-time | On-demand | | WIP Limits | Per sprint | Per column | Per column | | Changes | After sprint | Anytime | Anytime | ## References - https://www.agilealliance.org/scrumban/ - Corey Ladas: "Scrumban: Essays on Kanban Systems for Lean Software Development" ## Related - [[Scrum]] - [[Kanban Methodology]] - [[Kanban Boards]] - [[Agile Manifesto]] - [[Limit Work In Progress]] - [[Corey Ladas]]