From Scrum to Kanban

by Dec 1, 2022

I use Kanban instead of Scrum. Much simpler.

By removing two main things from Scrum we have Kanban:

❌ Sprints
❌ Tasks

When you have Continuous Delivery working then you can release anytime. With Continuous Deployment you are releasing every change. You don’t need the arbitrair schedule that Sprints give you.

Tasks are used to split up Backlog Items and to show progress. This progress is often shown on a board with columns Todo, In Progress and Done.

Often, I can’t split my Backlog Items into smaller tasks. Or they became tasks that represent a phase in the process, like Analyse, Implement, Test, Deploy.

Instead of tasks, use columns to show the progress. Put the Backlog Item in the right column to represent its status.

Do you need multiple steps for a Backlog Item? Add a Todo-list to the Backlog Item and flag the steps you already have done.

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

What makes SPAs feel modern?

What makes SPAs feel modern? Because Single-Page Applications feel fast. This is largely due to targeted partial page rendering: the strength of SPAs. HTMX allows you to build the same modern-feeling apps, just simpler, faster and cheaper. It allows you to do a...

read more

I almost never Debug my code.

I almost never Debug my code. Somehow this is strange in the eyes of fellow developers. They can't image coding without a debugger. For example, I have never felt the need to attach a debugger to a deployed Dynamics 365 Plugin. Never! Ok, one time. I wanted to know...

read more
Share This