While starting with Kanban may appear simple enough – after all, what can be simpler than ‘start with what you have’?! – modeling your first Kanban board does require some thinking and planning as it depends on a number of factors. Learn how do you design your first Kanban board.
We often hear the question – In Kanban, what should we do if a User Story in Test column is found to have a bug that needs to be fixed? Let’s say the workflow is something like this: Todo -> Development -> Test -> Release. If a User Story has completed Development and moved to Test, and a tester finds a bug, what should we do to that User Story? Is it right to leave that User Story in Test and the developer should stop their current development work to fix this Defect first? If so, does this mean that developers must be interrupted all the time to clear the bugs found in Test?
Recently, there was an interesting problem posed on a project management discussion board. The questioner asked –
“I have recently joined a company and to one of the projects that I’m engaged we have this Scrum team that has a mixed backlog (USs and Bugs).
In a recent post on a technical forum, a Dev manager had the question (paraphrased here) – My organization wants to operate in a Kanban way but maintain the structure of sprints and burn down charts to keep track of progress. Is it ok to do? Is Scrumban the correct methodology? If so, what is the best way to implement it?
In 2015, in a blog post called Kanban Cadences, David Anderson laid out a set of 7 Kanban cadences or meetings that provide comprehensive opportunities for feedback, planning, and review in an enterprise. Some of these were already identified in his original blue book, Kanban: Successful Evolutionary Change for Your Technology Business, some were identified later and put together in this post.
Try SwiftKanban Enterprise Plan FREE for 30 days.