Online Mind Mapping and Brainstorming

Create your own awesome maps

Online Mind Mapping and Brainstorming

Even on the go

with our free apps for iPhone, iPad and Android

Get Started

Already have an account? Log In

PRINCE2 (TM) Work Package by Mind Map: PRINCE2 (TM) Work
Package
0.0 stars - 0 reviews range from 0 to 5

PRINCE2 (TM) Work Package

Overview

Purpose

A Work Package is a set of information about one or more required products collated by the Project Manager to pass responsibility for work or delivery formally to a Team Manager or team member.

Contents

A Work Package should cover the following topics. The content may vary greatly according to the relationship between the Project Manager and the recipient of the Work Package.

Work Package Authorisation

Description

Techniques, Processes and Procedures

Development Interfaces

Operations and Maintenance Interfaces

Configuration Management Requirements

Joint Agreements

Tolerances

Constraints

Reporting Arrangements

Problem Handling and Escalation

Extracts or References

Approval method

Work Package Acceptance

Advice

A Work Package is derived from any existing commercial agreements between the customer and supplier (if appropriate); Quality Management Strategy; Configuration Management Strategy; Stage Plan

A Work Package can take a number of formats, including: Document; Oral conversation between the Project Manager and a Team Manager; Entry in a project management tool.

Where the work is being conducted by a team working directly under the Project Manager, the Work Package may be an oral instruction - although there are good reasons for putting it in writing, such as avoidance of misunderstanding and providing a link to performance assessment. Where the work is being carried out by a supplier under a contract and the Project Manager is part of the customer organization, there is a need for a formal written instruction in line with standards laid down in that contract.

The following quality criteria should be observed:, The required Work Package is clearly defined and understood by the assigned resource, There is a Product Description for each required product, with clearly identified and acceptable quality criteria, The Product Description(s) matches up with the other Work Package documentation, Standards for the work are agreed, The defined standards are in line with those applied to similar products, All necessary interfaces have been defined, The reporting arrangements include the provision for raising issues and risks, There is agreement between the Project Manager and the recipient on exactly what is to be done, There is agreement on the constraints, including effort, cost and targets, The dates and effort are in line with those shown in the Stage Plan for the current management stage, Reporting arrangements are defined, Any requirement for independent attendance at, and participation in, quality activities is defined.

How to use this template

How to share this template with your team

Send an email, 1. Click Share this map, 2. Select Invite People, 3. Write a message, 4. Click Invite

Send a link, 1. Click Share this map, 2. Tick Link to share, 3. Copy the link to share it

Export, 1. Click down arrow, bottom right, 2. Select the export option you want

How to complete this template

Complete the sections in square brackets, [....]

Navigate using the links in Contents, Contents

Read these sections for help on the template, Purpose, Advice

Attribution

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

Get this template here

Document information

Project Name

[name]

Date

[date]

Release

Draft/Final

Author

[author]

Owner

[owner]

Client

[client]

Document Number

[number]

Revision, Approvals & Distribution

Revision History, Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Revision # [....], Revision Date, [date], Previous Revision Date, [date], Summary of Changes, [change], Changes Marked, [change mark], Date of next revision:, [....]

Approvals, Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version], Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version], Approval # [....], Name, [name], Signature, [signature], Title, [title], Date of Issue, [date], Version, [version]

Distribution, Distribution # [....], Name, [name], Title, [title], Date of issue, [date], Version, [version], Distribution # [....], Name, [name], Title, [title], Date of issue, [date], Version, [version]

Work Package Authorisation

Title

[...]

Person Authorised

The name of the Team Manager or individual with whom the agreement has been made

[Name the Team Manager or individual with whom the agreement has been made]

Date

The date of the agreement between the Project Manager and the Team Manager/person authorised

[Give the date of the agreement between the Project Manager and the Team Manager/person authorised]

Description

A description of the work to be done

[Give a description of the work to be done]

Techniques, Processes and Procedures

Any techniques, tools, standards, processes or procedures to be used in the creation of the specialist products

[Note any techniques, tools, standards, processes or procedures to be used in the creation of the specialist products]

Development Interfaces

Interfaces that must be maintained while developing the products. These may be people providing information or those who need to receive information

[Document the interfaces that must be maintained while developing the products. These may be people providing information or those who need to receive information]

Operations and Maintenance Interfaces

Identification of any specialist products with which the product(s) in the Work Package will have to interface during their operational life. These may be other products to be produced by the project, existing products, or those to be produced by other projects (for example, if the project is part of a programme

[Identify any specialist products with which the product(s) in the Work Package will have to interface during their operational life. These may be other products to be produced by the project, existing products, or those to be produced by other projects]

Configuration Management Requirements

A statement of any arrangements that must be made by the producer for: version control of the products in the Work Package; obtaining copies of other products or their Product Descriptions; submission of the product to configuration management; any storage or security requirements; and who, if anyone, needs to be advised of changes in the status of the Work Package

[State any arrangements that must be made by the producer for: version control of ; obtaining copies of other products; submission to configuration management; any storage or security requirements; and who, if anyone, needs to be advised of changes in the status of the Work Package]

Joint Agreements

Details of the agreements on effort, cost, start and end dates, and key milestones for the Work Package

[Detail the agreements on effort, cost, start and end dates, and key milestones for the Work Package]

Tolerances

Details of the tolerances for the Work Package (the tolerances will be for time and cost but may also include scope and risk)

[Time and cost tolerances (may also include scope and risk)]

Constraints

Any constraints (apart from the tolerances) on the work, people to be involved, timings, charges, rules to be followed (for example, security and safety) etc.

[Enter any constraints e.g. on the work, people, timings, rules etc.]

Reporting Arrangements

The expected frequency and content of Checkpoint Reports

[Enter the frequency and content of Checkpoint Reports]

Problem Handling and Escalation

This refers to the procedure for raising issues and risks

[How issues and risks will be raised and handled]

Extracts or References

Any extracts or references to related documents, specifically: · Stage Plan extract This will be the relevant section of the Stage Plan for the current management stage or will be a pointer to it · Product Description(s) This would normally be an attachment of the Product Description(s) for the products identified in the Work Package (note that the Product Description contains the quality methods to be used)

[References to related documents and/or extracts of related documents]

Approval Method

The person, role or group who will approve the completed products within the Work Package, and how the Project Manager is to be advised of completion of the products and Work Package

[Who will approve and how the Project Manager will be advised]

Work Package Acceptance

Person Accepting

The Project Manager or other person accepting the work package on the Project Manager’s behalf

[Name of the person accepting the work package]

Date

The date of acceptance

[Give the date of the acceptance]

Assessment and feedback

This can be used by the person accepting the work package to provide comments on the work package possibly to go towards performance appraisal for the individual or teams involved

[Provide comments on the work package possibly to go towards performance appraisal for the individual or teams involved]