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

Scrum conceals bad teams.

Scrum conceals bad teams. Far too often, we confuse Scrum with a magic wand that transforms any team into a high-performing 'dream team'. It's tempting to believe that the sprint system, with its regular completion and initiation of tasks, gives us an agile and...

read more

🚀 Process Automations in Microsoft Loop!

🚀 Process Automations in Microsoft Loop! Now you can create Power Automate-backed rules to streamline repetitive tasks in your Loop table. See https://insider.microsoft365.com/en-us/blog/streamline-your-workflow-with-automation-in-microsoft-loop Loop is slowly...

read more

You don’t control the truth in Production!

You don't control the truth in Production! Now a days multiple teams/projects are working on the same Dataverse production environment. So thinking you can manage the complete production truth in your ALM pipeline is strange. Not every environment is 💯 equal to...

read more
Share This