Project Culture and Team Responsibility for Quality
summary
Presents evidence from about 20 teams and three case studies showing that whole-team testing reduces bugs and cost: one case where unstable tech returned 500 errors frequently, one where a lean product with shared testing won customers and revenue, and one where deferring quality caused multi‑million remediation. Recommends concrete practices: developers write unit, integration and component tests; tests and acceptance criteria are kept in the repository and run in CI; regular pairing and analyst/designer review of test models promote shared responsibility for quality.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 2:33Product quality responsibility
- 4:17Team quality responsibility
- 5:18Team types and outcomes
- 11:13Traditional testing problems
- 13:48Member impact on quality
- 15:55New analyst roles
- 19:04Developers' testing duties
- 21:55Designer's quality role
- 24:25Product owner in testing
- 27:14Scrum master's quality role
- 31:25Planning and meetings changes
- 33:32Team quality manifesto
- 35:38Hulk and Musketeers issues
- 37:22Quality improvement practices
- 40:15Team responsibility cuts costs
- 43:12Q&A
related talks
42mImproving Testing Quality by Changing Culture
49mDeveloper + tester = quality++
35mTesting != Quality
36mWhole team quality: In the same boat or up the creek?
19mHow can we improve quality on a project?
14mThinking of Quality as developer productivity tool
36mHow programmers & testers can be productive
35mBetter, Faster, Stronger - Delivering High Quality Products