Faster Delivering Teams? Kill the test column!
summary
Claim: the usual "In Test" and Waiting for Test columns create hidden WIP and make testing the bottleneck so teams deliver slower. Evidence: sample board shows development 3 days, In Test 2 days and Waiting for Test 1 day so testing alone equals development time. Method: measure average times per column on Kanban (Jira Trello Miro), break testing into entry/exit criteria (regression testing accessibility testing smoke feature), run small experiments pairing testers and devs to frontload testing, remove or collapse columns when averages drop, then repeat.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:50Wheres this talk
- 4:50Problems with intext columns
- 5:28Developers pick up work
- 6:00Push it into waiting
- 6:40More developers than teams
- 7:08Add more testers
- 8:16Automated testing
- 9:03Eliminate columns
- 10:26The Goal
- 11:40Example
- 12:59Breaking down testing
- 16:38Tweaking your boards
- 17:34Improving your teams
- 18:10Subordinate everything else
- 19:16Relieve the system constraint
- 19:52Dont allow inertia
- 22:07Summary
- 28:14Conclusion
- 29:54Questions
related talks
10mBeyond “try harder”: Effective strategies to tackle bugs
38mA Game of Testing
33mTaming The Chaos: After The Quick Wins
30mTaming the Chaos: Beyond the Quick Wins
30mHow to Visualize Impacts to Your Workflow & Metrics
21mThe Tester in Agile — Who Is That?
51mDependencies: Can your agile teams handle them? and if not.. how
22mOvercoming the obstacles of Exploratory Testing at scale