City leadership cannot see which digital-service bets are still ideas, which are scaling across neighborhoods, and which kiosk products should retire. What should the Product Owner establish?
Select an answer to reveal the explanation.
Short Explanation
A city portfolio without a board is a closet with the light off — the expired kiosk program is found by tripping on it. A kanban from idea to scale-or-retire shows flow, stuck work, and what should leave the closet. Lights on beat another RAG spreadsheet.
Full Explanation
Visualizing the initiative lifecycle from idea to scale or retire makes portfolio work-in-progress, aging, and exit criteria transparent. Gantt remaining-task charts and RAG sheets describe activity and status, not flow. Instantly staffing every idea as a Scrum Team explodes work-in-progress. A portfolio kanban supports inspect-and-adapt of the whole municipal pipeline rather than only the loudest project.