A team uses only a product management plan for a 311 app to control change requests on the delivery project. Why is that approach insufficient?
Select an answer to reveal the explanation.
Short Explanation
A product wishlist is not a change-control courtroom. Feature themes can guide what you want next; the project management plan is still where baselines and how-we-approve-changes live.
Full Explanation
Product direction documents do not replace project management plan elements that govern project change control and baselines. Using only a product management plan for a 311 app to control change requests on the delivery project is therefore insufficient. Saying product management plans are illegal to store beside project documents fails by concept: legality of co-storage is not the issue—governance roles differ. Saying change requests are never allowed on adaptive or predictive civic software projects fails because both approaches manage change—they differ in mechanism, not in forbidding change. Saying the product management plan already contains the only cost and schedule baselines the project needs fails because product plans steer product evolution; project baselines and integrated change control live in project management planning. Exam caveat: CAPM distinguishes product artifacts from the project management plan—especially when adaptive product roadmaps coexist with project governance. Operational check: route delivery change requests through the project change-control process defined in the project management plan, assess baseline impacts, and use the product plan for prioritization input without treating it as the change authority.