PMP Keeping Artifacts Traceable Through Configuration and Version Control

Configuration and version control matter because project artifacts lose value when nobody can tell what changed, which version is current, or whether the current record reflects an approved project state. PMP questions in this area usually test whether the project manager can preserve traceability and baseline discipline instead of letting records drift informally.

Version Numbers Alone Are Not Enough

Strong control is not just a naming scheme like v3-final-final2. It is a disciplined way to answer these questions:

• What is the current controlled version?
• What changed from the previous version?
• Who authorized that change?
• Does the artifact reflect the approved project state?
• Which older versions are still relevant for history, comparison, or audit?

That is why version control is part of configuration management, not just document housekeeping.

    flowchart TD
	    A["Artifact needs to change"] --> B["Assess whether the change is permitted or approved"]
	    B --> C["Update the controlled record and capture what changed"]
	    C --> D["Mark the current version and retire superseded copies"]
	    D --> E["Use the controlled version as the project source of truth"]

Connect Artifact Changes to Project Change Control

One of the most exam-relevant ideas here is alignment. If the project approves a scope, schedule, design, or requirements change, the related controlled artifacts should be updated accordingly. If they are not, the project can end up with one approved story and a different operational record.

The stronger answer usually ensures traceability between:

• the approved change or authorized update
• the modified artifact
• the current controlled version now in use

That linkage helps the project defend its current state during audits, governance reviews, and delivery disputes.

Uncontrolled Copies Create Delivery Risk

Version confusion is not a cosmetic issue. If teams use different baseline copies, design documents, test scripts, or release criteria, the project may perform the wrong work while believing it is aligned. The PMP exam often rewards candidates who treat this as a control and execution risk, not as a minor administrative inconvenience.

The right response usually includes removing dependence on local copies, identifying the authoritative source, and clarifying what counts as the current approved record.

Example

A requirements baseline is updated after a formally approved change, but several teams keep using an older local copy that still reflects the pre-change state. The stronger move is not just to announce the new version. The project manager should make the current approved record visible in the controlled source, preserve the change trace, and stop the outdated copy from driving work.

Common Pitfalls

• Using version labels without documenting what changed.
• Leaving superseded versions active in working channels.
• Updating artifacts without traceability to approved change.
• Assuming small or internal artifacts do not need disciplined version control.

Check Your Understanding

Sample Exam Question

Scenario: A change request affecting the approved scope baseline has been formally approved. The PMO repository contains the updated baseline, but the technical team is still using a local copy that predates the change. A defect trend begins to appear because the team is validating against the wrong acceptance criteria.

Question: What is the strongest first action?

• A. Let the technical team finish the current work cycle before addressing version control
• B. Ask each team to annotate its own local copy with the approved change
• C. Create a new tracker to note version disagreements without touching the baseline record
• D. Update and reinforce the controlled current version, preserve traceability to the approved change, and stop work from relying on superseded copies

Best answer: D

Explanation: The strongest answer is D because the project has a configuration-control failure. The approved change must be reflected in the controlled baseline, and teams must be brought back to the same authoritative version. Preserving traceability to the approved change is essential for defending the current project state.

Why the other options are weaker:

• A: Continuing work against the wrong baseline extends the defect and control problem.
• B: Local annotation preserves fragmentation instead of fixing it.
• C: A side tracker does not restore baseline discipline.

Key Terms

• Configuration control: The discipline of governing changes to controlled project items and records.
• Controlled version: The artifact state the project recognizes as current and authoritative.
• Traceability to change: A visible link between an approved change and the updated artifact that reflects it.