Section 7 Solutions

These are the answers to the Section 7 Review's Knowledge Check. If you haven't attempted the three scenarios yet, do that first.

Scenario 1: The Excluded QA Team

Correct answer: Reframe testing findings in terms of what product actually cares about (user experience, business impact) and seek earlier involvement at the requirements stage, per Working with Product and Developers.

Explanation: This is the module's own opening scenario restated — an adversarial framing and late-only involvement erodes trust and leads to exactly this kind of exclusion.

Alternative approaches considered: Escalating the exclusion as unfair, without addressing the underlying relationship pattern, doesn't fix the actual cause — the fix is changing how and when QA engages, not asserting a right to be included.

Real-world reasoning: Tests whether "interest-based framing and early involvement rebuild trust" was understood as the fix, not just "insist on being included."

Scenario 2: The Unowned Pipeline

Correct answer: Proactive, joint diagnosis treating the pipeline as genuinely shared territory, per Working with DevOps and Stakeholder Management — not waiting for either side to claim sole ownership.

Explanation: This is that module's own opening scenario restated — shared infrastructure needs explicit cross-functional ownership, since assuming it's someone else's job leaves it unresolved indefinitely.

Alternative approaches considered: Escalating to management to assign clear single ownership might resolve ambiguity but misses the actual insight — the problem often needs both groups' complementary expertise working together, not exclusive ownership by one side.

Real-world reasoning: Tests whether "genuinely shared ownership, not exclusive assignment" was understood as the model, not just "someone needs to own this."

Scenario 3: The Over-Explained Answer

Correct answer: Lead with the direct answer first, then supporting reasoning, per Executive Communication — "Yes, with one caveat..." rather than a detailed explanation building toward a conclusion.

Explanation: This is that module's own opening scenario restated — under executive time pressure, reasoning that arrives before the answer reads as evasive or unprepared.

Alternative approaches considered: Simply being more concise while still explaining first, then concluding, doesn't fully fix the issue — the order needs to invert, not just compress.

Real-world reasoning: Tests whether "answer first, reasoning second" was understood as a structural inversion, not just "be brief."

Section 7 Complete

Across three modules, this section built the cross-functional relationship skills every QA leadership track eventually needs: working effectively with product and engineering around their actual concerns, coordinating shared infrastructure with DevOps and managing stakeholders more broadly, and communicating with executives using an answer-first discipline. From here, continue to Section 8 — Scaling Quality, starting with QA in Startups vs. Enterprises.