PNSQC 2014 - Karen Johnson
summary
Argues that offshoring succeeds only when work is codified into tiny explicit steps and regularly reviewed, not left as mysterious scripts; finds regression status often a meaningless green ball metric until teams do whole‑team regression and document 50 scripts; reports automation work sitting idle for months because nobody onsite inspects demos; flags surprises: junior testers lacking domain context, devices and tooling often outdated, nightly cross‑timezone calls eroding trust, and that on‑site review measurably improves quality.
AI-written summary · about
chapters (16)
- 0:00Getting work done in testing
- 2:58Challenge of codifying work
- 7:07Codifying rarely discussed
- 9:13Scripts versus exploratory testing
- 12:04Power and pitfalls of metrics
- 16:17Test automation disconnect
- 19:29Onsite versus offshore teams
- 23:18Training junior testers
- 26:27Cultural and business gaps
- 30:52Questioning in testing culture
- 32:38Reviewing offshore work
- 34:50Hidden costs of offshore loyalty
- 36:14Equipment disparities in offshoring
- 37:19Building trust globally
- 38:41Language in global collaboration
- 40:07Feedback and closing
related talks
01h 13mPNSQC 2013 - Lee Copeland
01h 19mPNSQC 2013 - Capers Jones
01h 25mPNSQC 2013 - Kathy Iberle
01h 21mPNSQC 2013 - Michael Mah
53mNever-Neverland of pursuing Quality
39mThe Good Testing, The Bad Testing and The Ugly Testing
37mDavy Kenis: QA No More: Revolutionizing Software testing
19mHow can we improve quality on a project?