Helping Testers Add Value to Agile Projects
summary
Argues testers survive and add value by changing what they do not by pleading for process: learn the dev stack and TDD, shrink heavyweight artifacts and remove waste, make testing visible by put test notes in the story/work repo, peer with developers and automate boring reports, use exploratory testing where scripts fail, run small experiments and measure their effect, and apply cybernetic thinking — only variety can absorb variety — so testers create and own pragmatic strategies that fit each agile team.
AI-written summary · about
chapters (5)
- 0:00Start
- 10:28We survive when we learn to adapt to the System Of Development
- 14:23I remember a time before I worked on an Agile Project
- 29:47I try to foster an attitude of...
- 33:03Helping Testers Survive, and Add Value to Agile Projects
related talks
01h 05mAdding value in an agile context
53mHow Testers Add Value to the Organization But also, to ourselves
33mAgile Software Testing
08mTesting In Agile
01h 02mAgile Testers and Test Managers: Now What?
43mHow I fell in love with Agile testing and why you should, too!
26mTraditional tester lost in the Agile world
09m“Leading a Testing Revolution”