Download - Project Performance Reporting
Project Performance Reporting
1
Gary Mainwaring
Project Performance Reporting - v1 - 01Mar16 2
Agenda
• Process
• Dependencies
• Reporting – Examples
• Lessons to Share
Project Performance Reporting - v1 - 01Mar16 3
PMC Process Map
Project Performance Reporting - v1 - 01Mar16 4
Proposal Execution
Project Start (KPIs)
Project Closedown
Baseline
Planning Planning Monitoring & Control
Project Performance Reporting
PMC Timeline
Project Performance Reporting - v1 - 01Mar16 5
PPR & GoPM
Organisation
Corporate
Governance
Project
Management
GoPM
Project Performance Reporting - v1 - 01Mar16 6
Basic Elements of PPR
• Baseline against which to measure progress
• Method(s) to measure progress
• Forecast of future performance
Project Performance Reporting - v1 - 01Mar16 7
Content of PPR
• Based on project constraints (cost, time,
performance, risk, resources) and other factors such
as customer performance
• Standard report format / template essential
Project Performance Reporting - v1 - 01Mar16 8
Cadence
• Important to ensure cadence is maintained for reporting
periods (e.g. monthly)
• Need owner to ensure cadence is maintained
• Reports should be based on common baselines (e.g.
cost, schedule) to ensure coherent picture is presented
• Be aware of currency of data / changes to baselines as
progress is reported through the reporting hierarchy
• Focus should be on adding value / generating
information, not ‘processing data’
• Dependent on key stakeholders (e.g. PMs, Functions) to
provide source data – requires extensive stakeholder /
relationship management
Project Performance Reporting - v1 - 01Mar16 9
Reporting Hierarchy
LEVEL
1
LEVEL 2
LEVEL 3
LEVEL 4
LEVEL 5
L O W
MED
HIGH
Portfolio Status Reporting
Customers: Executive Mgmnt & Sponsors
Programme Status Reporting
Customers: Programme Mgr, Key Senior
Stakeholders
Project Status Reporting
Customers: Project Mgr, Project Team, Key
Stakeholders
Functional Intermediate Reporting
Customers: Functional Mgrs, Project
Team Leads
Working Level Reporting
Customers: Supervisors, Team
Members
LEVEL OF DETAIL
Project Performance Reporting - v1 - 01Mar16 10
Toolsets
• Reduce level of ‘manual data manipulation’ by
automating report generation
• Generate ‘glue ware’ (using e.g. Visual Basic, Excel
Macros) to integrate disparate toolsets
• Use shared data repositories to reduce duplication
of ‘data pots’ around the business – single
database with ability to generate ‘views’ of
relevant information
Project Performance Reporting - v1 - 01Mar16 11
Project Overview
Project Performance Reporting - v1 - 01Mar16 12
Changes to Baseline
Project Performance Reporting - v1 - 01Mar16 13
Project Roadmap
Project Performance Reporting - v1 - 01Mar16 14
-30 / 30 / 60
Project Performance Reporting - v1 - 01Mar16 15
Milestones
Project Performance Reporting - v1 - 01Mar16 16
Risks
Project Performance Reporting - v1 - 01Mar16 17
Issues / Actions
Project Performance Reporting - v1 - 01Mar16 18
Spend
Project Performance Reporting - v1 - 01Mar16 19
EV
Project Performance Reporting - v1 - 01Mar16 20
EV
No concerns regarding meeting
forecast ‘Go Live’ date
Looking at opportunities to
recover potential cost increase
(due to rework as a result of loss
of development environments)
Project Performance Reporting - v1 - 01Mar16 21
Resources
Project Performance Reporting - v1 - 01Mar16 22
Summary Status
• Amber or Green Project?
• Subjective or Objective status?
Project Performance Reporting - v1 - 01Mar16 23
Lessons to Share
Presenting:
• Communication primarily one way – be sure of
information presented
• Keep it simple
• No surprises
• Chair the meeting – avoid going down rabbit holes
• Be careful about use of traffic light status (objective
/ subjective status)
• Recycle slides (appending as necessary) as you go
up the reporting chain
Project Performance Reporting - v1 - 01Mar16 24
Lessons to Share
Performance:
• Don’t dwell in the past, focus on forecasting future
performance and risks / issues that would prevent
project success
• Analyse trend information to help forecast future
performance
• Integrated toolsets helps realise efficiencies and
data integrity when generating reporting artefacts
• Don’t just generate information, spend quality time
analysing the information
Project Performance Reporting - v1 - 01Mar16 25
Lessons to Share
Governance:
• Maintain the cadence of the monthly (e.g.) reporting cycle
• Use reporting templates
• Don’t tolerate deviations from standard templates unless approved
• Need governance to maintain standards
Personal Development:
• Ensure those involved in generating information fo reporting understand who reviews it and how they use it to make decisions
Questions?
26