Menu
ESC

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

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

Đang tải...

Bài 51 — Building Quality Culture

Test Strategy and QA Leadership Bài 51/60

Quality Culture

Khái niệm

Mindset trong tổ chức: quality is everyone's responsibility, not just QA.

5 dấu hiệu mature quality culture

  • Dev write own test, không "throw over wall".
  • Bug reported quickly, no shame.
  • Post-mortem blameless.
  • Quality metrics visible to all.
  • Release-quality tradeoff discussed openly.

Anti-cultures

Hero culture

  • "Senior X always saves us."
  • Issue: not scalable, X burn out, knowledge silo.

Blame culture

  • "Whose fault is this?"
  • Issue: hide bug, slow learning.

Cargo cult automation

  • "We need 100% automation!"
  • Issue: low-value test, miss exploratory.

Speed worship

  • "Ship fast, fix later."
  • Issue: tech debt, customer pain.

Build quality culture — leaders' role

  • Public sponsor: CEO talks about quality.
  • Resource: QA team appropriately staffed/funded.
  • Visibility: quality metrics in all-hands.
  • Reward: promotion for quality contribution.

Build quality culture — QA's role

  • Be partner, not police.
  • Education > enforcement.
  • Be data-driven.
  • Celebrate quality wins.
  • Make easy to do right thing (tooling, doc).

Tactical practices

  • Quarterly "Quality OKR" for each team.
  • Bug bash inclusive event.
  • Internal QA blog / newsletter.
  • Demo "found bug" in retro.

VN context

  • Outsourcing culture (FPT): contract-driven quality, formal.
  • Startup culture: speed-driven, quality afterthought initially.
  • Mature local product (Tiki, Shopee VN): blend.

Measuring culture

  • QA engagement survey.
  • Dev "would you test more?" survey.
  • Production incident root cause: process? tech? people?