Optimise-GB provides you with a free template for the programme start up document. This document is based on MSP, Lean and Six Sigma programme methodologies. The key difference and unique perspective for this methodology is that the programme never closes down but focuses on continuous improvement. This document reduces the number of documents that can often lead to confusion. The document sets the reason for the programme in regards to operational strategies, objectives and balanced scorecard reporting. As with most programme management methodologies, the document focuses on the now (Current state / as is) again the future (to be / future state). There are several inbuilt excel templates to boot including objectives weighting mechanisms, SIPOC flow diagrams and business cases. Please contact me should you have any questions on simon@optimise-gb.com and visit www.optimise-gb.com for more details. Many thanks Simon Misiewicz

1. Programme Start up
[Title]
Author: [Author]
Your Business Name
Street Address
Address 2
Telephone
Fax
E-Mail
Date: [Date]
Distribution: [Distribution list]
Version: [Enter Version number]
Version Date Authorised by Narrative
1.0

2. 1.0 Purpose
This document defines the project, sets out how the project is to be managed and
provides the baseline against which the project is continually assessed. It is an
overarching collection of documents brought together to form the basis for
management approach and analysis of overall success.
2.0 Vision and Mission Statement
3.0 Strategic positioning
4.0 Business Process (SIPOC)
SUPPLIER INPUTS PROCESS OUTPUTS CUSTOMER
5.0 Balanced scorecard / KPI’s - current “as is”
Must cover time, cost, quality
Project: [Project Name] Version:
Author: Date:
Status [Draft/Final]
Page 2 of 8

3. 6.0 Balanced scorecard / KPI’s - future “to be”
Expected benefits
7.0 Weighted Objectives
Project: [Project Name] Version:
Author: Date:
Status [Draft/Final]
Page 3 of 8

4. Weighting Objectives - which objectives overrides the others
[Objective 1]
[Objective 3]
[Objective 5]
[Objective 6]
[Objective 7]
[Objective 8]
[Objective 9]
[Objective 2]
[Objective 4]
Scores
Rank
[Objective 1] 0 1
[Objective 2] 0 1
[Objective 3] 0 1
[Objective 4] 0 1
[Objective 5] 0 1
[Objective 6] 0 1
[Objective 7] 0 1
[Objective 8] 0 1
[Objective 9] 0 1
8.0 Quality / Critical to success
8.1 Critical to Quality
8.2 Quality assurance
8.3 Responsibilities to ensure quality
Project: [Project Name] Version:
Author: Date:
Status [Draft/Final]
Page 4 of 8

5. 8.4 Reporting on quality performance issues
9.0 In scope (Deliverables)
10.0 Out of scope
11.0 Business Case
Project: [Project Name] Version:
Author: Date:
Status [Draft/Final]
Page 5 of 8

6. Year 0 Year 1 Year 2 Year 3 Year 4 Yea
Initial Investment
- Capital equipment costs £0
- 3rd Party costs £0
- Internal costs £0
Total costs £0
Benefits
- Headcount savings £0 £0 £0 £0 £0
- Efficiency savings £0 £0 £0 £0 £0
- Additional Revenue £0 £0 £0 £0 £0
Total Benefits £0 £0 £0 £0 £0
Ongoing costs
- Capital equipment costs £0 £0 £0 £0 £0
- 3rd Party costs £0 £0 £0 £0 £0
- Internal costs £0 £0 £0 £0 £0
Total costs £0 £0 £0 £0 £0
Benefit / (Loss) £0 £0 £0 £0 £0 £0
Payback
NPV 5% £0
Cumulative Benefits £0 £0 £0 £0 £0
Cumulative costs £0 £0 £0 £0 £0
Cumulative Benefits / (Loss) £0 £0 £0 £0 £0
£1
£1
£1
£1
£1
£1
£0
£0
£0
£0
£0
Year 0 Year 1 Year 2 Year 3 Year 4
Cumulative Benefits Cumulative costs
12.0 Approach - Framework
12.1 Programme Management
Project: [Project Name] Version:
Author: Date:
Status [Draft/Final]
Page 6 of 8

7. The programme framework will be initiated with the “Programme start up” document.
Once the objectives have been identified and ratified, then a “Programme improvement
document” will be written and a project portfolio (listing all projects in the programme)
will be managed.
The programme process will utilise the following tools:
- Business Risk log
- Issues log
- Lessons learned log
- Change request logs
- Stakeholder maps
12.2 Project Management
Every project in the portfolio will be imitated with a “project start up document” and
reviewed periodically through the “project delivery report” and then reviewed and
handed back to the business through the “project closure report”
Each project will utilise the following tools:
- Business Risk log
- Issues log
- Lessons learned log
- Change request logs
- Stakeholder maps
13.0 Project portfolio management
14.0 Programme Team
14.1 Programme team
14.2 Roles & responsibilities
15.0 Stakeholders, Communication & reporting
The progress for the project will be communicated via the “programme delivery report”
that will measure the objectives in regards to the time, cost and quality targets
Project: [Project Name] Version:
Author: Date:
Status [Draft/Final]
Page 7 of 8

8. 16.0 Issues and risk management
The programme and business issues / risks will be listed in the “programme issues log”
and “programme risk log”. All mitigating actions will be identified and agreed. Each
mitigating factor will be incorporated into the project portfolio.
17.0 Tolerance levels
Tolerance levels % Description of tolerance levels
Cost
Quality
Time
18.0 Change control management
Project: [Project Name] Version:
Author: Date:
Status [Draft/Final]
Page 8 of 8