問38
頻出度★★★
システム開発プロジェクトの開始時に, 開発途中で利用者から仕様変更要求が多く出てプロジェクトの進捗に影響が出ることが予想された。品質悪化や納期遅れにならないようにする対応策として, 最も適切なものはどれか。
令和元年度 秋期 ITパスポート試験 問38
マネジメント系プロジェクトマネジメント › プロジェクトマネジメント
This question's explanation and your answers so far.
解説
問 38
Incorrectア
Declaring that no change requests at all will be accepted after the design is completed is an unrealistic response that rigidly shuts out even necessary changes. Ignoring users' legitimate needs risks producing an unusable system and also damages the trust relationship with the customer. It merely rejects changes rather than managing them, and does not solve the essential problem.
Incorrectイ
Omitting testing to shorten the schedule when a delay occurs is precisely an act that causes quality deterioration, bringing about the very quality deterioration the question seeks to prevent. Insufficient testing leads to overlooked defects, making it the least appropriate response.
Incorrectウ
Including in the plan that function implementation will be cancelled whenever many change requests arise is a passive, go-with-the-flow response that unconditionally cuts even necessary functions. Without criteria for what to keep and what to drop, or agreement with the customer, it risks harming the value and quality of the deliverables. It is inappropriate because it lacks the control found in option エ, where priorities and the scope of response are agreed with the customer.
- エ
正解 エ is correct. In a project where many specification changes are expected, the most effective approach is not to handle changes on an ad hoc basis after they occur, but to agree with the customer on change management rules at the start of the project. Specifically, decide in advance how incoming change requests will be prioritized and how far the scope of response will extend. This way, even when changes are concentrated, the important ones can be incorporated in a planned manner and their impact can be predicted and controlled, thereby preventing quality deterioration and delivery delays while still responding to the customer's legitimate requests. This is the basic idea of project scope management (change management).
ここがポイント
- Project scope management (change management): specification changes should not be rejected or handled ad hoc; instead they should be controlled by agreeing with the customer in advance on the prioritization method and the scope of response.
- A response that protects quality and delivery deadlines does not rely on sacrifices such as skipping tests or cutting functions, but on having a mechanism that can predict and control the impact of changes in advance.
用語