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.
Scrumban is distinct from the Kanban Method in that it:
Prescribes an underlying software development process framework (Scrum) as its core.
Is organized around teams.
Recognizes the value of time-boxed iterations when appropriate.
Formalizes continuous improvement techniques within specific ceremonies.
WIP Limits
To ensure that the team is working effectively, Scrumban methodology states that a team member should be working on no more than one task at a time.
To make sure this rule is followed Scrumban uses WIP (work in progress) limit, this limit is visualized on top of the Doing section of the board (also could be on each column of that section) and means that only that number of tasks can be in the corresponding column at one time.
WIP limit is usually equal to the number of people in the team, but could be expanded based on the team work specifics.