Change Control & Configuration Management Flashcards
7 cards from real CPP practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Change Control & Configuration Management flashcards as text
Which change control document captures all submitted change requests along with their status and disposition?
Answer: Change log
The change log tracks all change requests, their current status (pending, approved, rejected), and final disposition throughout the project.
Configuration identification involves which of the following activities?
Answer: Selecting and labeling configuration items and establishing baselines
Configuration identification selects which items will be controlled, assigns unique identifiers, and establishes the initial baselines.
When assessing a proposed change, a project manager performs an impact analysis. What does this analysis evaluate?
Answer: Effects on scope, schedule, cost, quality, risk, and resources
A thorough impact analysis examines how the proposed change affects all project constraints including scope, schedule, cost, quality, risk, and resources.
What is a 'baseline' in the context of configuration management?
Answer: A formally approved version of a work product used as a reference for future comparison
A baseline is a formally approved snapshot of a product or plan that serves as the fixed reference point against which future changes are measured.
Which of the following BEST describes configuration status accounting?
Answer: Recording and reporting the status of configuration items and approved changes
Configuration status accounting maintains records of the status of each configuration item and tracks changes from baseline through implementation.
A client requests a small, seemingly low-cost change to a software module. The project manager should FIRST:
Answer: Log the request and perform a formal impact analysis
All changes, regardless of perceived size, must be formally logged and analyzed for impact before approval or rejection.
Emergency changes that bypass the standard CCB process should ALWAYS:
Answer: Be documented and retroactively reviewed by the CCB as soon as possible
Even emergency changes must be documented and submitted for formal CCB review after the fact to maintain configuration integrity.