David Anderson shares Goals for using Kanban
David Anderson on the goals behind the Kanban method: not just flow optimization, but evolutionary change in how the organization delivers.
David Anderson on the goals behind the Kanban method: not just flow optimization, but evolutionary change in how the organization delivers.
Making agile concepts tangible with food-based metaphors — edible versions of frameworks that help non-technical stakeholders get iterative thinking.
Measuring QA effort effectiveness through bug metrics — which ratios matter, what data to track in your tracker, and how to spot systemic quality problems.
Severity vs. priority in bug tracking — why these two axes matter, why teams conflate them, and how keeping them separate improves triage and flow.
How to get developers into the QA lab without friction — protocols for bug reproduction, developer-tester collaboration, and building quality into the flow.
Opening high-quality bug reports is a skill — protocols for writing bugs that developers can act on without back-and-forth and that keep the flow moving.