Directors on the housing-voucher ART schedule a dedicated hardening iteration at the end of every PI so testers can hunt defects after feature work. What should the Scrum Master / Team Coach do?
Select an answer to reveal the explanation.
Short Explanation
A hardening iteration is a mop at the end of a muddy hallway. If voucher work only gets real testing after the PI, quality never lived in the work. Build it in with test-first, CI, and a real Done—do not calendar a cleanup festival.
Full Explanation
A dedicated hardening iteration every PI is a smell that quality is not built in. Directors on the housing-voucher ART who schedule end-of-PI tester defect hunts after feature work are institutionalizing late inspection. The Scrum Master/Team Coach should treat regular hardening as evidence to coach test-first, continuous integration, and a real Definition of Done throughout the PI so voucher increments are releasable without a reserved rework slot.
Putting hardening on the PI calendar as a reserved quality slot fails by concept: it legitimizes deferred quality as the operating model. Parking untested voucher stories in IP so a regular iteration can remain hardening fails by concept by misusing IP and continuing to separate build from test. Standing up a System Team hardening backlog while feature teams ship untested stories fails by concept: it moves rework sideways instead of fixing team-level built-in quality.
Exam caveat: SAFe teaches built-in quality continuously; recurring hardening sprints/iterations are a recognized anti-pattern on advanced Scrum Master exams. Occasional stabilization for exceptional risk differs from making hardening the planned default every PI.
Operational check: map defects found only in hardening, coach DoD/CI/test-first on voucher teams, shrink or remove the reserved hardening iteration as in-flow quality rises, and show directors declining late defect discovery.