According to the PMBOK® Guide and the Standard for Project Management, a Change Request is a formal proposal to modify any document, deliverable, or baseline. When issues are found while project work is being performed, change requests are submitted to modify project policies or procedures, project scope, project cost or budget, project schedule, or project quality.
As per PMI standards, change requests are a primary output of many Monitoring and Controlling processes and the Direct and Manage Project Work process. They are processed through the Perform Integrated Change Control process and can include:
Corrective action: An intentional activity that realigns the performance of the project work with the project management plan.
Preventive action: An intentional activity that ensures the future performance of the project work is aligned with the project management plan.
Defet repair: An intentional activity to modify a nonconforming product or product component.
Updates: Changes to formally controlled project documents or plans to reflect modified or additional ideas or content.
The other options are incorrect based on the following PMI definitions:
Requirements documentation: This describes how individual requirements meet the business need for the project. While it can be modified via a change request, the document itself is not a proposal to change.
Scope baseline: This is the approved version of a scope statement, work breakdown structure (WBS), and its associated WBS dictionary. It is the target of a change request rather than the proposal itself.
Risk urgency assessment: This is a tool and technique used in Qualitative Risk Analysis to prioritize risks based on how quickly a response is needed. It does not function as a formal proposal for modifications.
As per the PMI Lexicon of Project Management Terms, the formal nature of a change request ensures that no unauthorized changes are made to the project ' s established baselines, maintaining the integrity of the project ' s performance measurement.
