ISTQB_TEST MANAGEMENT_ The Context of Testing_1.2.1 Test Stakeholders

 1.2.1 Test Stakeholders

• Testing involves collaboration with various stakeholders, each with distinct roles and interests in the quality of the product.

• Primary stakeholders include:

  • Product Owner / Business Analysts – Provide requirements, business rules, and validate outcomes.

  • Project Managers – Require reporting, control, and risk tracking.

  • Developers – Collaborate on early defect resolution, unit tests.

  • End Users / Customers – Focus on usability, functionality, and reliability.

  • Operations / Support Teams – Ensure maintainability, deployment, and incident management.

  • Regulatory Authorities (if applicable) – Demand compliance with legal/industry standards.

• Stakeholder influence and interest levels may vary; managing communication and expectations is a key responsibility of the Test Manager.

---

✅ Mock Questions: 1.2.1 – Test Stakeholders

Question 1 (K2 - Understand)

Why is it important for a Test Manager to identify test stakeholders early in the project?

• A. To automate unit tests using stakeholder input

• B. To delegate planning to developers

• C. To align testing objectives with stakeholder expectations and quality goals

• D. To ensure stakeholders write test cases
  ✔️ Answer: C

Question 2 (K1 - Remember)

Which stakeholder is MOST concerned with how the product behaves in real-world usage?

• A. Developer

• B. End User

• C. Product Owner

• D. Project Manager
  ✔️ Answer: B

Question 3 (K2 - Understand)

What is the role of a Project Manager in the context of testing?

• A. Writing automated test cases

• B. Executing tests

• C. Monitoring test progress and managing project risks

• D. Approving test data sets
  ✔️ Answer: C

Question 4 (K2 - Understand)

Why might a Test Manager need to manage different levels of stakeholder involvement?

• A. To reduce test execution time

• B. To tailor communication and reporting appropriately

• C. To ensure all stakeholders become testers

• D. To avoid test environment conflicts
  ✔️ Answer: B

Question 5 (K1 - Remember)

Which of the following is typically NOT considered a direct stakeholder in testing?

• A. Business Analyst

• B. Configuration Manager

• C. Software Tester

• D. Technical Writer
  ✔️ Answer: D

Question 6 (K2 - Understand)

Which stakeholder is PRIMARILY responsible for defining business rules and ensuring alignment with user needs?

• A. Developer

• B. Project Manager

• C. Product Owner / Business Analyst

• D. Tester
  ✔️ Answer: C

Question 7 (K3 - Apply)

You are leading a project involving regulatory compliance. Which stakeholder should be involved early to avoid late-phase compliance issues?

• A. Developers

• B. End Users

• C. Regulatory Authorities

• D. Support Team
  ✔️ Answer: C

Question 8 (K1 - Remember)

Who typically ensures the software product can be deployed and maintained in production?

• A. Operations / Support Team

• B. Business Analyst

• C. Tester

• D. Developer
  ✔️ Answer: A

Question 9 (K4 - Analyze)

In a stakeholder matrix, which type of stakeholder has high power but low interest and must be kept satisfied?

• A. Promoter

• B. Defender

• C. Apathetic

• D. Latent
  ✔️ Answer: D

Question 10 (K4 - Analyze)

A stakeholder with high interest and high power is opposing a test delay due to defect retesting. What should you do as a Test Manager?

• A. Escalate directly to senior management

• B. Engage in a discussion, show impact analysis, and negotiate a solution

• C. Ignore the objection and continue as planned

• D. Send the stakeholder weekly defect reports only
  ✔️ Answer: B