Agile

Meetup #4: Kanban Vs. Scrumban – Differences, challenges, solutions.

Agile Beirut had the honor hosting, with the sponsorship of Antwork and Agile Alliance, it’s fourth meetup titled “Kanban Vs. Scrumban – Differences, challenges,solutions.” on December 11 at Antwork premises, Spears, Kantari, Beirut, Lebanon.

Our event featured a special guest, Walaa el Kerdy from CardioDiagnostics showcasing the benefits of applying Scrum on the dev teams and the outcome from the business and team perspective.

THE SLIDES

The presentation
Walaa Presentation

Kanban

Kanban is focused on continuous delivery of completed work or part of work. One of the most recognizable features of Kanban is WIP limits, which is used to reduce the amount of tasks that can be worked on at one time. As the work is continuous, the board stays persistent, only the tasks change. Workflow happens through a pull principle, where tasks are assigned after they went to the backlog or backlog priorities sections. New items can be added to the backlog whenever WIP limits allow it. Just like in Scrum, team members are working individually and may swarm a task if there is a need for it, however Kanban doesn’t need daily meeting. There are no roles for team members, but they can choose specialization. Kanban uses cumulative flow diagrams, lead and cycle times to measure performance and the planning is done after each release/iteration or by planning on demand principle. Kanban doesn’t impose strict constraints, process is more flexible. Therefore it fits best for support, maintenance teams or continuous product manufacturing.

Our guest speaker Walaa el Kerdy

Scrumban

Scrumban uses mixed techniques of both methodologies. It combines basic features of Scrum and flexibility of Kanban. Scrumban has a slightly constrained process where prioritization is optional, but it is recommended during each planning and planning is done by Kaizen events. Scrumban uses planning on demand principle to fill the backlog and tasks are assigned only by the pull system like in Kanban. Also, just like in Kanban, the board stays persistent, while only the tasks and their priorities change. In Scrumban the work is usually focused more on planning than releasing, while in Scrum planning is done after each sprint, Scrumbans planning is done only on demand. This method is mostly used for fast-paced process like startups or projects which require continuous product manufacturing, where the environment is dynamic.

Most Popular

To Top