How a Tester Can Survive in an Agile Environment
summary
Covers the role of QA in classical development models versus whether they truly provided quality assurance, and examines Agile values from the Agile Manifesto as they apply to QA teams. Compares traditional and Agile approaches regarding risks, value delivery, transparency and team workload, and discusses test documentation in Agile — whether to keep test plans, how to handle test cases and checklists, and practical alternatives.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 3:10Testing problems
- 7:27Quality approach evolution
- 10:58Agile Manifesto impact
- 14:10Transparency and incremental dev
- 18:03Technical debt consequences
- 20:48Tester role in quality
- 23:58Documentation myths
- 26:44Living documentation
- 28:49Agile testing tips
related talks
09mQA in an Agile environment
26mTraditional tester lost in the Agile world
43mAgile Testing Practices for Better Software Quality
51mQuality Assurance vs. Testing
45mIs there a place for QA in modern agile autonomous fast-flow teams?
06mDoes QA have a place in DevOps? Heck yeah!
41mDevOps! Let's Change QA!
49mDeveloper + tester = quality++