QA Communication

Stakeholders QA work with

• Engineering — daily.
• PM — sprint planning, scope.
• Design — review mockup quality.
• Support / CS — bug feedback from users.
• Sales — feature commitment.
• Exec — release readiness.

Communication artifacts

• Daily standup — 1 phút status.
• Release sign-off — go/no-go decision document.
• Bug report — clear, actionable.
• Test plan — what we'll test for release X.
• Test summary report — what we tested, what we found.
• Quarterly metrics review — trend dashboard.

Saying NO professionally

• Explain risk: "Going live now: 3 critical bugs open, escape risk 30%".
• Offer alternative: "Defer 1 week or ship with feature flag off".
• Quantify: "If we ship Black Friday, p95 likely 5s vs SLA 2s".

Influence without authority

• Data > opinion.
• Specific user story > abstract.
• Show test result demo, not slide.
• Propose solution, not just problem.

Common pitfalls

• Yes-man → bug ship, blame later.
• Pessimist → block everything, lose credibility.
• Hide bug count → exec surprised.
• Use jargon → exec disengage.

Reporting upward

• Risk traffic light (Red/Yellow/Green).
• Key escalation 3 bullets.
• Trend chart prefer single number.
• "What I need from you" explicit.

VN context

Cultural — VN team reluctant push back exec / client. QA Lead must build trust + frame as service.