Leanagileprojects.blogspot.com Website Review

All kanban systems experience some “heart attacks” once in a while.  As a team, you can react in two ways: abandon your kanban system, or act smart. If you manage the situation well, you can learn from this experience and improve your kanban system to propel you all the way to high-performance. Building on my popular “Fika” blog series, I present here the mechanism at play behind these “heart attacks” (the policy debt trap) and give some advice on how to best handle it and stay on the high performing path. I also offer some new view on what “failing” with Kanban means: a fantastic opportunity for improvement. This presentation was recorded during a webinar organized by Digité (of SwiftKanban fame). The actual presentation starts at 09:35 after November in Sweden: Blä! The sky is impossibly low and grey, it’s pitch dark at 4 pm, freezing, and then everyone gets cold. Especially There are also situations when your Kanban gets a man-cold (though it doesn’t need to be November for that): it’s not really dying, but > “Kanban worked well for a while, but then it started to feel > cu*bersome, it did not really fit anymore. So we started to skip > some dailies…” (more details follow on how things start to go > south). Something is obviously wrong, but the good news is: it may not automatically mean that you’re doomed and that your organization is On the contrary, it could be positive, a sign that you are improving, becoming more ma*ure! Wait, what? How can this it be? The cause can be a mismatch between your understanding of your way-of-working and the design of your Kanban system. In other words, you put together a set of policies and rules governing what work you want to visualize, in which way, and how you want to manage it. Using is for you). It could be insights on who to involve, when you have the daily meetings, what is in your DoD, how to manage Joe’s availability with a column, what WIP limits would work better, etc. And here comes the danger: THE MORE YOU WAIT BEFORE REFLECTING THIS