PMI-SP Governance and Control

Configuration control and schedule governance are the foundation of schedule credibility. PMI-SP expects you to establish how schedule files are stored, versioned, baselined, changed, retrieved, and protected before the schedule becomes operational.

What PMI-SP is really testing

This part of the exam is not just asking whether you know the word “baseline.” It is testing whether the schedule can be trusted as a control artifact. A scheduler should be able to explain who may update the model, how changes are approved, where history is preserved, and how the organization avoids losing the authoritative record.

Strong answers also recognize that policies, regulations, contractual requirements, and organizational procedures may all shape schedule governance. A clean-looking file is not enough if baseline control is weak.

Stronger versus weaker moves

Stronger answers:

• define storage, retrieval, change control, and baseline procedures early
• align schedule governance with contract and organizational rules
• preserve schedule history and accessibility
• separate authorized updates from informal edits

Weaker answers:

• let multiple users overwrite the model without control
• treat the latest file as authoritative even when change approval is unclear
• assume schedule governance can be fixed after execution starts
• focus on formatting instead of baseline discipline

Sample Exam Question

Several team leads maintain their own versions of the project schedule and send updates by email. The project now needs a formal baseline. What is the strongest next step?

A. Merge the latest versions manually and publish the cleanest-looking file B. Establish schedule configuration management and baseline control procedures before further schedule changes are accepted C. Freeze updates completely until project closure D. Ask each team lead to keep a separate baseline for their own work

Best answer: B

PMI-SP expects configuration management and baseline control to be established before the schedule becomes a reliable control document. B fixes the governance weakness directly. A may create a file, but not a controlled system. C stops useful work without solving control. D fragments authority further.