The city portfolio currently funds forty digital initiatives at once, including permits, transit, parks, and public health, so every Scrum Team is context-switching. What should the Product Owner advocate?
Select an answer to reveal the explanation.
Short Explanation
Forty open city initiatives is forty half-cooked meals on one stove. Starting more work feels fair to every department and starves every product of finish and learning. Limit portfolio WIP so permits, transit, parks, and health can actually complete something.
Full Explanation
Portfolio throughput falls when too many initiatives share the same capacity. Context-switching hides as “progress” while few Increments reach Done or produce evidence. An advanced Product Owner advocates limiting work in progress at the portfolio level so the city finishes, inspects, and adapts faster. Starting more work, scoring starts, or collapsing forty products onto one Product Owner all worsen the overload.