Section 3 Review

Section 3 covered the core people-leadership skills every QA leadership track eventually depends on: influencing without formal power, running a team deliberately, building others' judgment, deciding what to delegate, and resolving genuine conflict.

Knowledge Check

Work through these five scenarios before checking the Section 3 Solutions.

Scenario 1: The Unaddressed Process Gap

A Senior QA Engineer notices releases keep shipping with untested edge cases, but says nothing, believing process changes aren't their responsibility until they have a formal title. What should they do instead, per this section?

Scenario 2: The Inconsistent Team

A new QA Lead makes every team decision case by case, with no explicit structure. Within months, the team is functional but inconsistent, and workload is imbalanced. What's missing?

Scenario 3: The Repeated Question

A junior tester asks the same type of question — how to prioritize edge cases — for the third time, despite getting a direct, correct answer each previous time. What should the mentor do differently?

Scenario 4: The Centralized Bottleneck

A QA Lead reviews and approves every test-case decision personally, even routine, low-risk ones. What's the cost of this approach, and what should change?

Scenario 5: The Side-Picking Resolution

A QA Lead resolves a disagreement between a developer and a QA engineer by simply siding with the QA engineer. The same type of disagreement resurfaces on the next release. What went wrong?

Next: Check your answers against the Section 3 Solutions, then continue to Section 4 — Engineering Excellence.