The key to controlling escalating costs when an organization is having new software implemented under contract is change management, which is the process of identifying, evaluating, approving, and implementing changes to the project scope, schedule, budget, or quality1. Change management can help to control escalating costs by:
* Establishing a clear and agreed-upon baseline for the project deliverables, requirements, and expectations, and ensuring that they are aligned with the contract terms and conditions2.
* Defining and enforcing a formal and consistent change control process, which includes the roles and responsibilities, the criteria and methods, and the documentation and communication of the changes3.
* Assessing and prioritizing the proposed changes, and determining their impact and feasibility, and their alignment with the project objectives and constraints4.
* Obtaining the approval and authorization of the relevant stakeholders, such as the project sponsor, the project manager, the contractor, or the customer, before implementing the changes5.
* Monitoring and measuring the performance and outcome of the changes, and ensuring that they are delivered within the agreed scope, schedule, budget, and quality6.
References =
* Change Management - CIO Wiki
* Project Scope Management - CIO Wiki
* Change Control - CIO Wiki
* Change Impact Analysis - CIO Wiki
* Change Approval - CIO Wiki
* Change Evaluation - CIO Wiki

Section: Volume D

A loss event is the result of a realized risk scenario, as it represents the actual occurrence of an adverse outcome or impact due to the exploitation of a vulnerability by a threat. A threat event, a vulnerability event, and a technical event are not the results of a realized risk scenario, as they are more related to the sources, conditions, or mechanisms of the risk, respectively, rather than the outcome or impact of the risk. References = CRISC Review Manual, 7th Edition, page 100.