Hans Borjesson: The Unique Holistic Perspective of the Software Tester
summary
Argues that testers hold a unique holistic view because they often run and feel the complete product across stakeholders, citing work on air‑traffic and MedTech systems handling patient data; shows how bad requirements (developers hadn’t read them for years) produced wasted effort in a live product until hiring a requirements owner improved things; prescribes concrete practices: use video calls and cameras, prefer calls over Jira/email for important clarifications, keep a test plan even if rough, treat testing time as a budget and escalate missing specs to managers.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:26Speaker background
- 3:37Holistic perspective in testing
- 5:06Miscommunication challenges
- 7:13Case study requirements frustration
- 9:44Shared language importance
- 11:31Achieving project overview
- 12:35Success factors communication
- 15:51Holistic perspective daily work
- 17:39Project visibility misconceptions
- 18:21Bug hunting versus value testing
- 19:29Questioning routines value
- 20:30Challenging established ways
- 21:58Breaking team silos
- 23:24Culture of asking questions
- 24:37Testers as conversation starters
- 25:18Q&A
related talks
09mSystems Thinking for Testers
53mHow Testers Add Value to the Organization But also, to ourselves
31mQuality Engineering mindset and TBS
37mWe Are The Testers: You Will Be Assimilated
34mHelping Testers Add Value to Agile Projects
15mHow to NOT waste time
42mHow a Tester Can Help Improve the Quality of Requirements
12mBeyond Testers: Embedding Test Expertise in Modern Software Development Teams