ITPEC IP April 2025 Question 56
When a system development project is started, it is foreseen that the progress of the project may be affected by a large number of change requests for specification that come from users during the course of development. Which of the following is the most appropriate measure for ensuring that there is no deterioration in quality or delay in delivery date?
Explanation
Agreeing with the customer on what change requests can be accepted and how their priority is decided — rules set at the start keep changes from eating into quality and the delivery date.
Many change requests are foreseen, so the project plans its response before they arrive. With the customer it agrees a change-control procedure: which requests are in bounds, how each one's effect on cost, schedule and quality is assessed, who approves it, and how accepted requests are prioritised, with the rest deferred to a later release. Changes are then taken in only as far as the plan can absorb them.
Answer (d)
Why not others:
- •(a) — refusing every change after design is a one-sided declaration; changes the business really needs are shut out and the system may not meet the users' needs
- •(b) — skipping tests to recover a delay directly lowers quality, the very thing the measure must protect
- •(c) — calling off functions just because many requests arrive drops agreed functions without weighing which requests matter
Key rule: Scope changes that can be foreseen are managed by an agreed change-control procedure (criteria, impact assessment, approval, priority), not by refusing them or absorbing them at the cost of quality.
Project Management · AI-written, may contain errors
This question comes from an official ITPEC past paper. ITPEC Practice is an independent study tool and is not affiliated with ITPEC. See the official IP past-paper collection or Report an issue.