Making Software Testing Innovation Work
summary
Provides six success factors that narrow where innovation actually fails: organizational root causes more than tools, leadership incompetence that caps team performance, and culture or HQ commander control that produces requirements defects. Gives concrete failures — outsource testing to carpenters and plumbers, weekly API churn that balloons automation maintenance — and argues readiness (CMMI jump) and skills beat plug‑in tools, recommends plan‑do‑check‑act and realistic, customized rollouts rather than copy‑paste practices.
AI-written summary · about
chapters (18)
- 0:00Intro
- 3:45Software architecture
- 5:17A true story
- 5:47Fear
- 6:27Smart corporations
- 7:03Hiring testers
- 8:29Freedom
- 9:42Top 4 reasons
- 11:10Culture changes
- 11:24How difficult is it to change a company culture
- 11:56What make people to change
- 12:42Readiness
- 14:04Agile Transformation
- 15:32Standard vs Custom
- 16:06Implement everything by the book
- 16:40Skills over processes
- 17:40Summary
- 19:19Challenges
related talks
16mChallenges of Testing at Scale | Experiments and Experiences
24mThe more we test, the worse?
01h 04mBuilding on Success, Beyond the Obvious
54mTest Automation Transformation Avoiding the 7 Common Pitfalls
42mUse testing to Develop Better Software Faster
14m3 Automation Testing Mistakes & How to Correct Them?
49mThe Secret to Successful Testing
09m“Leading a Testing Revolution”
