256 | Appendix A: Product Description outlines controls are adequate to ensure that the project remains compliant with such a directive Consideration has been given to the format of the Project Initiation Documentation. For small projects a single document is appropriate. For large projects it is more appropriate for the Project Initiation Documentation to be a collection of stand-alone documents. The volatility of each element of the Project Initiation Documentation should be used to assess whether it should be stand-alone, e.g. elements that are likely to change frequently are best separated out. A.21 PRojeCt PRoDuCt DesCRiPtion A.21.1 Purpose The Project Product Description is a special form of Product Description that defines what the project must deliver in order to gain acceptance. It is used to: Existing products to be modified Design specifications A feasibility report Project mandate Development skills required An indication of the skills required to develop the product, or a pointer to which area(s) should supply the development resources Customer's quality expectations A description of the quality expected of the project's product and the standards and processes that will need to be applied to achieve that quality. They will impact on every part of the product development, and thus on time and cost. The quality expectations are captured in discussions with the customer. Where possible, expectations should be prioritized Acceptance criteria A prioritized list of criteria that the project's product must meet before the customer will accept it ­ i.e. measurable definitions of the attributes that must apply to the set of products to be acceptable to