# Scrumban

{% hint style="success" %}
**Scrumban** is an Agile management methodology describing hybrids of *Scrum* and *Kanban* and was originally designed as a way to transition from Scrum to Kanban. Today, Scrumban is a management framework that emerges when teams employ Scrum as their chosen way of working and use the Kanban method as a lens through which to view, understand and continuously improve how they work.
{% endhint %}

### **Kanban vs. Scrumban**

![](https://3408508746-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lis5JLcnSD2vdYdyQ3U%2F-Litn8dWNFYFaLpCh5MB%2F-LitnMCnZUBieYjRSwUn%2Fkanban-vs-scumban.jpg?alt=media\&token=74391dde-f6f0-4e66-a1d1-7efc8cb72bc7)

### **Scrum vs. Scrumban**

![](https://3408508746-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-Lis5JLcnSD2vdYdyQ3U%2F-Litn8dWNFYFaLpCh5MB%2F-LitnbS4E_DsKjAiAzYT%2Fscrum-vs-scrumban.jpg?alt=media\&token=e0d5cff1-e9e9-41de-937d-35d0e9a3b405)

### **When to consider Scrumban**

* Maintenance projects
* Hardening/packaging phases
* Projects with frequent and unexpected user stories or programming errors
* Sprint teams focused on new product development
* If Scrum is challenged by workflow issues, resources and processes
* To manage improvement communities during/after Scrum roll-out

### **Scrumban Backlog**

* Avoid creating/analyzing too many stories (requirements/defects) – reduce waste
* Assure the necessary level of analysis before starting development
* The backlog should be event-driven with an order point
* Prioritization-on-demand – the ideal work planning process should always provide the team with best thing to work on next, no more and no less
