Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Project Governance
Overview1. What is governance?2. Defining governance levels3. Defining the governance forum(s) and the   agendas4. Definin...
What is it? Every project, no matter what size, will require governance You probably don’t think about it much or call i...
Yes, so WHAT IS IT? Quite simply, governance is the infrastructure around your  project which deals with:   –Culpability/...
Define the levels ofresponsibility
1. Who do you need to deliver to? Who are the people you answerable to for the delivery of this  project? Do you communi...
2. Who needs to deliver for you?   Who is responsible for performing tasks on your project?   What are they responsible ...
Examples:1. Who do you need to deliver   2. Who needs to deliver forto?                             you? Account Manager ...
Now group those people eg.Day-to-day delivery          Day-to-day signoff        Overall project signoffCopywriter        ...
Now give them a name eg.Project delivery team        Project Review Board      Project Executive BoardCopywriter          ...
IS IT A BIG PROJECT?If it is…get yourself a Project Sponsor, 1 person who you haveaccess to, who has ultimate responsibili...
Define the forum(s) and theagendasWhere will you speak to your people and whatwill you discuss?
Scrums meetings      15 minutes      What did you do yesterday?      What will you do today?      Will anything preven...
Executive Board Meetings      Review product backlog and confirm the prioritisation      Distribute current copy deck   ...
Now decide on the frequencyTeam                        FrequencyProject delivery team       DailyProject Review Board     ...
Other useful one-off Meetings    Planning meeting           Agree the tasklist           Agree durations    Commitment...
Now send out the meeting requests –include the agenda  Project Governance
Define the reporting toolsWhat information will you distribute in yourmeetings?
Project reporting documentationCommon sense needs to be applied on the level of detail anddocumentation, but on EVERY proj...
Communicate the governanceMake sure that everyone is clear on thebaseline report and their responsibilities.
Thank-you
Upcoming SlideShare
Loading in …5
×

Project governance

46,072 views

Published on

Published in: Business, Technology
  • Login to see the comments

Project governance

  1. 1. Project Governance
  2. 2. Overview1. What is governance?2. Defining governance levels3. Defining the governance forum(s) and the agendas4. Defining the reporting tools5. Communicating the governance Project Governance
  3. 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. 4. Yes, so WHAT IS IT? Quite simply, governance is the infrastructure around your project which deals with: –Culpability/ responsibility Project Governance
  5. 5. Define the levels ofresponsibility
  6. 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. 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. 8. Examples:1. Who do you need to deliver 2. Who needs to deliver forto? 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. 9. Now group those people eg.Day-to-day delivery Day-to-day signoff Overall project signoffCopywriter Project Manager legal representativeResource manager Senior Project Manager branding representativeProject Director Project Director compliance representativeWeb developer Head of Technology senior clientDesigner Creative Director Programme DirectorPlanner Head of User Experience Client Services DirectorAccount Manager Day-to-day client Project lead from overlapping projectsDay-to-day client Client Services ManagerNinja Planning Director Project Governance Head9 of Social Media Slide Date to go here
  10. 10. Now give them a name eg.Project delivery team Project Review Board Project Executive BoardCopywriter Project Manager legal representativeResource manager Senior Project Manager branding representativeProject Director Project Director compliance representativeWeb developer Head of Technology senior clientDesigner Creative Director Programme DirectorPlanner Head of User Experience Client Services DirectorAccount Manager Day-to-day client Project lead from overlapping projectsDay-to-day client Client Services ManagerNinja Planning Director Project Governance Head10 Social Media Slide of Date to go here
  11. 11. IS IT A BIG PROJECT?If it is…get yourself a Project Sponsor, 1 person who you haveaccess to, who has ultimate responsibility for the delivery ofthis project Project Governance
  12. 12. Define the forum(s) and theagendasWhere will you speak to your people and whatwill you discuss?
  13. 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. 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 risksProject Governance
  15. 15. Now decide on the frequencyTeam FrequencyProject delivery team DailyProject Review Board WeeklyProject Executive Board Monthly Project Governance
  16. 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. 17. Now send out the meeting requests –include the agenda Project Governance
  18. 18. Define the reporting toolsWhat information will you distribute in yourmeetings?
  19. 19. Project reporting documentationCommon sense needs to be applied on the level of detail anddocumentation, but on EVERY project you need to track andreport: – Deliverables – Assumptions – Risks – Issues – Changes – Milestones – Budget, recon and forecast Project Governance
  20. 20. Communicate the governanceMake sure that everyone is clear on thebaseline report and their responsibilities.
  21. 21. Thank-you

×