Parks reservations, special-event street closures, and building permits only talk when a festival weekend blows up in an emergency war room. What portfolio design should the Product Owner pursue?
Select an answer to reveal the explanation.
Short Explanation
If three city products only meet when a festival is on fire, the building is the problem, not the firefighters. War rooms feel productive, but they are a tax on last-minute coupling. Better product boundaries mean a street closure does not need a midnight permit scramble.
Full Explanation
Chronic emergency coordination is a portfolio design smell: products are coupled in ways that destroy Time-to-Market and hide who owns which citizen journey. Reducing coupling — clearer interfaces, shared calendar data, fewer sequential handoffs — beats institutionalizing war rooms. A program manager who seizes three Product Backlogs, or a PMO RAID log, centralizes coordination without removing the dependency. Standing war rooms make the smell the process.