問32
頻出度★★★
プロジェクト・スコープ・マネジメントで実施する作業として, 適切なものはどれか。
平成25年度 秋期 ITパスポート試験 問32
マネジメント系プロジェクトマネジメント › プロジェクトマネジメント
This question's explanation and your answers so far.
解説
問 32
Incorrectア
“Form the project team and develop its members.” is a task of resource management (human resource management). It means gathering the people needed, forming a team, assigning roles and responsibilities, and raising the team's capability through training and motivation; what it deals with is people (resources), not the range of work. It is the later step of deciding who will carry out the work that scope management has identified, not the work of defining the scope itself.
- イ
正解 The correct answer is イ, “Identify the work required for the project without omission or excess.” Project scope management is the management activity of clearly defining the deliverables the project will produce and the range (scope) of work needed to produce them, and then getting the project completed exactly within that range. If the scope is left vague, missing work leads to schedule delays, and work that was never requested gets taken on — scope creep (the swelling of the scope) — so neither effort nor cost can be estimated. Scope management therefore starts by listing the deliverables and the work required, and then breaks the work down hierarchically as a WBS (Work Breakdown Structure). The principle of a WBS is to break higher-level work down into lower-level work with no gaps and no overlaps, which is exactly what identifying the required work without omission or excess means. The scope fixed in this way becomes the foundation for every later management activity, such as building the schedule, estimating costs, and assigning staff. Therefore イ is appropriate.
Incorrectウ
“Identify the project's stakeholders and decide how to communicate with them.” is a task of stakeholder management and communication management. It means listing the people who have an interest in the project — the client, the user departments, partner companies and so on — and planning who is told what information, when, and by what means (meetings, reports, email, and so on). Its subject is the flow of information and the coordination of the parties involved, not deciding the deliverables or the range of work.
Incorrectエ
“Identify the project's risks and consider countermeasures.” is a task of risk management. It means listing the uncertain events that could threaten the achievement of the project's objectives, analyzing their probability and impact to set priorities, and preparing responses such as avoidance, mitigation, transfer, and acceptance. What gets listed is risks, not work, so its purpose differs from defining the scope.
ここがポイント
- Project scope management: the management activity of defining the project's deliverables and the range of work required to produce them, and getting the project completed within that range. Its central technique is the WBS (Work Breakdown Structure); breaking work down hierarchically with no gaps and no overlaps is how the required work is identified without omission or excess. The scope fixed here is the premise for estimating schedule, cost, and resources.
- Learn to tell the knowledge areas apart: deciding the range of work = scope, dates = schedule (time), money = cost, people and teams = resource (human resource), information flow and coordination of the parties involved = communication / stakeholder, preparing for uncertain events = risk, quality standards = quality, buying from outside = procurement. Once you can tell which knowledge area a choice describes, you can decide right from wrong with certainty.
用語