A city IT charter marks every future wish-list feature for a permitting system as “in scope” with no priority or phase. What risk does that create?
Select an answer to reveal the explanation.
Short Explanation
Stuffing every wish into “in scope” is like saying the grocery cart has no bottom. Without priority or a boundary, creep is almost guaranteed—and the charter stops protecting the team.
Full Explanation
Scope that includes an unbounded, unprioritized wish list fails to set a controllable boundary and heightens scope-creep risk. Capturing ideas can be useful in a backlog, but declaring all of them in-scope without limit is not predictive success. A charter is not an operations runbook, and it does not eliminate ongoing stakeholder engagement.