Overview
Visualizing the QA Workflow
For QA teams, Kanban provides a real-time view of the testing pipeline, highlighting bottlenecks where tickets are piling up in 'Ready for QA'.
Unlike Scrum, Kanban doesn't require a 'Sprint Commitment.' It is ideal for teams handling maintenance, production support, or high-volume automated testing where priorities shift daily.
Best Practices
Dos and Don'ts
Avoid common mistakes that can lead to flaky tests and maintenance nightmares.
What to do
- •Set strict 'Work-In-Progress' (WIP) limits to prevent testers from being overwhelmed.
- •Use 'Pull' signals—only move a ticket to QA when a tester has the capacity to start it.
- •Measure 'Cycle Time' to understand how long it takes for a bug to go from 'Found' to 'Fixed'.
Common Pitfalls
- •Don't ignore the 'Bottleneck'—if tickets are stuck in QA, the whole team should help clear them.
- •Don't forget to visualize 'Blocked' tickets with a clear 'On Hold' status.
The Details
Limiting WIP: The Secret to QA Speed
In a Kanban system, the WIP Limit is the most powerful tool for a QA Manager. If a team of 3 QAs has a WIP limit of 3, they cannot take on a 4th ticket until one is finished. This forces the team to stop starting and start finishing. It reduces context switching—the 'silent killer' of quality—ensuring that each feature receives the full attention and rigor it deserves before moving to production.