A citizen-services app has a product roadmap of release themes and a project management plan for the delivery project. How should the team distinguish those documents?
Select an answer to reveal the explanation.
Short Explanation
Think restaurant menu versus kitchen shift plan. The roadmap is what diners will see over seasons; the PM plan is how tonight's service actually runs—staffing, timing, and change rules.
Full Explanation
The project management plan describes how the project is executed, monitored, and controlled; the product roadmap describes how the product is expected to evolve over releases. On a citizen-services app, both can coexist with different jobs. Saying both must list identical milestones so either can authorize baseline changes alone fails by concept: project baselines and change control live in project management planning; a roadmap’s themes are not automatically authorized project baseline changes. Saying the product roadmap replaces the project management plan once the first release theme is approved fails because product evolution guidance does not replace project governance, cost/schedule baselines, or integrated change control. Saying the project management plan lists only marketing themes while the roadmap lists cost and schedule baselines reverses the documents’ purposes. Exam caveat: CAPM and modern delivery practice distinguish product direction artifacts from project management plan components—especially on adaptive civic apps. Operational check: keep roadmap themes for product sequencing, keep the project management plan for delivery governance and baselines, and route project baseline changes through change control even when the roadmap shifts.