問48
頻出度★★★
プロジェクトの立上げ時に考慮すべき事項として, 適切なものはどれか。
平成24年度 春期 ITパスポート試験 問48
マネジメント系プロジェクトマネジメント › プロジェクトマネジメント
This question's explanation and your answers so far.
解説
問 48
Incorrectア
Incorrect. Assumptions and constraints include not only internal ones (staff skills and headcount, in-house standards, existing systems, and so on) but also, and especially, those in the external environment that one cannot control (laws and regulations, exchange rates and market conditions, the circumstances of clients and vendors, seasonal factors, and so on), which must be clarified. Leaving them unaddressed just because they cannot be controlled leads to risks being overlooked, and the plan collapses with no countermeasures prepared. Precisely because such factors cannot be controlled, stating them explicitly as assumptions, registering them as risks, and drawing up monitoring and response plans is the basis of project management, so the statement that it is “meaningless and therefore not done” is inappropriate.
Incorrectイ
Incorrect. The purpose of a project is the very first thing to be clarified at initiation and shared among the parties involved. Only once there is a purpose can the boundaries of scope, the definition of deliverables, the setting of priorities, and the criteria for judging completion be determined. Presenting the purpose only after it becomes clear what outcomes are likely reverses ends and means, letting the means define the purpose; scope then swells without limit partway through, and expectations differ from one stakeholder to another. The difficulty of foreseeing how progress will unfold is not a reason to postpone the purpose.
Incorrectウ
Incorrect. Because the information available at the time of initiation is limited, a rough estimate (a top-down estimate) based on past similar projects and the like is enough for the budget. A concrete estimate for each smallest subdivided process (each work package of the WBS) is a bottom-up estimate made after the scope has been broken down into a WBS during the planning process, and it is not a precondition for initiation. Estimating accuracy is raised in stages as planning proceeds, so the statement that a project cannot be initiated because this cannot be done confuses the roles of initiation and planning.
- エ
正解 The correct answer is エ. Project initiation is the first process in which a project is formally launched and its existence and framework are recognized by the organization. The central deliverable here is the project charter, which documents the project's purpose and objectives, the main deliverables, the rough budget and duration, the assumptions and constraints, the main stakeholders, and so on, and which also appoints the project manager and states their responsibilities and authority explicitly. By deciding on the project manager at an early stage and formally defining how far they may make decisions on their own (assigning staff, spending funds, approving specification changes, and the like), decision-making does not stall in the later planning, execution, and monitoring processes, and responsibility is clearly located. Conversely, if work goes ahead while no one is in charge, the chain of command breaks down and, when a problem occurs, nobody can make a decision. Therefore the appropriate matter to consider at initiation is エ, which says to appoint a project manager and clarify their responsibilities and authority.
ここがポイント
- At project initiation, the purpose, deliverables, assumptions, and constraints are documented in the project charter, and a project manager is appointed with responsibilities and authority formally clarified. These are the requirements for formally launching a project.
- Assumptions and constraints should be identified on both the internal and the external side. The more an external factor is beyond one's control, the more it is worth identifying and monitoring as a risk; detailed budget estimates, meanwhile, are refined based on the WBS during the planning process after initiation, so a rough estimate is sufficient at initiation.
用語