CAPM Change Control & Configuration 4 — Questions and Answers
Question 1: A customer requests a 'small' wording change to a contractual deliverable. Why should this still go through formal change control?
- Because all contract changes require legal approval
- Because even small changes can affect scope, schedule, cost, or quality (Correct answer)
- Because the project charter requires it for all deliverables
- Because only the CCB can define what is 'small'
Correct answer: Because even small changes can affect scope, schedule, cost, or quality
Even minor changes can have cascading effects on other project baselines, so all changes should be evaluated through the formal process.
Question 2: The change log is BEST described as:
- A record of all project risks and their status
- A document that tracks the status of all change requests throughout the project (Correct answer)
- The list of approved changes to be implemented in the next sprint
- A summary of corrective actions taken during project execution
Correct answer: A document that tracks the status of all change requests throughout the project
The change log is used to document and track all change requests, including their status, disposition, and any updates made.
Question 3: Which of the following BEST describes integrated change control?
- Managing only scope-related changes across the project
- Coordinating changes across all project knowledge areas in an integrated way (Correct answer)
- Reviewing only customer-initiated change requests
- Documenting changes after they have been implemented
Correct answer: Coordinating changes across all project knowledge areas in an integrated way
Integrated change control ensures that changes in one area are evaluated for their effect on all other project areas before approval and implementation.
Question 4: A project manager notices that several team members are implementing changes verbally agreed upon in meetings without submitting change requests. What is the risk of this practice?
- Increased team collaboration
- Scope creep and uncontrolled baseline changes (Correct answer)
- Faster project delivery
- Improved stakeholder satisfaction
Correct answer: Scope creep and uncontrolled baseline changes
Implementing changes without formal change requests leads to scope creep, untracked baseline modifications, and loss of project control.
Question 5: What is the role of the project management information system (PMIS) in change control?
- It replaces the CCB for routine changes
- It provides tools to track, store, and communicate change request status (Correct answer)
- It automatically approves low-impact change requests
- It generates change requests from risk triggers
Correct answer: It provides tools to track, store, and communicate change request status
The PMIS supports the change control process by providing tools for documenting, tracking, and communicating the status of change requests.
Question 6: During project execution, a risk becomes an issue that requires a schedule adjustment. What formal action should the project manager take?
- Adjust the schedule informally and note it in the team meeting minutes
- Submit a change request to update the schedule baseline (Correct answer)
- Update only the risk register
- Escalate directly to the sponsor without documentation
Correct answer: Submit a change request to update the schedule baseline
Any adjustment to a baseline—including the schedule baseline—requires a formal change request processed through integrated change control.
Question 7: Which configuration management activity verifies that the functional and physical characteristics of a configuration item conform to its requirements?
- Configuration identification
- Configuration status accounting
- Configuration control
- Configuration audit (Correct answer)
Correct answer: Configuration audit
A configuration audit verifies that the configuration item meets its documented functional and physical requirements before it is baselined.
CAPM Change Control & Configuration 4
A customer requests a 'small' wording change to a contractual deliverable.
Why should this still go through formal change control?