You are completely right, WIP is one of the core principle in a Kanban system.
The title of this post is misleading. It should be read as process map diagram exemple since it was a part of a value stream mapping effort.
Actually it was done prior to the kanban system flow design. Determining WIP limit came later as well as what should be part of the board. I will post soon an exemple of a deployed kanban system.
.png)
The WIP aspect is critical: limiting the amount of requests, tickets not resolved, features not tested.
ReplyDeletePlease find one example below
http://www.tiernok.com/LTDBlog/KanbanPt4_VisBoard_4c.png
You are completely right, WIP is one of the core principle in a Kanban system.
DeleteThe title of this post is misleading. It should be read as process map diagram exemple since it was a part of a value stream mapping effort.
Actually it was done prior to the kanban system flow design. Determining WIP limit came later as well as what should be part of the board. I will post soon an exemple of a deployed kanban system.
Thanks for the feedback.