How do you measure Project On-Time Delivery?

Sara B · ‎02-17-2022

How do you measure whether a project met the planned go-live date and was delivered on time?

We have configured the system with an additional go-live date field and a check box for "delivered to customer" to support this measurement. However, we would like to be able to factor in approved Project Change Requests records or potential re-baselining into the metric, but have not found a way to do that (without manual analysis).

If you are not measuring on-time project delivery, what other metrics/KPIs do you use to monitor the project portfolio?

-Sara

juan9 · ‎02-17-2022

I need some more examples:

You can measure by looking at different states, and maybe adding time stamps per state.

You can also do an approval, or some attestation on the go-live date to.

You can also have the system check a set of conditions on the go-live date, then depending on that logic, it can determine if it was delivered or not.

For example, at the end of our projects, we always do a write-off, so the system should be able to recognize that the project was completed based on some set of parameters.

The first question I ever answered here:)

View solution in original post

juan9 · ‎02-19-2022

Hi Sarab,

How strict are others in defining or considering valid project changes, which impact the schedule, when measuring On-Time Delivery? :: This completely depends on how the organization handles these changes.

From my previous implementation, project changes happen more often than they should lol. So these issues should be accounted for in the architecture of the software

Dhiren Aghera · ‎02-21-2022

How strict you need to be depends solely on the organizations maturity and processes. As per PMBoK any change in the triple constraints (time, cost and scope) results in a CR.