Menu
ESC

Nhập từ khóa để tìm kiếm

↑↓ Di chuyển
Enter Mở
ESC Đóng

Đang tải...

Bài 38 — Quality Coaching & Champions Program

Test Strategy and QA Leadership Bài 38/60

Quality Coach Model

Vấn đề

QA team không scale với eng team. 1 QA: 10 dev common, but quality phải distribute.

Quality Coach role

QA senior who coach dev to test better. Not test executor anymore.

Activities

  • Pair with dev on test design.
  • Run lunch & learn (testing techniques).
  • Review test code, give feedback.
  • Author internal "testing handbook".
  • Office hours: dev can ask testing questions.

Quality Champion (dev side)

1-2 dev per team volunteer as testing advocate.
  • Attend QA monthly meetup.
  • Spread best practice in team.
  • Report quality concerns to QA Lead.

Org structure example

QA Lead
  ├── Quality Coach (3-5)
  │     ├── coach embedded with squad
  │     └── shared backlog quality initiatives
  └── SDET Platform team (5-10)
        └── build framework, infra

Engineering squads ├── 8 dev + 1 Quality Champion ├── 6 dev + 1 Quality Champion └── ...

Coach skills

  • Strong technical depth.
  • Influence without authority.
  • Patience teaching.
  • Documenter (write playbooks).

Anti-pattern

  • Coach become helpdesk → no proactive work.
  • Coach skip pairing → just review PR.
  • No champions → coach burn out.

VN context

Tiki, Shopee VN có quality coach mature. FPT structure traditional QA, mixed.

Metrics

  • Tests written by dev (trend).
  • Test coverage per service.
  • Champion activity (meetup attendance).
  • Coach NPS from dev.

Outcome

  • Test ownership shift to dev.
  • QA team scale sublinearly with eng team.
  • Higher quality overall.