To implement Scrumban, it is impossible to completely abandon Scrum and its iterations. It is necessary to master both methods perfectly.
Scrumban is an approach for visualization, and the work constraint involves using a board. Items from the sprint backlog are implemented in a strict sequence, so not all task cards can be in the "In progress" column at the same time. This helps to align the work flow. Team members visually control the process of moving cards along the board and identify opportunities for further process improvement. This is how Kanban works within a sprint.
Scrumban has loan database adopted Scrum's ceremonies and feedback loops for transparency.
What is Scrumban
Source: shutterstock.com
Scrumban is best suited for:
maintenance projects;
works related to any events;
functioning of the help desk or information support;
remote work of teams that launch new projects;
activities preceding the initial stage, research;
testing and deployment of the product,
organizations that have problems using pure Scrum.
If Scrumban is planned to be used, the process is structured as follows:
determine the average size of iterations or sprints that is most appropriate for a particular project;
planning, review and retrospective processes are maintained;
design is carried out on the basis of a slight multitasking, but at the same time the team understands that other issues may “arrive”, so there should always be a reserve;
each task has its own priority, but they themselves are almost the same size;
Before developing a question, it is mandatory to analyze it and work it out by visualizing it on the board in the “Done” column;
each column contains a WIP indicator or a limit on the number of tasks in the process of working on a project;
specific roles are not specified, but are introduced as needed;
The project backlog includes those tasks that someone “ordered”, and a separate column on the board is assigned for them;
daily stand-up is carried out daily, but other ceremonies are held only when necessary;
the backlog does not have a sprint, there is no burndown, and new tasks are put on the board and into work if necessary;
At retrospectives, the team's main goal is to reduce cycle time.
Of course, it is important to understand that this is an average example of project implementation in accordance with the Scrumban methodology. It may deviate towards one method or another depending on the goals and needs of the team.
Read also!