問36
頻出度★★★
合意済みのシステム要件に対し, 機能追加となる変更依頼を顧客から受けた。このときの受託側の対応として, 適切なものはどれか。
平成22年度 春期 ITパスポート試験 問36
マネジメント系プロジェクトマネジメント › プロジェクトマネジメント
This question's explanation and your answers so far.
解説
問 36
Incorrectア
The person in charge of operations design is an expert on how the system will be operated after it goes live, and is important as someone who evaluates the impact of a change on operations, but does not hold the authority to decide whether a requirements change itself should be made. Only a meeting or a responsible person with decision-making authority can take on the impact on the project as a whole — development effort, cost, delivery date, and contract scope. If a specialist in a single area judges alone, a change can slip in while its effects on other areas are overlooked.
- イ
正解 The correct answer is “イ A meeting or a responsible person with decision-making authority decides whether to make the change.” Once system requirements have been agreed with the customer, they become the baseline for all later design, development, and testing. If a change such as adding a function is introduced, the development effort, cost, delivery date, impact on other functions, and even the scope of the contract all shift, so whether to make a change is not a matter that may be left to the judgment of an individual staff member. For this reason a project defines a change management procedure (a meeting with decision-making authority, such as a change control board, or a responsible person to whom that authority has been delegated): the change request form is formally received, its impact is analyzed, approval or rejection is formally decided, and only approved changes are reflected in updated requirements, plans, and estimates, which are then communicated to the stakeholders. Choice イ describes exactly this formal change management flow, so it is appropriate.
Incorrectウ
The sales representative does play the role of the contact point who receives change requests from the customer, but tends to take the position of wanting to grant the customer's wishes and cannot necessarily evaluate the technical impact on development or the increase in effort correctly. If the contact point accepts on their own authority and says “we will do it,” the work alone grows while neither the estimate nor the contract is updated, inviting what is called scope creep (uncontrolled growth of requirements). Receiving a request and approving it should be separated, and whether to make the change should be decided through the change management procedure.
Incorrectエ
The developer in charge of the software involved in the change is responsible for estimating feasibility and the effort required, but is not in a position to take the lead in deciding whether the change should be made. If a developer takes a change on board by their own judgment, implementation proceeds while the content of the change is neither recorded nor approved, and consistency with other modules, the impact on delivery date and cost, and version control of the deliverables all break down. The division of roles must be kept: supply technical assessment information to the change management meeting, and let the side that holds the authority make the decision.
ここがポイント
- A change request against requirements that have already been agreed (baselined) is handled according to the change management procedure. The flow is: formally receive the change request; analyze the impact on cost, delivery date, quality, and other functions; have a meeting with decision-making authority (such as a change control board) or a responsible person decide on approval or rejection; and reflect only approved changes in the requirements specification, plan, estimate, and contract, then inform the stakeholders. The key point is to separate the person who receives the request from the person who approves it.
- From the standpoint of project scope management, it is important to prevent uncontrolled additions to requirements (scope creep). If functions keep being added out of a staff member's goodwill or on a verbal agreement, the result is effort overruns, schedule delays, and later trouble over where responsibility lies. A change must always be documented and taken into the scope only after approval by a decision maker who holds the authority.
用語