From the course: Agile Software Development: Kanban for Developers
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Avoiding bad kanban - Trello Tutorial
From the course: Agile Software Development: Kanban for Developers
Avoiding bad kanban
- [Instructor] Before we wrap up the course, there are two common pitfalls to be aware of with limiting work in progress and managing flow. And that's thrashing, and what I like to call, repeating the grade. Thrashing describes a situation where feedback loops are too short which won't allow the team enough time to incorporate any new information or process improvements. Repeating the grade is what I call situations where work items routinely go through the board multiple times. So let's look at a practical example of thrashing. Let's put our Build column's work in progress max to one and let's also change our Code Reviews max to one. Now, this is great because there really won't ever be a bottleneck in Code Review anymore. There only will be allowed one in there at a time. However, this also means that there's no flow. So let's say we move an item into Code Review. Oh, great, there's nothing in Build and we're only allowed one in our Code Review. So that's fine. But then let's say it…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.