Leadership In QA: The Future of Enterprise Software: Requirements, Domain Knowledge, & Beyond
summary
Panelists argue concrete practices: a battery product with a 20-year guarantee forces build of a physical test facility and long‑duration validation, a recent feature split after a problematic 58-point feature shows the team breaks work into phased iterations, a large customer rollout (Australia Super Battery / Powan) requires major architecture changes and creation of dockerized simulators to mimic stations, domain modeling and event storming iterate until models get less wrong, and scalability and adaptability drive refactors and occasional full rewrites.
AI-written summary · about
chapters (10)
- 0:00Leadership in QA
- 1:26Panelist backgrounds
- 5:12Correct requirements
- 16:00Iterative requirements management
- 27:09Customer expectations vs scope
- 29:43Handling scope creep
- 36:46Domain expertise needs
- 43:50Breaking team silos
- 46:23Non-functional requirements
- 51:44Closing remarks
related talks
49mDiscussion Panel: QA in the Last Decade - Past Lessons and Future Visions
01h 01mPanel Discussion: Role of QE in Shaping the Future of Financial Services
49mPanel Discussion: Mission-Critical Priorities in Quality Engineering: The Leader's Playbook
55mQuality Engineering Evolution: What Lies Ahead in
37mDavy Kenis: QA No More: Revolutionizing Software testing
46mQA to QE: Scaling Quality with Ownership, Code, and Culture
45mPanel Discussion | How to deal with bad requirements in testing?
16mTear Down the QA Wall