PRINCE2 (TM) Product Status Account

To get an editable copy of this template to use on your project go to http://www.stakeholdermap.com/project-templates/prince-2-templates.html

Get Started. It's Free
or sign up with your email address
Rocket clouds
PRINCE2 (TM) Product Status Account by Mind Map: PRINCE2 (TM) Product Status Account

1. Overview

1.1. Purpose

1.1.1. 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.

1.2. Contents

1.2.1. The format following on page 3 is an example of the type of information the Project Manager may request as a Status Account on a Product or set of Products. Depending on the purpose of the request the Project Manager may request more or less information. This format would be repeated for each product included in the request.

1.3. Advice

1.3.1. The Product Status Account is derived from the Configuration Item Records and the Stage Plan.

1.3.2. A Product Status Account can take a number of formats, including: Document, spreadsheet or report from a database; Output from a project management tool.

1.3.3. The following quality criteria should be observed:

1.3.3.1. The details and dates match those in the Stage Plan

1.3.3.2. The product name is consistent with the product breakdown structure and the name in the Configuration Item Record.

2. How to use this template

2.1. How to share this template with your team

2.1.1. Send an email

2.1.1.1. 1. Click Share this map

2.1.1.2. 2. Select Invite People

2.1.1.3. 3. Write a message

2.1.1.4. 4. Click Invite

2.1.2. Send a link

2.1.2.1. 1. Click Share this map

2.1.2.2. 2. Tick Link to share

2.1.2.3. 3. Copy the link to share it

2.1.3. Export

2.1.3.1. 1. Click down arrow, bottom right

2.1.3.2. 2. Select the export option you want

2.2. How to complete this template

2.2.1. Complete the sections in square brackets

2.2.1.1. [....]

2.2.2. Read these sections for help on this template

2.2.2.1. Purpose

2.2.2.2. Advice

2.2.3. Navigate using the links in Contents

2.2.3.1. Contents

2.3. Attribution

2.3.1. Copyright © AXELOS Limited 2009. All rights reserved. Material is reproduced with the permission of AXELOS

2.4. Get this template here

3. Product Status Account

3.1. Report Scope

3.1.1. [Describe 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)]

3.2. Date Produced

3.3. Product Status

3.3.1. Product Identifier

3.3.2. Product Title

3.3.3. Version

3.3.4. Status and date of status change

3.3.5. Product State

3.3.6. Owner

3.3.7. Copy-holders

3.3.8. Location

3.3.9. User(s)

3.3.10. Producer

3.3.11. Date Allocated

3.3.12. Baseline Date planned

3.3.13. Actual

3.3.14. Planned date of next baseline

3.3.15. List of related items

3.3.16. List of related Issues and risks

3.3.16.1. [Include changes pending and approved]

3.4. Product Status

3.4.1. Product Identifier

3.4.2. Product Title

3.4.3. Version

3.4.4. Status and date of status change

3.4.5. Product State

3.4.6. Owner

3.4.7. Copy-holders

3.4.8. Location

3.4.9. User(s)

3.4.10. Producer

3.4.11. Date Allocated

3.4.12. Baseline Date planned

3.4.13. Actual

3.4.14. Planned date of next baseline

3.4.15. List of related items

3.4.16. List of related Issues and risks

3.4.16.1. [Include changes pending and approved]

3.5. Product Status

3.5.1. Product Identifier

3.5.2. Product Title

3.5.3. Version

3.5.4. Status and date of status change

3.5.5. Product State

3.5.6. Owner

3.5.7. Copy-holders

3.5.8. Location

3.5.9. User(s)

3.5.10. Producer

3.5.11. Date Allocated

3.5.12. Baseline Date planned

3.5.13. Actual

3.5.14. Planned date of next baseline

3.5.15. List of related items

3.5.16. List of related Issues and risks

3.5.16.1. [Include changes pending and approved]

3.6. Product Status

3.6.1. Product Identifier

3.6.2. Product Title

3.6.3. Version

3.6.4. Status and date of status change

3.6.5. Product State

3.6.6. Owner

3.6.7. Copy-holders

3.6.8. Location

3.6.9. User(s)

3.6.10. Producer

3.6.11. Date Allocated

3.6.12. Baseline Date planned

3.6.13. Actual

3.6.14. Planned date of next baseline

3.6.15. List of related items

3.6.16. List of related Issues and risks

3.6.16.1. [Include changes pending and approved]

4. Document information

4.1. Project Name

4.1.1. [name]

4.2. Date

4.2.1. [date]

4.3. Release

4.3.1. Draft/Final

4.4. Author

4.4.1. [author]

4.5. Owner

4.5.1. [owner]

4.6. Client

4.6.1. [client]

4.7. Document Number

4.7.1. [number]

4.8. Revision, Approvals & Distribution

4.8.1. Revision History

4.8.1.1. Revision # [....]

4.8.1.1.1. Revision Date

4.8.1.1.2. Previous Revision Date

4.8.1.1.3. Summary of Changes

4.8.1.1.4. Changes Marked

4.8.1.2. Revision # [....]

4.8.1.2.1. Revision Date

4.8.1.2.2. Previous Revision Date

4.8.1.2.3. Summary of Changes

4.8.1.2.4. Changes Marked

4.8.1.3. Revision # [....]

4.8.1.3.1. Revision Date

4.8.1.3.2. Previous Revision Date

4.8.1.3.3. Summary of Changes

4.8.1.3.4. Changes Marked

4.8.1.4. Date of next revision:

4.8.1.4.1. [....]

4.8.2. Approvals

4.8.2.1. Approval # [....]

4.8.2.1.1. Name

4.8.2.1.2. Signature

4.8.2.1.3. Title

4.8.2.1.4. Date of Issue

4.8.2.1.5. Version

4.8.2.2. Approval # [....]

4.8.2.2.1. Name

4.8.2.2.2. Signature

4.8.2.2.3. Title

4.8.2.2.4. Date of Issue

4.8.2.2.5. Version

4.8.2.3. Approval # [....]

4.8.2.3.1. Name

4.8.2.3.2. Signature

4.8.2.3.3. Title

4.8.2.3.4. Date of Issue

4.8.2.3.5. Version

4.8.3. Distribution

4.8.3.1. Distribution # [....]

4.8.3.1.1. Name

4.8.3.1.2. Title

4.8.3.1.3. Date of issue

4.8.3.1.4. Version

4.8.3.2. Distribution # [....]

4.8.3.2.1. Name

4.8.3.2.2. Title

4.8.3.2.3. Date of issue

4.8.3.2.4. Version