7 / 62 · 22 Test Strategy & Quality Metrics · Building a Test Strategy← prev⊞ allnext →☰ Read as one page
1.7Getting Stakeholder Buy-In
A test strategy is worthless if nobody follows it. Getting buy-in requires making the strategy relevant to each stakeholder's concerns.
| Stakeholder | Their Concern | How to Get Buy-In |
|---|---|---|
| VP of Engineering | Release velocity, team productivity | "This strategy reduces our regression cycle from 3 days to 4 hours" |
| Product Manager | Feature delivery speed, customer satisfaction | "Risk-based prioritization means we test the checkout flow exhaustively but spend less time on admin pages" |
| Development Lead | Developer productivity, code quality | "Developers own unit tests, QA owns E2E -- clear ownership, no duplication" |
| CTO | Technical debt, platform reliability | "This strategy includes quarterly security and performance assessments" |
| CFO | Cost | "Automation investment of $X pays for itself in Y releases through reduced manual testing" |
The Buy-In Process
- Draft the strategy based on your risk assessment and product analysis
- Socialize it individually -- meet with each stakeholder 1:1 and incorporate their feedback
- Present the final version to the full team, showing how their input shaped it
- Get explicit approval from the engineering leader who owns the quality budget
- Review quarterly and report on whether the strategy is working using the metrics defined in Section 8