Kanban method in four steps
After you introduce the WIP limits you can try to propagate them back through the workflow, observe results and adapt. Getting limits right takes time, so start with your best guess and fine-tune over time. The ultimate goal is to achieveconstant, high throughput and personal / team performance.
Project karma with Kanban
When things go wrong, especially at work, change is preferred over learning from mistakes. By not reviewing what went wrong, you run risk of simply making a bigger hash of it. A good analogy is when you attempt the nightmare that is flat-pack furniture. Instructions for these finger-busting items are rarely wholly descriptive or helpful. So [...]
Kanban applied to Scrum (video)
Rather than thinking in terms of using Scrum with Kanban, it is better to use Kanban as sole approach. However, if you have a company culture that is still getting used to Scrum or another Agile approach, consider implementing Kanban to compliment, rather than replace.
The illusion of the Scrum “safety net” with Kanban
It can take decades for methodologies to fully gain momentum and be understood. Agile was no different, as it’s taken 10 years for people to realise Agile had been misunderstood dramatically. Read that again – “to realise Agile had been misunderstood …”. That means we haven’t even reached point we have addressed the problems fully. [...]
