Darren KosaPlanning & Controls ContractorHampshire, United Kingdom
Hi,
I'm currently developing a project assessment tool that focuses on enhancing the robustness/validity of our project schedules and one of the KPIs we're looking at is float/slack.
We'd like to know after running the assessment tool, how many tasks/milestones in the project schedule have a total float value that is greater than 20% of the remaining project duration and also how many have a total float value of 15 days or less. We then plan to grade the returns using a traffic light system.
As an example. If a project had 100 days remaining until product delivery and 30% of the remaining tasks had total float/slack of more than 20 days, would that be good, bad or indifferent? Conversely if 30% or remaining tasks had total float/slack of less than 15 days, would our risk exposure be deemed to be high?
Are there accepted data points which we could then use as a RAG status to determine whether the project schedule would need reviewing as a result of the KPIs we are trying to track?
