Kanban for QA
Kanban for QA applies the Kanban method — visualizing work as cards moving through columns (To Do, In Progress, Testing, Done), limiting work in progress — to testing workflows, emphasizing continuous flow over fixed-length sprints, well suited to teams handling a steady stream of testing requests rather than batched sprint work.
Unlike Scrum's fixed sprint cadence, Kanban has no built-in iteration boundary — work items flow continuously through the board as they're ready, which fits naturally with QA teams that field an unpredictable, ongoing stream of testing requests (support escalations, ad hoc verification requests) alongside planned feature testing.
Work-in-progress limits — capping how many items can sit in the "Testing" column at once — are Kanban's key mechanism for preventing a QA team from being overwhelmed with more in-flight testing work than it can realistically handle at any given moment, surfacing bottlenecks visibly rather than letting a backlog silently balloon.
