Kanban
Kanban is a visual workflow management method that uses a board with columns representing process stages to track work items as they flow from start to completion. Teams set work-in-progress (WIP) limits for each column to control flow and identify bottlenecks. Unlike sprint-based methods, Kanban emphasizes continuous delivery and pulls new work only when capacity becomes available.
Kanban operates on three core principles: visualizing workflow, limiting work-in-progress, and managing flow. Teams create boards with columns representing their actual process stages, such as Backlog, Analysis, Development, Code Review, QA Testing, UAT, and Production Ready. Each work item, represented by a card, moves left to right through these stages. WIP limits prevent teams from taking on too much simultaneous work, forcing them to complete existing items before starting new ones. This constraint surfaces bottlenecks immediately and encourages collaborative problem-solving.
For website QA teams, Kanban provides critical visibility into testing capacity and delivery predictability. When managing multiple website releases, feature updates, and urgent fixes simultaneously, Kanban boards show exactly where work accumulates and which team members are overloaded. This visibility becomes essential in regulated industries where compliance testing cannot be rushed or skipped. QA managers can use flow metrics like cycle time and throughput to demonstrate team capacity to stakeholders and negotiate realistic delivery commitments. The continuous flow model also aligns well with modern web development practices like continuous integration and frequent deployments.
Common mistakes include setting WIP limits too high, which negates the bottleneck-revealing benefits, or too low, which creates artificial constraints. Teams often create too many columns, making the board complex rather than clarifying workflow. Another pitfall is treating Kanban as merely a visual tool without implementing the discipline of WIP limits and flow measurement. Some teams also fail to distinguish between different work types on their boards, mixing urgent production fixes with planned feature testing, which obscures true capacity allocation.
Kanban integrates naturally with website quality management by making testing dependencies visible across development, design, and content teams. When QA testing becomes a bottleneck, the visual board immediately shows upstream teams they should help resolve testing issues rather than create more work. This collaborative approach improves overall website quality because problems get addressed systematically rather than through crisis management. The continuous flow model also supports better user experience delivery, as teams can respond to user feedback and production issues without disrupting artificial sprint boundaries or waiting for arbitrary release windows.
Why It Matters for QA Teams
Kanban makes the QA testing queue visible to the entire team. WIP limits prevent developers from flooding the testing column with more work than QA can handle, promoting sustainable quality.
Example
An e-commerce QA team at a major retailer manages their holiday season website updates using a Kanban board with columns for Backlog, Development Ready, In Development, Code Review, QA Testing, UAT, and Live. They set WIP limits: 3 items in Development, 2 in Code Review, 4 in QA Testing, and 2 in UAT. During peak season preparation, payment gateway updates pile up in QA Testing while the Development column sits nearly empty. The visual bottleneck immediately signals that developers should pause new work and help with testing activities like test data setup and environment configuration. The team realizes their payment testing requires specialized PCI compliance knowledge that only two team members possess, so they cross-train others and adjust their WIP limits accordingly. This prevents a potential compliance violation and ensures payment functionality launches on schedule for Black Friday traffic.