プロジェクトにおける開発予算に関する記述のうち, 最も適切なものはどれか。
平成22年度 春期 ITパスポート試験 問44
This question's explanation and your answers so far.
問 44
Incorrectア
The assertion that “you must not plan by summing up the estimates for each individual task” is wrong. Breaking the work down with a WBS or the like, estimating the effort and cost of each task, and adding them up is called bottom-up estimating (aggregate estimating), and it is a standard, recommended technique for building an accurate development plan. The total budget ceiling and the bottom-up total of the individual tasks stand to each other as an upper limit and its breakdown; they are meant to be cross-checked and reconciled, so there is no reason to forbid either one.
- イ
正解 The correct answer is イ. A project’s development budget is not a figure that is fixed once it is set during planning; it is something that must be managed continuously while the project is under way. You periodically total up the costs actually incurred (the actual results), compare them with the budget, and monitor whether any variance (an overrun or an underrun) has appeared. When the variance goes beyond the acceptable range, you analyze its cause and then review how the work is being carried out, adjust the scope, the schedule, or the staffing, and in some cases change the budget or the plan itself. Running this PDCA cycle of “plan → do → monitor and measure → correct (change the plan)” is the basis of cost management (cost control) in project management. イ states this principle plainly, so it is the most appropriate statement about a development budget.
Incorrectウ
Limiting the development budget to material procurement costs alone is wrong. In software development most of the cost is spent on people, so the personnel costs of the employees taking part in the project (effort × unit price) are naturally a central item of the development cost and are of course included in the budget. A budget that leaves personnel costs out cannot be used to manage the real cost, and variance analysis would not work either.
Incorrectエ
The assertion that the FP (function point) method should be used uniformly “regardless of whether a similar project exists” is wrong. If actual results from a similar past project are available, analogous estimating (top-down estimating), which takes those results as a baseline and adjusts for the difference in size, can be used quickly and effectively. The FP method also presupposes that the functions have been identified, so it is hard to apply at the planning stage, when the requirements are not yet fixed. Estimating techniques should be used selectively according to the stage of the project, the information that can be obtained, and the accuracy required.
- The basis of cost management is not to stop once the budget has been set, but to keep monitoring the variance between the actual results and the budget and to take corrective action or change the plan as needed (cost control through PDCA).
- Using estimating techniques selectively: there is bottom-up estimating (the aggregate method), which breaks the work down and adds it up; analogous estimating, which infers from the actual results of similar past projects; and the FP method, which computes size from the number and complexity of the functions. Choose among them according to the situation. Any statement that always forces or always forbids one particular technique can be judged wrong.