Help! We have a QA problem
summary
A testing backlog of 206 days shrinks to 47 days by cutting big packages into smaller pieces, using Excel for quick estimations, a visible PDCA and timeline and by empowering testers to coordinate developers to help. The plan prioritizes customers, timeboxes work and keeps responsibility for quality with testing, clearing the pile in nine weeks, recovering lost customers and driving about 70% revenue growth. Practical tools: chunking, coarse estimates and developer-assisted testing — concrete numbers and a working process, not vague promises.
AI-written summary · about
chapters (4)
- 0:00Start
- 3:27The essential ingredient: the PDCA Cycle (Shewhart Cycle - Deming Cycle - Plan-Do-Study Act Cycle - Kaizen)
- 10:56Objectifying and quantifying the problem is a first step to the solution
- 20:16The Myth of the Man-Month
related talks
40mHelp! We Have a QA Problem!
49mOptimizing QA Flow to Minimize Time to Release While Meeting Quality Standards
21mEstablishing Quality Assurance in Startup environment
24mImproving Development Quality and Speed with Agile Testing
56mNo QA resources? You can still deliver a quality website
36mWhy a Growing Company Needs a Growing QA Team
36mHow programmers & testers can be productive
20mTesting Complex and Time Critical Projects!