Panel Discussion: Quality Engineering - an Evolution of Software Quality as a Team Responsibility
summary
Defines quality engineering as team-owned delivery, argues for built-in quality and joint responsibility, gives a 16‑week bootcamp and static analysis with PHPStan as concrete teaching/tools, cites boundary‑value testing and floating‑point 0.1+0.2 quirks as testable specifics, references ISO 25010 for quality characteristics and adding sustainability, reports DevOps makes teams personally on‑call so quality matters, and recommends workflow change to delete the QA column so tasks shift between design development and testing.
AI-written summary · about
chapters (12)
- 0:00Panel introduction
- 3:02Defining quality engineering
- 4:06Software quality as team responsibility
- 7:39Building in vs fixing later
- 12:17Overcoming resistance to quality
- 17:44Training non-QA in quality skills
- 24:04Balancing code and process quality
- 30:52Centralized vs distributed quality
- 34:50Expanding quality characteristics
- 38:00Eliminating silos between development and QA
- 41:31Team responsibility for quality
- 45:26Closing remarks
related talks
46mQuality Engineering for DevOps Teams
35mWhy Software Engineers Should Make Quality a Priority
18mThe evolution of Quality Engineering
46mProject Culture and Team Responsibility for Quality
24mQuality Engineering: A Journey from traditional testing to ‘Shift-Left’ Mindset
42mOPENING KEYNOTE: Quality Engineering in DevOps
31mQuality Engineering mindset and TBS
37mDavy Kenis: QA No More: Revolutionizing Software testing