What feature allows a project manager to track changes in project scope effectively?

Question

Options

• AIssue logs
• BChange request forms
• CResource planner
• DBaseline snapshots

• A
  12% (6)
• B
  4% (2)
• C
  6% (3)
• D
  78% (38)

Explanation

Baseline snapshots (D) are correct because they capture the approved project scope at a specific point in time, giving the project manager a fixed reference to compare against - making scope changes (creep or approved changes) immediately visible as deviations from that baseline.

Issue logs (A) track problems and concerns that arise during execution, not scope changes specifically. Change request forms (B) are used to submit or document a proposed change, but they don't provide a tracking mechanism for how scope has evolved over time. Resource planner (C) deals with people and equipment allocation, unrelated to scope tracking.

Memory tip: Think of a baseline as a "before photo" - you can't tell what changed unless you have a snapshot of what the project looked like before any changes were made.

No community discussion yet for this question.