There are our Project Governance processes to address how do we capture project KPIs, what/when do we escalate and how do we escalate.
At H&D we have a number of Project processes to ensure project quality and that we are hitting project KPIs to maximise delvery and margins.
However, if we don't have governance across these items they can fall by the wayside and quality controls can be missed resulting in poor delivery and the missing of our KPIs.
Project Resourcing
Key Considerations
- Has it been resourced / has resource been allocated
- Is resource bunched / over allocated
Measures (by Active project)
- Maximum of 15 points per user per sprint allocated
- Tasks with no real users assigned
Project Overruns
Measures (by Active project)
- Forecast Points: Actual Number + % (Budget Points Spent - Actual Points Spent)
- # Days Forecast of Launch vs. Original Plan
Project Closures
- # of Projects Open per PM
- # of Projects not closed 30d after key launch date
- Ultimate outcome/quality of project
Considerations
- Archive a project on closure to reduce the risk of individuals continuing to capture tasks against them
- All work on an account post project closure should go to Support/Success and be captured outside of the project
Project Progress Reports
Measures (by Active project)
- Last Progress Report Date Sent
- # of Progress Reports Sent
- Number of Weeks project has been running
- Deficit of Progress Reports - should exclude 1 week for kick-off + 4w post launch
- Note: Checking through the reports on Wednesday to check that there is nothing off and if there is troubleshooting and getting them fixed before progress reports on Thursday.
Project Changes
- # of Changes Raised by Status
- # of Changes in a To Do status that are more than 1 week old
Project Risks
- # of Risks Raised by Status
- # of Risks in a To Do status that are more than 1 week old
- # of Active Red Risks
How we Report
- Forecast per user per sprint
- # Active Projects per PM
- Active Projects
- Project Kick-off Date
- Sum total points allocated with no real users
- Forecast Points #
- Forecast Points %
- Original Launch Date
- Forecast Launch Date
- Forecast Launch Days (number of days from the original forecast date)
- Last Progress Report Date Sent
- # of Progress Reports Sent
- Number of Weeks project has been running
- Deficit of Progress Reports
- # of Changes Raised by Status
- # of Changes in a To Do status that are more than 1 week old
- # of Risks Raised by Status
- # of Risks in a To Do status that are more than 1 week old
- # of Active Red Risks
What do we Escalate
- Sum Total points with no real users is over 20 points and project kick-off date is over 2 weeks ago
- Forecast Points # is over 15
- Forecat Launch Days is over 10
- Last Progress Report Date sent is over 10 days
- Deficit of Progress Reports is over 3
- # of Changes in a To Do status that are more than 2 weeks old is more than or equal to 1
- # of Risks in a To Do status that are more than 2 weeks old is more than or equal to 1
- # of Active Red Risks is more than 1
How we Escalate
- Weekly report sent via Email on Mondays if any of the above escalations are met
- Included in Tuesday SLT report
- Reviewed in Weekly PM Session
- Reviewed in Monthly PM 1-on-1s