This is a common dilemma for teams wanting to use Kanban for ‘fixed price, fixed cost” projects. On the one hand, you have a business demand to commit up-front to a timeline and scope (and cost) to deliver a product;
David J Anderson’s book on Kanban shows us that a way to handle ticket issues is by attaching a color tag to a ticket to make it visible. An issue is a ticket-related event that becomes an impediment to its
This question comes up not only in Personal Kanban but also for teams and enterprise (portfolio) kanban boards as well. It is a great question – and quite often tricky to answer!
What should be the level of work breakdown