Professional Documents
Culture Documents
BEFORE COMPLETING THIS DOCUMENT, PLEASE REFER PREVIOUS PROJECT(S) LESSONS LEARNED
Project Mandate
[insert project name]
Project Size: [insert project size (refer to sizing guide in appendix)]
Author(s):
Date:
Version: []
Group IT must be consulted for provision of ALL IT solutions ahead of the mandate being signed off.
Business teams should not engage with technology vendors without engaging IT in the first instance.
Any overhead resource assumptions included in your forecast MUST be validated by resource
owner
After approval of the Project Mandate by relevant parties, the approved copy is to be submitted to Group PMO
(GroupPMO@bsigroup.com) who will add it to the project register. The original mandate should be retained by
the business owner or assigned project manager.
Contents
1 Project Information...........................................................................................................3
2 Objectives, Strategic Alignment, Cost and Benefits..........................................................3
3 Change Impact & Impacted Business Areas......................................................................4
3.1 Impacted Business Areas...................................................................................................5
4 Data Privacy Impact..........................................................................................................5
5 Data Impact.......................................................................................................................6
6 Expected Timelines............................................................................................................6
7 Stakeholder Engagement.................................................................................................. 6
8 Approvals...........................................................................................................................7
9 Revision History.................................................................................................................7
10 Appendix.........................................................................................................................8
10.1 Sizing a Project.................................................................................................................8
1 Project Information
Project ID: [To be allocated by Group PMO Group Exec Name of the Group Exec Sponsor who is
once project is registered] Sponsor accountable for this project]
Business Area [Portfolio / Functional Area] Business [Name of the appointed Business Lead for
Lead this project]
Associated [State whether the project will be a stand-alone activity to fulfil a particular business
Programme or requirement or whether it is part of a bigger programme. Provide a brief description of what
other Projects they are and how they are associated]
Scope [Identify specific business areas that will be supported, functionality to be included, and/or
impacted sytems to be addressed during the project. If there is a need for the project to be
accomplished in phases, the specific boundaries for each phase should be stated.
List specific deliverables that are not defined as part of the project scope; this could include
things to be carried out by another project]
Project scope includes:
1.
2.
3.
Key [What “Outputs” will be created as a result of the project. These “Outputs” will enable the
Deliverables objectives and benefits to be achieved. Benefits can be financial (e.g. cost saving,
and Benefits decommissioning assets) or non-financial (e.g. business reputation, performance
improvements, organisational value add). Financial benefits will need to be agreed/validated
with finance during the ‘Initiation’ phase of the project lifecycle]
Assumptions [Describe any circumstances or events that are expected to occur for the project to be
successful - list all major assumptions]
Dependencies [Describe any other projects, initiatives or other business changes that are reliant on this
& Constraints project in order for them to be successfully delivered or vice versa. Identity any restrictions
known at this stage for example, there may be restrictions around when particular items of
work can be done or need to be completed by i.e. any events or circumstances that may
restrict, limit, or regulatory / legislative]
Risks [Provide a list of uncertain events or conditions that could occur resulting in a negative impact
on the project. Identify what you consider to be the top three risks at this stage]
1.
2.
3.
Customer / [Who is the ‘ultimate customer’ or user community that this will support/ is being delivered to
End Users (provide numbers if available). This can also be used to provide an indication of scale of user
base]
Project [Outline any initial ideas for how the project might be delivered including external delivery,
Approach consultants, governance arrangements etc. If applicable, have 3rd party arrangements
been discussed (MSA/SoW)? Is it clear how they will support the project? You will
need to factor in the time it takes to get a MSA/SoW in place via Procurement and
Legal and therefore plan for early engagement (could take 2-3 months+)]
5 Data Impact
[Confirm if the project could potentially result in changes to the collection, structure, quality and format of data
held within our systems.
If this section is relevant to the project, there will be a requirement to complete a Data Impact Assessment during
the initiate & design phase of the project]
Central Data Stewards
Kasia Kwak - Commercial, Marketing, Legal Sei-Ting Leung - Regulatory Services, Knowledge Solutions
6 Expected Timelines
[Using the template attached below, provide an outline of the project plan by giving major milestones (an
important achievement in a project) and their target dates. This plan may focus on the early stage of the
programme if there is a milestone to complete a Full Business Case, which will enable a detailed delivery plan.
Copy of template summary to be pasted into this document]
The project activities are summarised in the plan below:
Month 1 Month 2 Month 3 Month 4 Month 5 Month 6 Month 7 Month 8 Month 9 Month 10 Month 11 Month 12
Project
Activity 1 Narrative
Activity 2 Narrative
Activity 3 Narrative
Activity 4
Narrative
Activity 5 Narrative
7 Stakeholder Engagement
[Please complete the table below to include the stakeholders who need to be consulted at the outset of the project
(mandatory stakeholders have been highlighted in red, as you will need to factor in their interest and effort
required within the project)]
Role Stakeholder Name Engaged
(Y/N)
[Group IT Representative]
[Group Risk & InfoSec Representative]
[Legal Representative]
[Finance Representative]
[Change Management Representative]
[Solution Architect]
[Domain Data Governance Working Group]
[HR Representative]
[Procurement Representative]
[…]
8 Approvals
[It is mandatory to complete this section with names of the individuals that are approving the commencement of
this project. Must include information of the project sponsor in order to register and proceed with the project.
Please refer to the BSI delegated authority policy to confirm additional required approval level.]
Approver Name Title Date
[Project Sponsor]
[Business Lead]
[Group IT Representative
e.g Solution Architecture., Service Management]
9 Revision History
Revision Date Author Changes history Purpose Approved By
No.
10 Appendix
1 2 3 4 5
Business Impact Divisions Full-Life
Size Characteristics Type of Change Examples
H/M/L Impacted Cost
Table 2
¹ Decision of control and governance to be agreed at appropriate Governance forum (Group PMO can advise if needed)
² If the project is <£300k, the Project Mandate can be used as approval for the project to proceed
³ Group IT may want to manage this as a project or work request within their area (as appropriate)