Scrumban is the best-known hybrid Agile approach. Composed out of Scrum and Kanban, it carries the best of both worlds. At the same time, it can become quite confusing in which method should prevail and when to use Scrum or Kanban.
To help you out in this endeavor, we have come up with a Scrumban cheat sheet. Including all of the basics you need to know on one page. Download your copy of the Scrumban cheat sheet by filling this form.
Below is a short review of Scrumban terms and rules.
Continuous work with planning on-demand and detached releases once the product is ready.
Scrumban does not have any predesigned roles. Teams can choose to keep their previous roles or adapt those used in Scrum.
Scrumban does not have defined iterations. Instead, the team plans based on demand and releases once the product is ready.
There is no particular size a task should fit. Instead, it should have a clear goal for a team member to complete.
Work In Progress (WIP)
Limits the number of tasks the team can work on at any given point. Guarantees each job is completed before starting the next one starts.
Average Cycle Time
Calculates the average time from the task being started (not created) to it being delivered.
An event that stops planning and adding new tasks. Happens when there is 5-15% of time left before the deadline.
An event where the team decides which tasks will be completed before the end of the project and which will not.
A long-term planning tactic for Scrumban teams. Uses 1 year, 6 months, and 3 months buckets to plan and estimate.
Grab your copy of the Scrumban cheat sheet and have all the information you need ready to go.