A slow city identity vendor threatens the forecast for a citizen self-service portal. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A stuck identity vendor is a closed bridge, not a reason to park the whole city. Say the dependency out loud and send the traffic that can still move. Hiding the delay keeps a pretty date and a portal nobody can use.
Full Explanation
Dependencies must be transparent in the forecast; hiding them preserves a date that empiricism already knows is at risk. Reordering the Product Backlog to deliver citizen value that does not require the vendor keeps learning and Current Value moving. Idling the entire portal, or promoting the vendor date to Product Goal, lets an external constraint replace product strategy. The Product Owner inspects the dependency and adapts order rather than freezing the original outlook.