Skip to content

ACCA Strategic Professional · Strategic Business Leader · Leading and managing projects

Orlin Construction is building a hospital under a fixed-price contract. Midway, the client requests several additional features without formal approval, the team agrees informally, and costs and timeline begin to grow. Which control mechanism would most directly have prevented this problem, and what does it imply for the project's baseline?

Formal change control would have prevented it. Each requested feature would be assessed for cost, time and risk impact and approved before the baseline is changed, so scope creep is managed. Post-implementation review is too late, contingency is not a substitute for approval, and critical path analysis cannot stop requests.

  1. AA post-implementation review, which would reset the baseline after completion
  2. BA formal change control process, so that each request is assessed for cost, time and risk impact and approved before the baseline is changedCorrect
  3. CA contingency reserve, which removes the need to approve changes
  4. DA critical path analysis, which would stop the client making requests

Explanation

The problem is scope creep from uncontrolled changes. A formal change control process evaluates the impact of each request and requires authorisation before the baseline is revised. Post-implementation review comes too late, contingency does not replace approval, and critical path analysis does not govern client requests.

Did you get it right without looking?

One question tells you little. A timed set on Leading and managing projects shows your real accuracy, how long you take and where you lose marks.

More Leading and managing projects questions