Kanban for DevOps

If your infrastructure team is struggling with Scrum, you should try Kanban.

The Kanban way of working fits the more reactive nature of DevOps/SRE/Infrastructure teams more than Scrum:

Flexibility in Prioritization: Kanban allows for continuous reprioritization of tasks. You can quickly adapt without disrupting the flow of work, making it ideal for reactive teams where priorities shift frequently.

Focus on Continuous Delivery: Small, incremental changes and continuous delivery are encouraged, aligning well with the DevOps philosophy of rapid, reliable, and frequent deliveries.

Limiting Work in Progress (WIP): By limiting WIP, Kanban helps your team not overcommit to work.

Give Kanban a shot if you haven’t. I’ve successfully convinced my last two teams to switch from Scrum to Kanban.


Like what you've read?

If you're an engineering leader or developer, you should subscribe to my 80/20 DevOps Newsletter. Give me 1 minute of your day, and I'll teach you essential DevOps skills. I cover topics like Kubernetes, AWS, Infrastructure as Code, and more.

Not sure yet? Check out the archive.

Unsubscribe at any time.