Marcus Hammarberg wrote:when we have 3 items left in the Todo-column we call the product owner (or customer or whatever) and say that we need more work.
In that way we pull new work to us just-in-time rather than plan up a lot of work onto a waiting list, just-in-case. We become more agile and can change easier.
Junilu Lacar wrote:My 2 cents: Kanban works well when your team has a level of maturity where they can chunk work out into reasonably same-sized pieces or if they have established a relatively smooth flow of work such that WIP can be reasonably used as a predictor of the team's output. With new projects where a flow has not been established and there are still many unknowns both from the users' perspective as well as the developers' perspective, the work completed in the past may not be a very good predictor of the work that can be completed in the upcoming weeks.
Marcus Hammarberg wrote:Think about this: how do your coworkers know that you have loads to do? That you're on a roll? That you need help? What you have accomplished the last week?