How can we improve quality on a project?
summary
A panel argues that quality improves by moving testing earlier — shift left — splitting work into unit, API and front-end checks run by developers, while reserving human investigation for unknown behaviour; automation is reframed as automated checking that confirms expected results and misses exploratory edge cases. They cite a consumer recall (Bose sleep pods) and claim roughly 50% environmental/configuration failures on some projects. They recommend three‑amigos analysis up front and adopting risk-based documentation so effort matches potential cost.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:50Quality comes from requirements
- 5:00Impact of development on testing
- 6:00Do we risk losing rigor
- 7:50The Three Amigos
- 11:45RiskBased Documentation
- 13:40What is an automated test
- 15:50Automation vs manual testing
related talks
35mWhy Software Engineers Should Make Quality a Priority
42mImproving Testing Quality by Changing Culture
56mControlling Quality in Software Development
46mProject Culture and Team Responsibility for Quality
28mInstilling the built-in quality mindset into a dev team
35mTesting != Quality
21mEstablishing Quality Assurance in Startup environment
40mReal Quality Assurance from an Agile and Lean Viewpoint