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.

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more