システム開発のプロジェクトマネジメントに関する記述 a~d のうち,スコープのマネジメントの失敗事例だけを全て挙げたものはどれか。 a 開発に必要な人件費を過少に見積もったので,予算を超過した。 b 開発の作業に必要な期間を短く設定したので,予定期間で開発を完了させることができなかった。 c 作成する機能の範囲をあらかじめ決めずにプロジェクトを開始したので,開発期間を超過した。 d プロジェクトで実施すべき作業が幾つか計画から欠落していたので,システムを完成できなかった。
令和5年度 ITパスポート試験 問54
This question's explanation and your answers so far.
問 54
Incorrectア
a, b. Item a is a case where labor cost was underestimated and the budget was exceeded, which is a failure of cost management that manages cost. Item b is a case where the work period was set too short and could not be finished in time, a failure of schedule management that manages time. Neither is scope management, so this is wrong.
Incorrectイ
b, c. Item c is correctly a scope failure, but item b is a failure of schedule management caused by setting the period too short, not a scope failure. It also improperly omits d, which is a scope failure, so this is wrong.
Incorrectウ
b, d. Item d is correctly a scope failure, but item b is a failure of schedule management caused by a too-short (poorly set) period setting, not a scope failure. It also improperly omits c, which is a scope failure, so this is wrong.
- エ
正解 Scope management is the activity of defining and managing, without excess or shortfall, the range of deliverables the project creates and the work that must be done to produce them. The key point is that failure cases should be classified by their root cause, not by their surface symptom. For c, the symptom that the development period was exceeded looks schedule-like, but its cause was starting the project without deciding in advance the range of functions to create, that is, an omission in defining the scope, so it is a failure of scope management. For d, the work that should have been carried out was missing from the plan, meaning the necessary range of work was not identified in the WBS, which is also a failure of scope management. Therefore the failure cases are only the two, c and d, and the answer that lists only those, c, d, is correct.
- Scope management is the activity of defining and managing, without excess or shortfall, the range of deliverables and the work to be carried out. Starting without deciding the range (c), or letting necessary work slip out of the plan (d), are scope failures.
- Classify failure cases by cause, not by symptom. Even though c shows the symptom of an exceeded development period, its cause is undefined scope, so it belongs to scope. On the other hand, if the cause is a budget overrun from a too-optimistic estimate it is cost, and if the cause is a delivery delay from a too-optimistic period setting it is the schedule management domain; do not confuse these with scope.