This information is retrieved from Project Details and week logs for all running projects.
Planned is defined in Project details:
- Project – Name of the project
- Budget – Total working hours
- Project length – Total project length (number of week between Start date and Close date)
- Decided finish date – Close date
- Speed – Speed forecast calculated as Total working hours / (Total project length * Length of working week * 80%) where length of working week is defined in Pulse room details.
Actual is retrieved from the project’s week log:
- Completed sub-results – calculated as Completed sub-results / number of sub-results where the Number of Sub-results is defined in Project details. If the calculated finish date is later than decided finish date + 1 week, the value is displayed in red.
- Calculated finish date – Trend based on the number of Completed sub-results reported in the week log. If the calculated finish date is later than decided finish date + 1 week, the value is displayed in red.
- Resources – Number of Full-time resources + 0.5 * number of Part-time resources reported in the week log for this week. This is the actual number of resources (FTE) that are currently allocated to the project. Speed specifies the planned number of resources on average throughout the project.
Total Full-Time Equivalents [FTE] for projects
The total number of available people translated into FTE.
This value is defined in Pulse Room Details. The number of FTEs should be the number available for working in projects only. Of the total resource pool, a certain proportion should be set aside for work on assignments; these should not be included here.
Planned FTE in project portfolio
The sum of Speed forecast in ongoing projects, measured in FTE. Note that the need for resources varies over time in the projects; this figure is an average for all projects.
This value is based on Total working hours, Start date and Close date in Project details.
From Start and Close date, the Total project length in weeks is calculated.
For each project the App calculates:
Speed forecast = Total working hours / (Total project length * Length of working week * 80%), where Length of working week is defined in Pulse room detail.
For the whole portfolio: Planned FTE in project portfolio = Σ Speed forecast for all running projects
The difference between Total FTE and Planned FTE. The figure will show if your project portfolio is balanced in respect of resources.
Overloaded/Underloaded = Planned FTE in project portfolio – Total FTE for projects
Allocated FTE in projects this week
Is based on what the projects have reported in their week log (Full-time resources and Part-time resources). One part-time resource
is set to half (0.5) one full-time resource.
For the whole portfolio:
Allocated FTE in projects this week = Σ Full-time resources + 0.5* Part-time resources for all running projects
This value is the difference between Total FTE and Allocated FTE. The figure will show your actual resource balance for the project portfolio.
Overloaded/Underloaded = Allocated FTE in projects this week – Total FTE for projects
Planned completion rate
The average number of sub-results that the ongoing projects need to complete each week to reach their end date.
Is based on definition in Project Details of Number of subresults and Total project length (Close date – Start date).
Planned completion rate is the total number of sub-results that on average must be completed per week as for all ongoing projects.
Planned completion rate = Σ Number of sub-results / Total project length for all running projects
Actual completed sub-results this week
Total number of completed sub-results this week from the projects’ week logs minus completed sub-results last week.
Over time, this figure must be in line with planned completion rate.
Actual completed sub-results this week = Σ Completed sub-results (this week) – Completed sub-results (last week) for all running projects
Project portfolio turn-over (12 months)
Calculated as the total number of sub-results in closed projects, divided by the average number of completed subresults in projects during the last 12 months. Will show how often the project portfolio is renewed.
The figure corresponds to stock turnover rate.
If the projects on average are completed in 6 months, the project portfolio turnover is 2.0. The project portfolio is thus replaced twice a year.
Project portfolio turn-over = Σ Number of sub-results in closed projects / Average number of Completed sub-results in running projects
Delivery precision [%] (12 months)
Percentage of projects that have been completed on planned completion date + 1 week during the last 12 months.
Closing lead time [week] (12 months)
The average time it takes from when all the sub-results have been completed (they are reported green in the week log) until the project is Closed.