Mattias Skarin
Lean and Kanban Coach
Sun Tzu once said the ultimate responsibility of generalship is maneuver into a position of success. How do we do this in software? After 9 years as a developer I found this was more important than writing the best code, and decided to learn what it takes to do just that. During this journey I’ve helped helped several software teams deliver with confidece, scaled Scrum over 10+ teams (cutting game cycle time from 24 months to 4), and improved life at operations using Kanban.
I’m a co-author of ”Kanban & Scrum, making the best of both” and regularly train and coach in Lean, Kanban and TDD.
Track abstract - Room K2 - Software Development Teams
10 pitfalls when implementing Kanban
”How hard can it be” - visualize flow (cool) - and we’re done (right)? Four weeks later you got a visual board which people slowly starts to ignore and your kanban experiment slides into entrophy death. Good news - it doesn’t need to be that way. Bad news – it’s you who makes the difference.
Let me share my top 10 pitfalls implementing kanban, based on experience from software, operations and support.
