CHAPTER 19 - PM HERO

QA dan Release Management

Bug yang sampai ke production cost mahal. PM perlu skill QA collaboration dan release planning untuk smooth launch.

TIME: 24MLEVEL: intermediate30 CHAPTERS

1. PM Role di QA

PM bukan testing yourself, tapi own quality strategy. Define test plan dengan QA tim. Acceptance criteria clear. Edge case identifikasi. Sign off sebelum release. Quality is product feature, not afterthought.

2. Test Strategy

Unit test (developer). Integration test (system). End-to-end test (full flow). User acceptance test (UAT, by user atau PM). Setiap level catch different bugs. Discuss strategy dengan QA tim di awal sprint.

3. Release Types

Big Bang: launch ke 100 persen user sekaligus. Risky tapi simple. Phased Rollout: 1 persen, 10 persen, 50 persen, 100 persen. Safer, allow detect issue. Beta: limited user dulu test. A/B test launch: split test fitur baru. Pilih sesuai risk profile.

4. Pre-Launch Checklist

Production deploy ready. Documentation updated. Customer support trained. Marketing materials ready. Legal review done (untuk fitur sensitive). Monitoring dan alerts setup. Rollback plan defined. Communication ke stakeholder send.

5. Post-Launch Monitoring

First 24-48 hours kritikal. Watch metric: error rate, response time, user complaint. Customer support feedback. Social media monitoring. Be ready hotfix atau rollback. Document lesson learned untuk next launch.

YOUR MISSION

  1. Pelajari testing best practices
  2. Buat pre-launch checklist untuk produkmu
  3. Setup feature flag untuk phased rollout
  4. Post-mortem launch terakhir
  5. Setup monitoring dashboard untuk launch

POWER-UP RECAP