問50
頻出度★★★
システム開発の結合テスト段階において, 開発済の機能に追加や修正が必要となり, データベースの構成も変更することになった。プロジェクトマネージャの対応に関する記述 a～d のうち, 適切なものだけをすべて挙げたものはどれか。 a WBSを改定しプロジェクトスケジュールを見直す。 b 追加又は変更に要するコストを見積もる。 c データベースの構成変更に伴うリスクを洗い出す。 d 当初予定していた結合テストを完了させてから変更を行う。
平成23年度 特別試験 ITパスポート試験 問50
マネジメント系プロジェクトマネジメント › プロジェクトマネジメント
This question's explanation and your answers so far.
解説
問 50
- ア
正解 This question asks about the change management steps a project manager should take when a specification change occurs during project execution. Adding or modifying functions and changing the database configuration at the integration testing stage means extra work that was not built into the original plan, so the project manager must assess the impact of the change from three angles — work and schedule, cost, and risk — and reflect it in the plan. Item a means revising the WBS (Work Breakdown Structure) by adding the new work to it and reviewing the schedule accordingly; this is the basic action for reflecting a scope change in the plan. Item b is estimating the cost required for the addition or change, which is both the basis for deciding whether to carry out the change and the prerequisite for revising the budget and the cost plan. Item c is identifying, as risks, the effects that the database configuration change has on existing functions, data migration, performance, and so on; the larger the scope of a change, the more essential it is to identify risks in advance. Therefore a, b, and c are the appropriate items, and ア, which lists all of them, is the correct answer.
Incorrectイ
Items a and b are appropriate, but this option is wrong because it includes d. Item d — “complete the originally planned integration testing first, and then make the changes” — means running testing based on the pre-change specification all the way to the end even though additions and modifications are already known to be needed; most of those test results will be invalidated by the change, causing rework in the form of retesting and wasted effort. This option also omits the appropriate item c (identifying the risks that come with changing the database configuration), so it is incomplete as well.
Incorrectウ
Item b is appropriate, but this option includes the inappropriate item d and also omits the appropriate items a (revising the WBS and reviewing the schedule) and c (identifying the risks). If only the cost is estimated without reviewing the work plan and the risks, the added work will not be reflected in the WBS, the baseline for progress management will stop matching reality, and the project will move ahead with the impact of the database configuration change still unknown.
Incorrectエ
Item c is appropriate, but this option includes the inappropriate item d and also omits the appropriate items a and b. Even if the risks are identified, the change has not truly been reflected in the project plan unless the WBS and the schedule are revised and the additional cost is estimated.
ここがポイント
- Change management during project execution: when a specification change occurs, the project manager assesses its impact from three angles — scope and schedule (revising the WBS), cost (estimating the additional amount), and risk (identifying the effects) — and reflects it in the project plan.
- The WBS (Work Breakdown Structure) is the planning baseline that breaks work down hierarchically; once work is added or changed, it must be revised and the schedule redrawn. Finishing testing based on the old specification after a change has already come to light causes rework and wasted effort, so it should be avoided.
用語