A project team member is reviewing the scope of a task with an end user and realizes that requirements have changed. Which project artifact should be used in this situation?

Question

Options

• AScope management plan
• BRisk management plan
• CConfiguration management plan
• DProject management plan

• A
  8% (2)
• C
  4% (1)
• D
  88% (23)

Explanation

When requirements change during scope review, the Project Management Plan (D) is the go-to artifact because it contains all subsidiary plans and baselines - including the scope baseline, change control procedures, and the processes needed to formally evaluate and document scope changes. It provides the integrated framework for handling exactly this kind of situation.

Why the distractors are wrong:

• A (Scope Management Plan): This is actually a component of the project management plan, not a separate artifact used for handling changes - it describes how scope will be defined and controlled, but you'd reference the full PMP to act on a change.
• B (Risk Management Plan): This governs how risks are identified and responded to. A scope change isn't inherently a risk event requiring this plan.
• C (Configuration Management Plan): This controls versions of project documents and deliverables, not the process for addressing changed requirements.

Memory tip: Think of the Project Management Plan as the "master key" - all other plans (scope, risk, configuration) live inside it. Whenever a question involves a cross-cutting situation like a scope change that touches process, baselines, and approvals all at once, the PMP is almost always the answer.

No community discussion yet for this question.