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

SpecFlow: Great concept, flawed execution.

SpecFlow: Great concept, flawed execution. SpecFlow, a BDD framework designed to make writing scenarios a breeze for requirement analysts. The problem: It falls short of its promise. ❌ The reality? Analysts rarely, if ever, write the specs themselves. Instead,...

read more

What if…? Production has a Staging slot.

What if...? Production has a Staging slot. Staging or QA environment needs to be the same or as close to production as it can be. Preferably, you want to restore a recent backup 💾 from Production as Staging and then deploy your changes 🔄. Kudos 👏 if you've fully...

read more

UUID v7 coming in .NET 9

UUID v7 coming in .NET 9 For those that didn't know, you can create Guids in different ways (algorithms). System.Guid supports UUID v4 out-of-the-box, the most used version. UUID v7 is now added, which creates Guids based on the current time. This means Guids can be...

read more