CAPM Practice: Determine how to document project controls of predictive, plan-based projects

Configuration management controls the characteristics of project deliverables — ensuring that any change to approved specifications goes through a formal process. It maintains the integrity of the product baseline, controls versions of documents and deliverables, and ensures stakeholders are always working from current, approved versions.

**Why not A:** Configuration management has nothing to do with computer hardware or software configurations used by team members. It is a project management discipline focused on controlling the characteristics and versions of project deliverables and their specifications.

**Why not B:** Following the "same configuration in agile sprints" conflates IT configuration with project configuration management and introduces agile concepts irrelevant to a predictive project context. Configuration management in predictive projects ensures deliverable specifications are formally controlled.

**Why not D:** Configuring the schedule for resource availability describes resource management or resource leveling, not configuration management. Configuration management controls product specifications and deliverable characteristics, not schedule or resource parameters.