Controlling Escalating Costs due to Scope Creep in New Software Implementation | CISA Exam Preparation

Key to Controlling Escalating Costs due to Scope Creep in New Software Implementation

Prev Question Next Question

Question

When an organization is having new software implemented under contract, which of the following is key to controlling escalating costs due to scope creep?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

C.

When an organization is having new software implemented under contract, it is common for the project's scope to expand beyond the initial expectations, resulting in cost overruns, missed deadlines, and unsatisfied customers. Therefore, it is essential to have proper controls in place to manage scope creep and prevent cost escalation.

Out of the options provided, the most relevant control to prevent scope creep and control costs is change management (option C). Change management is the process of controlling changes to a project's scope, schedule, or budget. By managing changes systematically, the project team can identify the impact of the change, evaluate its costs and benefits, and decide whether to implement it or not.

Effective change management can help organizations prevent scope creep, which is the uncontrolled expansion of a project's scope, leading to additional costs, delays, and risks. When changes are proposed, the project team needs to evaluate their impact on the project's scope, schedule, and budget. Based on this analysis, they can decide whether to approve, reject, or defer the change.

In addition to change management, risk management (option D) can also help control costs by identifying potential risks and developing mitigation strategies to reduce their impact. Quality management (option B) can help prevent rework and ensure that the software meets the organization's requirements, but it is not directly related to controlling scope creep. Problem management (option A) is focused on resolving incidents and problems that occur during the project, but it is not related to controlling scope creep.

Therefore, the most appropriate answer is C - Change management.