The document discusses project governance and defines what it entails. It recommends defining governance levels by identifying who the project reports to and who needs to deliver work for the project. It also recommends defining governance forums like daily scrums, weekly project review board meetings, and monthly executive board meetings. The document advises defining the reporting tools needed to track deliverables, assumptions, risks, issues, changes, milestones, and budget. It stresses the importance of communicating the governance structure to ensure everyone understands their roles and responsibilities.

1. Project Governance

2. Overview
1. What is governance?
2. Defining governance levels
3. Defining the governance forum(s) and the
agendas
4. Defining the reporting tools
5. Communicating the governance
Project Governance

3. What is it?
 Every project, no matter what size, will require governance
 You probably don’t think about it much or call it governance
 Think about the structure of the governance on your project
BEFORE you start the project
 Governance takes time and costs money, ensure that you
have included it in your project planning
Project Governance

4. Yes, so WHAT IS IT?
 Quite simply, governance is the infrastructure around your
project which deals with:
–Culpability/ responsibility
Project Governance

5. Define the levels of
responsibility

6. 1. Who do you need to deliver to?
 Who are the people you answerable to for the delivery of this
project?
 Do you communicate with them directly or does someone
else do it on your behalf?
 What method will you use for communicating?
 How often will you communicate ?
 What will you communicate with them?
 What format will the information that you are trying to relay be
presented in?
Project Governance

7. 2. Who needs to deliver for you?
 Who is responsible for performing tasks on your project?
 What are they responsible for?
 When do they need to deliver it?
 How will they communicate with you?
 How often do you want them to communicate with you?
 What format do you want their communication to take?
 What format do you want the final deliverable to take?
Project Governance

8. Examples:
1. Who do you need to deliver 2. Who needs to deliver for
to? you?
 Account Manager  Planning team
 Project Director  Account team
 Heads of department  Client
 Creative Director  Creative team
 Client  Designers, Copywriters,
 Senior client developers etc…
 Resource Manager  External suppliers
Project Governance

9. Now group those people eg.
Day-to-day delivery Day-to-day signoff Overall project signoff
Copywriter Project Manager legal representative
Resource manager Senior Project Manager branding representative
Project Director Project Director compliance representative
Web developer Head of Technology senior client
Designer Creative Director Programme Director
Planner Head of User Experience Client Services Director
Account Manager Day-to-day client Project lead from
overlapping projects
Day-to-day client Client Services Manager
Ninja Planning Director
Project Governance Head9 of Social Media
Slide
Date to go here

10. Now give them a name eg.
Project delivery team Project Review Board Project Executive Board
Copywriter Project Manager legal representative
Resource manager Senior Project Manager branding representative
Project Director Project Director compliance representative
Web developer Head of Technology senior client
Designer Creative Director Programme Director
Planner Head of User Experience Client Services Director
Account Manager Day-to-day client Project lead from
overlapping projects
Day-to-day client Client Services Manager
Ninja Planning Director
Project Governance Head10 Social Media
Slide of
Date to go here

11. IS IT A BIG PROJECT?
If it is…get yourself a Project Sponsor, 1 person who you have
access to, who has ultimate responsibility for the delivery of
this project
Project Governance

12. Define the forum(s) and the
agendas
Where will you speak to your people and what
will you discuss?

13. Scrums meetings
15 minutes
What did you do yesterday?
What will you do today?
Will anything prevent you doing your work today?
Project Review Board Meetings
Review product backlog and confirm the prioritisation
Review progress against milestones
Review progress against budget
Review financial forecasts
Review of issues log
Review of risks log
Project Governance

14. Executive Board Meetings
Review product backlog and confirm the prioritisation
Distribute current copy deck
Distribute current designs
Review progress against budget
Raise any major issues
Raise any foreseen risks
Project Governance

15. Now decide on the frequency
Team Frequency
Project delivery team Daily
Project Review Board Weekly
Project Executive Board Monthly
Project Governance

16. Other useful one-off Meetings
Planning meeting
Agree the tasklist
Agree durations
Commitment meeting
Team members claim ownership of tasks
Team members estimate effort on their tasks
Team members commit to task delivery
Demo meeting
Team members display their work
Project Kickoff meeting
Project Governance

17. Now send out the meeting requests –
include the agenda
Project Governance

18. Define the reporting tools
What information will you distribute in your
meetings?

19. Project reporting documentation
Common sense needs to be applied on the level of detail and
documentation, but on EVERY project you need to track and
report:
– Deliverables
– Assumptions
– Risks
– Issues
– Changes
– Milestones
– Budget, recon and forecast
Project Governance

20. Communicate the governance
Make sure that everyone is clear on the
baseline report and their responsibilities.

21. Thank-you