Reading path4 stops9 stepsAbout 26 minutes of reading
Bringing in a testing partnerwhat to read before the first call.
Four stops for engineering and quality leaders: what poor quality costs and when outside help pays, how we assess and improve a test function, programs we have run, and the questions to ask before you sign.
Stop 1
The problemIs testing really where we are losing?
The cost of poor quality, and when to bring in outside help.
- 01ArticleThe Case for Investing in Testing: A Board-Level Argument for Enterprise Test-Function CapabilityThe board-level case for investing in testing capability.Read →
- 02ArticleDeciding When to Bring in External Help: A Framework for Training, Consulting, Staff Augmentation, and Outsourced TestingWhen to choose training, consulting, staff augmentation, or outsourced testing.Read →
Stop 2
How we workHow would they improve our testing?
How we assess a test function, find the gaps, and close them with your team.
- 03ArticleCritical Testing Processes: A Non-Prescriptive Framework for Test Process ImprovementThe framework we use to assess a test function and decide what to improve first.Read →
- 04Template · 12 minThe 137-row skills matrix for managing a test function's capability.The skills matrix we use to see where each tester needs coaching.Read →
- 05Checklist · 6 minPrioritize risk before you prioritize tests.How we decide what to test first, based on business risk.Read →
Stop 3
ProofHave they run programs like ours?
Test programs we designed and ran.
- 06Case studyQuality at ScaleA AAA game studio that cut defects by more than half.Read →
- 07Case studyMission-Critical QATesting to Department of Defense compliance standards.Read →
- 08Case studyIndependent Test Organization for a Device + Service ProductA four-phase quality program for a consumer device, with the master test plan behind it.Read →
Stop 4
Before you signWhat should I ask any partner?
The questions to put to any testing partner.
Next
Seen enough?A senior principal takes the first call.
Keep reading
Related reading
- Primer
Careers in Software Quality: Roles, Skills, and First Steps
What testers, test automation engineers, quality engineers, and test managers actually do, the skills each role uses, and practical first steps for students and career changers, including the ISTQB Foundation certification.
Read → - Primer
Errors, Defects, and Failures: What a Bug Really Is
Everyone says 'bug', but testers use three precise words: error, defect, and failure. Learn the difference, why it matters, and how severity and priority decide which problems get fixed first.
Read → - Primer
How Software Gets Attacked: Common Vulnerabilities in Plain English
The most common ways attackers break into software, explained without jargon: trusting input, broken access control, weak sign-in, misconfiguration, and outdated components. Each one comes with the defense that stops it.
Read → - Primer
How to Report a Bug So It Actually Gets Fixed
Finding a bug is half the job. Learn how to write a bug report a developer can act on: a clear summary, exact steps to reproduce, expected versus actual results, and the habits professional testers use to make every report count.
Read → - Primer
Security Testing Basics: Finding Weaknesses Before Attackers Do
An introduction to security testing for new testers and developers: thinking in threats, designing abuse cases, testing access control, the role of automated scanners and penetration tests, and the rules that keep security testing legal and ethical.
Read → - Primer
Staying Safe Online: Passwords, Sign-In, Phishing, and Updates
The everyday security habits that stop most attacks: strong unique passwords, multi-factor sign-in, spotting phishing, keeping devices updated, and sharing carefully. Written for students, families, and anyone starting out.
Read →
Practices
Where this leads
- QA & testingSoftware testing
Software quality consulting since 1994: we test the releases that matter, coach your team on the method, and measure how its testing matures.
Book a call →