Why Agile Testing
The business case for agile testing: faster feedback, higher quality, less stabilization cost, and testing that's embedded instead of a gate at the end.
The business case for agile testing: faster feedback, higher quality, less stabilization cost, and testing that's embedded instead of a gate at the end.
How flow thinking reduces testing bottlenecks and stabilization costs, and why the same constraint-thinking matters as AI shifts the bottleneck downstream.
An article (in Hebrew) on the tester journey from waterfall land to Agile/Kanban — how quality thinking shifts when you stop treating testing as a phase.
Kanban classes of service solve the coordination problem between generalist and specialist roles, and manage shared dependencies without new bottlenecks.
Dev:Test ratio is a proxy for team balance, not a target. How Kanban helps you find the right balance by making bottlenecks visible instead of guessing.