LinkedIn·Saturday, 22 August 2026·4d ago
A common scenario that often triggers moving cards backward on your Kanban board is handling defects during the ‘Testing’ phase. If you…
Nave
1,197 followers
A common scenario that often triggers moving cards backward on your Kanban board is handling defects during the ‘Testing’ phase. If you discover an issue with the implementation, instead of moving the work item back and forth, block it in the ‘Testing’ state and create a new defect card in the ‘Development’ (Queue) state.
That way, the new card will count towards your WIP limit, and the focus will move to sort out all quality issues before initiating new work. This approach will enable you to evaluate the number of defects that you are handling in the long run and better understand how failure demand impacts your customer demand overall.
To learn more about the 4-step process to effective defect management, download our guide to more sustainable delivery of quality software → https://getnave.co/4iFNTV0
#NavigateYourFlow #Kanban #Quality #Agile #ContinuousImprovement #DefectManagement #SoftwareDevelopment
Cross-referenced
Related on the wire
The approach of analyzing your data using the Cycle Time Breakdown is extremely powerful if you maintain a Kanban pull system. Kanban pull…
As teams scale and projects grow, the Kanban board can become cluttered and hard to read. Exactly why Kanban swimlanes are used to tame…
If the work comes into your workflow faster than it leaves it, this is a clear indication that your system is unstable. From a…
Project managers are constantly balancing short-term responsiveness and long-term strategic planning. Striving for maximum agility by…
The Throughput Breakdown Chart is a great tool to use when it comes to emphasizing the high volume of unplanned work that your team has to…
Painting the inside of a truck white is not a transformation initiative. Nobody puts that in a plan. Nobody approves a budget for it. But…