“Quality is a Team Responsibility”
summary
A production outage prompts a hotfix that appears to work but only surfaces after customers call support, revealing that a critical change was unplanned, untracked so testers were unaware and did not cover affected areas. The meeting fixes nothing: feedback on testing critical features late and lack of monitoring and alerting comes too late. The clear claim is that quality requires collective ownership across requirements, meetings, code, automated and exploratory tests, and observability.
AI-written summary · about
related talks
46mProject Culture and Team Responsibility for Quality
35mTesting != Quality
19mHow can we improve quality on a project?
35mWhy Software Engineers Should Make Quality a Priority
49mIs your Quality on the Road to Nowhere?
38mWhen Nobody Owns Quality: Making Testing Responsibility Explicit in Open Source Projects
12mSoftware Quality Is Not Just Code and Tests
31mQuality Engineering mindset and TBS