I attended the online meeting last Wed, and now I'm reviewing it, here is a question, When you move from the push to pull strategy, you will have very long lists in the "done" intermediate sections as you have in the initial TO DO column. How can you do to avoid very long lists in the Done columns?
I think that the problem with long lists that you describe doesn't relate directly to the push or pull workflow management approach. It may be an indicator of a bottleneck in crossfunctionality/seniority levels/team composition (like 3 senior developers bombarding one junior QA with done items). If done items pile up, they are likely to pile up in "done" intermediate sections as well as in subsequent "to do" intermediate sections.
One of the tenets of shifting towards Kanban is focusing on the flow of work. Adding "done" columns enables bottlenecks to be visualized. By 'fixing' a bottleneck early in the flow of work by improving flow, another bottleneck may be illuminated downstream in the workflow. Optimizing all of these for faster flow should improve output.
Great video. Keep up the good work. 👍
I attended the online meeting last Wed, and now I'm reviewing it, here is a question, When you move from the push to pull strategy, you will have very long lists in the "done" intermediate sections as you have in the initial TO DO column. How can you do to avoid very long lists in the Done columns?
I think that the problem with long lists that you describe doesn't relate directly to the push or pull workflow management approach. It may be an indicator of a bottleneck in crossfunctionality/seniority levels/team composition (like 3 senior developers bombarding one junior QA with done items).
If done items pile up, they are likely to pile up in "done" intermediate sections as well as in subsequent "to do" intermediate sections.
One of the tenets of shifting towards Kanban is focusing on the flow of work. Adding "done" columns enables bottlenecks to be visualized. By 'fixing' a bottleneck early in the flow of work by improving flow, another bottleneck may be illuminated downstream in the workflow. Optimizing all of these for faster flow should improve output.
Updated: Does Scrumban really allow for faster delivery, or it is just more frequent delivery of smaller items?
It's faster because you focus on what's most valuable and use WIP limits to reduce multitasking.
$/' Why directly remove it .... make it shorter or longer .... hm velocity variations. ...? 1-4 Weeks the shorter is better if there is a trigger ....