Improving Development Quality and Speed with Agile Testing
summary
Software projects fail 68% of the time and low performers spend 31% of time on rework so upgrade testing with concrete practices: use BI and customer support logs to shape test data and device coverage, map complex flows with mind maps, run the training-journey A/B test only on non-subscribers to split risk and still get statistically significant results, run paired exploratory sessions using personas like the training junkie, and set a measurable quality goal to raise release confidence while reducing defects and rework.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker introduction
- 1:59Fuel miscalculation and planning fallacy
- 3:49Project failure rates and agile testing goals
- 4:33Defining quality assurance roles
- 6:19Quality analyst role and data sources
- 9:08Customer engagement and bug insights
- 11:16Clarifying user stories and value
- 12:43Example of user story validation with mind map
- 15:12Quality assurer role and testing goals
- 16:15Exploratory testing and team approach
- 17:39Personas and real-world bug examples
- 18:24Quality ambassador and team goals
- 19:49Post-mortems and blameless culture
- 20:55Key techniques to improve quality and speed
- 21:35Conclusion and final thoughts
- 22:04Q&A: Convincing developers to care about quality
related talks
36mYou Can't Be Agile If Your Testing Practices Suck
45mSpeeding Up Delivery and Raising Quality with Agile Testing
39mMyths & Challenges of Agile Testing
33mAgile Software Testing
42mImproving Testing Quality by Changing Culture
43mAgile Testing Practices for Better Software Quality
35mBetter, Faster, Stronger - Delivering High Quality Products
43mHow I fell in love with Agile testing and why you should, too!