According to the PMBOK® Guide and the Standard for Project Management, specifically within the Manage Quality process (which encompasses quality assurance), Project documents serve as a critical input.
In the context of a Configuration Management System, project documents are part of the configuration items that must be controlled and monitored. Quality assurance work is influenced by these documents because they provide the specific standards, logs, and reports against which the project ' s processes are audited.
Relevant project documents used in this context include:
Quality Control Measurements: Used to analyze and evaluate the quality of the processes.
Quality Metrics: Used to verify that the project is meeting its quality objectives.
Risk Report: Provides information on sources of overall project risk that may impact quality.
Lessons Learned Register: Applied to improve the quality of the current process based on previous experiences.
The other options are incorrect based on the following PMI definitions:
Work performance data: This consists of raw observations and measurements identified during activities being performed (e.g., percent of work physically completed). While used in Control Quality, it is not the primary driver for the systematic quality assurance audits found in project documents.
Scope baseline: While the scope baseline defines what must be achieved, it is a higher-level planning component. The specific execution of quality assurance is more directly influenced by the detailed project documents and logs.
Requirements documentation: While important, this is typically a subset of what is covered under the broader " Project documents " category in the Manage Quality process. PMI specifically lists " Project documents " as a distinct input category for this process.
As per the PMI Lexicon of Project Management Terms, a configuration management system ensures that the latest versions of project documents are used, which is a prerequisite for effective and accurate quality assurance.
