Free Trial

Safari Books Online is a digital library providing on-demand subscription access to thousands of learning resources.


Share this Page URL
Help

Appendix A: Product Description outlines > A.19 PROJECT BRIEF - Pg. 253

Appendix A: Product Description outlines | The Senior User(s) confirms that their Stage Plan. 253 requirements of the product, as defined in the Product Description, are accurately defined The Senior Supplier(s) confirms that the requirements of the product, as defined in the Product Description, can be achieved. A.18.4 format and presentation A Product Status Account can take a number of formats, including: Document, spreadsheet or report from a A.18 PRoDuCt stAtus ACCount database Output from a project management tool. A.18.1 Purpose The Product Status Account provides information about the state of products within defined limits. The limits can vary. For example, the report could cover the entire project, a particular stage, a particular area of the project, or the history of a specific product. It is particularly useful if the Project Manager wishes to confirm the version number of products. A.18.5 Quality criteria The details and dates match those in the Stage Plan The product name is consistent with the product breakdown structure and the name in the Configuration Item Record. A.19 PRojeCt BRief A.19.1 Purpose A Project Brief is used to provide a full and firm foundation for the initiation of the project and is created in the Starting up a Project process. In the Initiating a Project process, the contents of the Project Brief are extended and refined in the Project Initiation Documentation, after which the Project Brief is no longer maintained. A.18.2 Composition Report scope Describing the scope of the report (e.g. for the entire project, by stage, by product type, by supplier etc. The product's attribute can be used to select the subset of products for the report) Date produced The date the report was generated Product status For each product within the scope of the report, the report may include: Product identifier and title Version Status and date of status change Product state Owner Copy-holders Location User(s) Producer and date allocated to producer Planned and actual date Product Description was baselined Planned and actual date product was baselined Planned date for the next baseline List of related items List of related issues (including changes pending and approved) and risks. A.19.2 Composition Project definition Explaining what the project A.18.3 Derivation Configuration Item Records needs to achieve. It should include: Background Project objectives (covering time, cost, quality, scope, risk and benefit performance goals) Desired outcomes Project scope and exclusions Constraints and assumptions Project tolerances The user(s) and any other known interested parties Interfaces outline Business Case (see section A.2) Reasons why the project is needed and the business option selected. This will later be developed into a detailed Business Case during the Initiating a Project process Project Product Description (see section A.21) Including the customer's quality expectations,