Project Governance Deck Template Project Meetings Structure and









- Slides: 9
Project Governance Deck Template
Project Meetings Structure and Governance (OLS Auth) An Important Element in the Project’s success is proper communication to Project team and key stakeholders. The primary objectives of these meetings are to ensure the Project is on track, Deliverables are Met and Milestones are achieved in the desired timeframe. Going forward the OLS Auth Weekly Project Meeting Cadence will consist of the following Structure: • Project Status Overview - High Level Status from PM with main focus on deliverables and dates. • Project Activity Status Detail - PM Led Sprint Planning and Sprint Review. There will be a Two week sprint iteration for each Epic. All Jira tasks relevant to each Epic for that particular Sprint will be reviewed. The responsibility will lie with the Task owner that each assigned task be updated with utmost detail. • Product Status Meeting – SPM Led meeting which covers Operation stability issues and risks. Also will introduce discussions on any special topics. • Detailed Project Review – PM led Status gathering sessions including setting Milestone
1 Project tatus Overview Project Activity Status Detail Project Risks & Issues Decision & Action Items Proposed Changes
Project Status • Provide a high-level image of the current project status • Notes in this box should highlight critical dates • If the project time line has changed since the last meeting be sure to point that out
Project Status Detail Last meetings totals • The image above shows a detailed view of tasks and where they are in the project – this was derived directly from Service. Now PPS • Depending on the state of your project you may or may not need to show this detail or can also be shown as a bar graph or pie chart • Use this space to provide high-level overview of what the detail means – you will need to talk them through this. • Showing last meeting’s numbers will help to show a trend – improvement or a reason for concern -
Risks & Issues 2 Likelihood of Occurrence 5 1 4 3 3 2 1 1 Issue / Risk 1. List out the issues/risks that require executive attention – basically these are the ones that could derail the project 2. The numbers in the boxes above correlate to the risks/issues listed here 3. 2 3 4 Business Impact 5 Mitigation Update Provide any updates regarding what is being done to mitigate this risk/issue
Decision & Action Items Decision/Action Item List Items that require Decisions or Actions to by the exec or key stakeholders You may also list decisions or actions that belong to others that are delayed or may impact the project Assigned To Status
Changes Proposed Changes List any changes that you may be proposing Expected Impact What the expected impact or outcome is Decision What the Go/no go decision is and who made the decision.