After a hiring freeze, leadership still adds scope to a public-health immunization registry, and Ability to Innovate then collapses. What should the Product Owner do with that evidence?
Select an answer to reveal the explanation.
Short Explanation
You cannot freeze hiring, pile on registry work, and still expect new value to appear like nothing happened. Ability to Innovate crashing is the dashboard light for that contradiction. Show leadership the numbers instead of hiding them, thinning Done, or trying to squeeze the same crew harder.
Full Explanation
Key Value Area evidence exists to expose whether leadership asks can be satisfied together. After a hiring freeze, leadership that still adds scope to a public-health immunization registry and then sees Ability to Innovate collapse has created a contradictory ask: less capacity and more ambition. The Product Owner should use that A2I evidence to make the contradiction visible so goals, scope, or staffing can be adapted.
Hiding the Ability to Innovate drop so the freeze looks successful destroys transparency and teaches the organization to ignore capacity signals. Promising the new scope by lowering the Definition of Done until A2I recovers trades quality and civic trust for a false schedule. Adding a project manager to force overtime until the backlog clears reinstalls command-and-control instead of resolving the capacity contradiction.
Exam caveat: PSPO II expects Product Owners to surface A2I evidence when scope and capacity collide—not to conceal, weaken Done, or overtime their way past physics.
Operational check: present pre/post freeze A2I capacity (or firefighting share) beside the newly added registry scope, and ask leadership which of scope, staffing, or timeline will change before the next ordering cycle.