Many agile teams use planning poker to estimate the relative size of items in their product backlog. Yet the usual planning poker with the (rounded) Fibonacci numbers can be applied the wrong way. Or better, in a suboptimal way. Fruit Estimation Poker to the rescue!
At first sight, Kanban looks deceptively simple. You visualise your workflow, put some work-in-progress limit to every stage, and that’s it!
This is indeed the basics for any succesful Kanban. But why are these two principles the driving force behind Kanban? And how can we teach people these basics in a way that they understand the principles, not only know them by heart?