システム開発プロジェクトの品質マネジメントには, 成果物の品質要求事項や品質標準を定め, それらを達成するための方法を明確にする品質計画プロセスがある。 品質計画プロセスの考え方として, 適切なものはどれか。
平成27年度 春期 ITパスポート試験 問46
This question's explanation and your answers so far.
問 46
Incorrectア
Incorrect. Even if the deliverables are not exactly the same, the quality standards, quality metrics, review viewpoints, and defect tendencies used in past projects are organizational assets that are very useful for the quality planning of the next project. The idea of not referring to past results goes against the concept of continuous improvement in quality management.
Incorrectイ
Incorrect. It is inappropriate to say that the schedule should always be given top priority and that the period for reviews and tests may be shortened. Cutting back on quality checks delays the discovery of defects, increases rework in later processes, and in the end increases both cost and duration. Quality, cost, and schedule are constraints that affect one another, and giving one of them top priority unconditionally is not the idea of quality planning.
Incorrectウ
Incorrect. Opposite to イ, this option treats quality as absolute and says that no constraints should be set on the budget, but a project always has the constraint of a budget. Activities that raise quality also have a cost-effectiveness aspect, and spending cost without limit cannot be justified. Quality planning is about defining methods to efficiently achieve the required quality requirements within the given constraints.
- エ
正解 エ is correct. In the quality planning process, you decide “how much effort to put in” in order to achieve the target quality. The criterion for that judgment is the idea of quality cost: you compare and weigh the cost required for activities that build quality in, such as reviews and tests, against the effects those activities bring — less rework, higher productivity, and greater stakeholder satisfaction. Setting the quality standards and the methods for achieving them at a level where the effects justify the cost is the basic idea of the quality planning process. エ states exactly this comparison of cost and effect, so it is appropriate.
- Quality planning process: the process of defining the quality requirements and quality standards for deliverables and clarifying the methods to achieve them (reviews, tests, applying standards and procedures, etc.).
- Cost-effectiveness of quality cost: decide the level by comparing the cost of activities that build quality in against effects such as less rework, higher productivity, and greater stakeholder satisfaction. The idea of unconditionally giving top priority to any one of quality, cost, or schedule is wrong.