Why Agile Testing
The business case for agile testing practices: faster feedback, higher quality, reduced stabilization costs, and the shift from testing-as-gatekeeper to testing-as-embedded-quality.
Agile Testing
Improving Testing Flow / Throughput - A Key Pillar of Managing The Feature Factory
How flow-based approaches reduce testing bottlenecks and stabilization costs — using WIP limits, "done is done" standards, and systematic bottleneck elevation to deliver release-quality software predictably.
Read my article on the journey of a Tester from waterfall land to Agile/Kanban land (in Hebrew...)
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.
Collaborating with specialized roles using kanban classes of service
Kanban classes of service solve the coordination problem between generalist and specialist roles. How to use them to manage shared dependencies without creating bottlenecks.
Finding the right Dev to Test Ratio when working in Kanban
Dev:Test ratio is a proxy for team balance, not a target to optimize. How Kanban helps you find the right balance by making bottlenecks visible instead of guessing at headcount ratios.