Software Testing Communication & Stakeholder Relations 2 — Questions and Answers
Question 1: A product owner keeps changing requirements mid-sprint. What is the BEST approach for the QA lead to handle this?
- Ignore the changes and test original requirements
- Document all changes and assess their impact on existing test cases before proceeding (Correct answer)
- Immediately update all test cases to reflect the latest version
- Escalate to senior management to stop the product owner from changing requirements
Correct answer: Document all changes and assess their impact on existing test cases before proceeding
Documenting changes and assessing impact ensures informed decision-making before modifying test artifacts.
Question 2: Which communication style is MOST effective when delivering a defect report to a non-technical business stakeholder?
- Use technical jargon to appear credible
- Focus on business impact, risk, and user experience rather than technical details (Correct answer)
- Provide raw log files and stack traces for completeness
- Avoid mentioning severity to prevent alarming them
Correct answer: Focus on business impact, risk, and user experience rather than technical details
Non-technical stakeholders respond best to information framed in terms of business risk and user impact.
Question 3: A developer disputes a bug report, claiming the behavior is 'by design.' What should the tester do FIRST?
- Close the defect immediately
- Re-check the requirement specification and provide evidence linking the defect to documented expectations (Correct answer)
- Escalate to the project manager right away
- Accept the developer's judgment without further action
Correct answer: Re-check the requirement specification and provide evidence linking the defect to documented expectations
Referencing the specification provides objective evidence to resolve the dispute professionally.
Question 4: What is the PRIMARY purpose of a test summary report shared with stakeholders at project end?
- To assign blame for unresolved defects
- To provide an objective overview of testing activities, coverage, results, and outstanding risks (Correct answer)
- To list all tools used during testing
- To request additional testing budget for the next phase
Correct answer: To provide an objective overview of testing activities, coverage, results, and outstanding risks
The test summary report gives stakeholders a transparent view of quality status and remaining risks.
Question 5: During a sprint review, a stakeholder says 'I thought this feature was already tested.' How should the QA engineer respond?
- Apologize and promise to test it immediately
- Explain what was tested, what was not, and why, referencing the agreed test scope (Correct answer)
- Deflect responsibility to the development team
- Promise additional testing rounds without consulting the team
Correct answer: Explain what was tested, what was not, and why, referencing the agreed test scope
Transparent communication about scope boundaries helps stakeholders understand what testing was actually contracted.
Question 6: A client requests daily verbal status updates instead of written reports. What risk does this introduce for the QA team?
- Faster communication cycles that reduce defect resolution time
- Lack of documented record making it difficult to track commitments or resolve disputes later (Correct answer)
- Reduced stakeholder engagement due to information overload
- Improved agility since fewer documents need to be maintained
Correct answer: Lack of documented record making it difficult to track commitments or resolve disputes later
Verbal-only updates create an audit gap and leave no traceable record of decisions or commitments.
Question 7: Which metric is MOST useful to communicate testing progress to a project manager who is primarily concerned with schedule?
- Number of test cases written per tester
- Percentage of planned test cases executed versus the schedule baseline (Correct answer)
- Total number of defects found
- Average defect severity rating
Correct answer: Percentage of planned test cases executed versus the schedule baseline
Execution progress against the schedule baseline directly answers a project manager's scheduling concern.
Software Testing Communication & Stakeholder Relations 2
A product owner keeps changing requirements mid-sprint.
What is the BEST approach for the QA lead to handle this?