<Project Name> Project Brief

<Project Name>Project Brief <date> <Project Manager name> <regional project-id> Template version 2.0

<project name> <project ID> 1. Mandate Project Background – Rationale for Action Project Governance Please summarize the project background Project Planning Budget / Resources Project Objectives • Please summarize the project objectives in a list (1-5) and link them to your company KPI’s (e.g. risk, profit, cost) Project Deliverables • Please summarize the project key deliverables in a list (1-5) Constraints & Risks • Please describe any limitations you can think of Project Dependencies In Scope Out of Scope • Please summarize what is in scope • Please summarize what is out of scope

<project name> <project ID> Document Management Revision History ApprovalsThis document requires the following approvals. Signed approval forms are filed in the Management section of the project file. For each ‘’ a descriptionneeds to beprovidedon the recommnedations building block (3). DistributionThis document has been distributed to.

<project name> <project ID> 3. Project Background / Dependencies Project name Project name This Project Project name Project name Project name Delivers output to Waiting for output from

<project name> <project ID> 4a. Scope (1/2) PoV: ‘Business capabilities to measure project execution success’

<project name> <project ID> 4a. Scope (2/2)

4b. Product Breakdown Structure <project name> <project ID> 1 Milestone 1.1 Key deliverable 1.3 External deliverable 1.1.1 Sub deliverable 1.1.2 Sub deliverable 1.1.3 Sub deliverable 1.1.3.1 Sub deliverable 1.1.3.2 Sub deliverable 2 Milestone 2.1 Group A 2.2 Group B 2.2.1 Sub deliverable 2.1.1 Sub deliverable 2.1.2 Sub deliverable 2.2.2 Sub deliverable 2.2.3 External deliverable Legend Group (Sub) Product/ deliverable External deliverable Milestone 7

<project name> <project ID> 5. Acceptance Criteria (to accept completed project)

<project name> <project ID> 6a. Impact Analysis

<project name> <project ID> Legend Road to follow Alternative path (not chosen) 6b. Project Approach Developed In House Project name Based on Specific Technology Alternative A Package Big Bang implemen-tation Alternative B Based on existing product In stages, rolling wave planning Alternative C

<project name> <project ID> 6c. Assumptions

<project name> <project ID> 7b. Risks To be reported to Project Board Risk Priority Levels

<project name> <project ID> 8a. Cost and Benefit Cash Flow Streams

<project name> <project ID> 9. Organisation Project Board <project name> Project Manager <name> Project Assurance <name> (PMO) <name> (Expert) <name> (Architecture) Project Team <project name> <Lead Team X> <name> <name> <name> <Lead Team Y> <name> <name> <name> <Lead Team Z> <name> <name> <name>

<project name> <project ID> 2011 Jan Feb Mar Apr May Jun Jul Aug Sept Oct Nov Legend Milestone Tolerance: =/- xx days 10. Project Plan / <date> Requirements gathering Business requirements Functional requiremetns Approval of requirements by Project Board Product design and build of prototype First design Review design Build prototype Testing FAT UAT Roll out / implementation Prepare for roll out Local communication and training local organization Stage 2 Stage 3 Stage 4

<project name> <project ID> 2011 date date date date date date date date date date date Legend Milestone Tolerance: =/- xx days 20. Initiation Stage Plan / <date> PID preparation Detail Business requirements Define PoV’s and deliverables Detail functional requirements Detail System requirements Prepare Quality Plan Prepare Comm. Plan Resource Planning Create Project Plan Refine Business Case PID quality approval PID Approval by Project Board

<project name> <project ID> 11. Resources / <date> Needed for PID creation 17

<project name> <project ID> 14. Budget Details / <date> Needed for PID creation 18

<Project Name>Project Initiation Documentation <Date> <Project Manager name> <Regional Project-id> Version 2.0

PID Please include all building blocks from the PB except the initiation stage plan, resources and budget.

<project name> <project ID> 11. Resources

<project name> <project ID> 12. Budget Details / <date>

13a. Quality Plan <project name> <project ID>

<project name> <project ID> 14. Benefits Review Plan

<project name> <project ID> 15a. Stakeholders Map Positionstakeholderson the map • Key stakeholders need to accept the objectives and will be fully engaged • Participation project board • Sign-off business requirements • Demo product • Weekly highlight reports & issue log • Regular business update meetings • Operational acceptance • Stakeholders need to agree the translation of objectives into activities • Good working relationships to ensure an effective coalition of support for the project • Careful monitoring and management as they may be a source of significant risk • Progress updates via newsletters • Stakeholders be kept informed of progress and remedies taken to achieve the objectives • limited monitoring or evaluation • Progress updates via newsletters • Stakeholders notified of milestone completion • limited monitoring or evaluation • Progress update via newsletters 1 Importance of the stakeholders to the organisational activity Low Medium High • Name 1 • Risk • Compliance High • Name • Name 2 2 • Name Medium PMO Potential impact of organisational activity of the stakeholders (Audit) 3 3 • Name Low 4 4

<project name> <project ID> 15b. Communication Management Strategy Analysis – What is the communication issue? Project Background – What should be known on forehand? Please summarize the communication issue Please summarize the project background Assumptions • Please summarize the communication assumptions in a list (1-5) Project Communication Action Plan

<Work package name><Project name> <date> <Project Manager name> <regional project-id> Version 2.0

Work Package Please include Mandate + Scope + Product Breakdown building blocks from the PID

<project name> <project ID> Legend Group (Sub) Product/ deliverable External deliverable Milestone 21. Work Breakdown - <project name>Work Package - <work package name> 1 Milestone 1.1 Key deliverable 1.3 External deliverable 1.1.1 Sub deliverable 1.1.2 Sub deliverable 1.1.3 Sub deliverable 1.1.3.1 Sub deliverable 1.1.3.2 Sub deliverable

<project name> <project ID> 22. Product Description - <project name>Work Package - <work package name> (1/3)

Highlight Report Please include budget details building block from PID

Project Manager: xxx Project Owner: yyy Project ID: id Project Cost Center: CC Project Name - Highlight 1/2Reporting period dd/mm/yyyy – dd/mm/yyyy

Project Manager: xxx Project Owner: yyy Project ID: id Project Cost Center: CC Project Name - Highlight 2/2Reporting period dd/mm/yyyy – dd/mm/yyyy Change requests

<Project Name>End Stage Report <date> <Project Manager name> <regional project-id> Version 2.0

End Stage Report Please include updated building blocks from the Mandate, Business Case and the last Highlight Report and the Risk building block 40

25. Recapitulation <project name> <project ID> 41

26. Follow-on Action Recommendations <project name> <project ID> 42

27. Lessons Learned <project name> <project ID> • Remarks: • Collecting to be mentioned items during the project life cycle makes life easier at the end. (Lessons Log) • What went well, what could be improved? What would you do different if you have to do it again? 43

<Project Name>End Project Report <date> <Project Manager name> <regional project-id> Version 2.0

End Project Report Please include updated building blocks from the Mandate, Business Case and the last Highlight Report 46

25. Recapitulation <project name> <project ID> 47

26. Follow-on Action Recommendations <project name> <project ID> 48

27. Lessons Learned <project name> <project ID> • Remarks: • Collecting to be mentioned items during the project life cycle makes life easier at the end. (Lessons Log) • What went well, what could be improved? What would you do different if you have to do it again? 49

<Project Name> Project Brief