A program includes multiple projects to deliver new prototypes. One project has concluded all scheduled tasks, and there are no unresolved concerns. However, several managers are asking for additional features. Which step should the program manager complete before allowing final closure of this project?
Permit the enhancements and close the project after introducing the requested changes
Close the project once the final product is delivered without discussing any extra requests
Request a contract amendment, extend the timeline, and add desired features under the same project
Verify alignment with the original scope, gain stakeholder consensus, and close upon meeting the scope baseline
Ensuring the project has fulfilled its planned objectives and scope—while also confirming stakeholder agreement—prevents unplanned changes from undermining the established goals. If requests go beyond the original scope, they should be handled through formal change control. Closing when the scope baseline is satisfied avoids scope creep and maintains alignment with the broader initiative. Other choices either disregard key closure tasks or improperly push new work into the existing project timeline.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is scope baseline in project management?
Open an interactive chat with Bash
What is formal change control?
Open an interactive chat with Bash
What does it mean to gain stakeholder consensus?
Open an interactive chat with Bash
PgMP
Program Life Cycle Management
Your Score:
Report Issue
Bash, the Crucial Exams Chat Bot
AI Bot
Loading...
Loading...
Loading...
Project Management Package Join Premium for Full Access