DOC

Work Package Definition v2

By Leo Scott,2014-03-28 09:40
8 views 0
Work Package Definition v2

    WORK PACKAGE DEFINITION

    Project Title Project Ref:

    Work Package Title Work Package Manager

    Sponsor Project Manager

    Version Date of Issue

    Document Ref Document Author

    1. DOCUMENT CONTROL

    3.3 DOCUMENT SIGN OFF PROCESS

    This section should state the purpose of the document and explain the process for

    gaining sign-off approval. Typically this will include how individuals have been

    selected for sign-off, lead time for approvals and method by which the document will

    be issued.

    3.4 SIGN OFF

    [Include as many names as required to gain appropriate approval]

    Name Project Role Signature

    3.5 CHANGE HISTORY

    Issue Issue Date Revised by Reasons for Update

    Number

    3.6 DISTRIBUTION

    [The action field should reflect what the recipient of the document is being requested

    to do. Read for information only, comment on the content of the document, quality

    controls it as so on.]

    Name Role Action

2. PROJECT INTRODUCTION

    3.7 PROJECT BACKGROUND

    [An overview of the project including objectives, rationale for change and brief overview of work to be accomplished. It is important that in this section any measurable targets or benefits are started]

Objective Target Delivered By

3.8 TOP LEVEL WORK PACKAGE AND PROJECT MILESTONES

    [Overall project milestones will be provided by the project manager. Significant work package milestone need to be stated here, particularly where there are specific dependencies.]

    Milestone Due Date Date Completed Accountable

3. TERMS OF REFERENCE

    3.9 DESCRIPTION OF WORK

    [An overview of the work package manager’s deliverables including a brief

    description of the work to be accomplished]

3.10 PROJECT ORGANISATION

    [Project Organisation Chart showing the work package manager to be provided by

    Project Manager]

3.1.1. Work stream Organisation

    [Organisation Chart showing the proposed team within the work stream where applicable]

3.11 ROLES AND RESPONSIBILITIES

    3.1.2. Project Manager

    [State the role of the Project Manager in terms of the level of governance that will be applied to the project. It is useful in the section to state how reporting and communication with the project will be dealt with]

    3.1.3. Work package Manager

    [State the role of the work package manager to ensure it is clear in terms of their level of responsibility, how they will manage and report on their element of the project,]

3.11.3 Others

    [State additional roles that need to be identified relevant to the work package only. An example of this may be is an external third party is sharing delivery of the work package.]

3.12 DEPENDENCIES

    Date Required Dependency Impact Area/ Project Dependant Upon

    Description

    When does the Description of High/Medium/Low Which areas/ project/ programme is it

    dependent task Dependency dependant upon?

    end?

3.13 RISK ASSESSMENT

    [Identify any risks associated with your work stream. Mitigating actions should highlight the actions required to prevent the risk or reduce it if it occurs.]

    Date Raised Risk Description Probability Impact 1-3 (Mitigating)

    1-3 (L,M,H) (L,M,H) Actions Owner

3.14 ASSUMPTIONS

    [A statement of supposed fact accepted as true for the purposes of planning.]

Date Assumption Description Actions Required (if relevant)

3.15 WORK PACKAGE EXCLUSIONS

    [Any tasks, assumptions, activities which are beyond the scope of this work stream and as such will not be considered or completed by this work package]

Report this document

For any questions or suggestions please email
cust-service@docsford.com