A client continues to present the project team with additional changes. To help with agreeing upon an expected delivery date, the project manager sets up a meeting with stakeholders. Which of the following should this meeting identify?
This meeting should identify (and re-confirm) the project scope because repeated “additional changes” are classic drivers of scope change/scope creep, and scope is the primary input for setting a realistic delivery date. In CompTIA Project+ objectives, scope is explicitly treated as a planning-phase activity—e.g., creating a detailed scope statement and defining units of work—which then enables reliable scheduling and estimating.
When stakeholders keep adding changes, the project manager must use the change control process (collect the change requests, assess impacts, determine decision makers/CCB involvement, update the project plan, implement and validate changes, and communicate deployment). Agreeing on an “expected delivery date” requires stakeholders to align on what work is actually included (scope boundaries) so impacts to the schedule can be calculated and accepted.
While budget, objectives, and communication are important, they don’t directly resolve the problem created by ongoing additions: without a clarified, agreed scope baseline (what’s in vs. out), any delivery date becomes unstable and will continue to slip as new work is introduced.
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit