Project Management

5 Common Approaches for Performance Measurement

From the The Money Files Blog
by
A blog that looks at all aspects of project and program finances from budgets, estimating and accounting to getting a pay rise and managing contracts. Written by Elizabeth Harrin from GirlsGuideToPM.com.

About this Blog

RSS

Recent Posts

3 Tips for when your to do list is full of important things

Managing data maturity risks

What does commercial viability mean?

Building resilience into project delivery

Lessons about project metrics



How do you track the performance of your project? Here are 5 ways that you can do it.

1. Fixed Formula

This is pretty easy. Assign a fixed percentage when the work starts. Then make it up to 100% by allocating the rest when the task finishes.

The Pareto principle is a good one to use if you don’t know how to split your task percentages. Assign 20% complete to the job when it starts, and the remaining 80% when your team member reports the work complete (because at that point it’s 100% complete).

It’s simple to work out but it’s not terribly accurate. It’s only good for small pieces of work and short tasks where it would be too difficult or not worth it to work out percent complete across a couple of days. It can also be used where the task is no longer than a week long. If you are updating your project plan once a week, and the task is no longer than a week long, the task is either started or finished so the 20/80 split (or 50/50 or whatever you think is appropriate) works out pretty well.

2. Weighted Milestones

When you’ve got plenty of milestones along the way, you can work out project performance by tracking how many you’ve hit.

In other words, you can pre-assign progress (percent complete) to certain milestones or parts of tasks. When you hit Milestone 1 you can say the project is 15% complete, at Milestone 2 it goes up to 20%, at Milestone 3 you’re 65% complete and so on. Until your final milestone at project completion where your project (or task) gets updated to be 100% complete.

This is also a way to split payments to vendors – many contracts have a schedule of payments linked to the achievement of key milestones. Your budget could be weighted in the same way as how you track performance.

3. Percentage Complete

We’ve talked about % complete already, but this version of it is just based on the project manager’s guess best professional judgement. They update the schedule or tracker weekly (or whenever it’s appropriate) with their take on project performance by assigning a percent complete.

This isn’t hugely accurate either – although it depends on the project manager. It takes experience to be able to pick a percentage out of the air and have it reflect reality. Generally, project management tools can help with this by playing back to you the % complete of your project schedule, so at least in that case you should have something underpinning the number you give.

4. Percentage Complete with Gates

This is similar to weighted milestones but instead of waiting to hit the ‘gate’ point, you can report any percentage complete up to the approved limit for that milestone.

For example, when you hit Milestone 1 you can say the project is 15% complete, as we saw above. With weighted milestones, until that point the project would be 0% complete. With gates, you can set a % complete every day if you like, working up to 15% at the point of hitting the gate (the target milestone date or achievement).

It’s like a blend of using your professional judgement but being constrained to not say you are too far ahead because you can only ever hit a certain percent complete through the nature of where you are on the project.

It sounds complicated to explain but this is my favourite approach for measuring project performance.

5. Level of Effort

Finally, you can track effort against the elapsed time. Alternatively, you can track against some other task or work package on the plan. For example, ‘Complete Testing Documentation’ might be linked to ‘Complete Testing’ and the two activities progress in parallel.

You’d track performance for ‘Complete Testing’ and then, as you know that testing documents are being updated as you go, apply the same % complete to ‘Complete Testing Documentation.’

Which one(s) of these do you use? And which do you avoid? Do you use these as standalone techniques or do they link to your Earned Value Management activities? Let us know in the comments below!

Posted on: April 23, 2017 11:59 PM | Permalink

Comments (10)

Please login or join to subscribe to this item
Great Elizabeth.

I have using percentage complete, relying on my team for stating their 'best guess percentage', but I also use the 'on-track' feature if the team also confirms the task(s) are on-track per the given estimates.

I like the other options too. All depends on expectations and the project. I could see using different types on different types of projects. We currently have a couple under different PM's that I think would do well with 'Percentage complete with gates'.

Very helpful to document the various methods for us. I usually apply my educated guesses to % complete, so it's good to know that I'm not committing a big project management faux-pas by doing so. I liked the "Percentage Complete with Gates" method, so I'll use that going forward.

Very nice summary. Thank you.

As a project progresses it is pretty common to see weighted milestones for deliverables (documents, drawings, etc...) and then once in the construction phase moving to level of effort as most tasks have been estimated against norms.

Nice summary of the different types that can be used.

Extremely helpful. Thank you, Elizabeth.

Depending on project & team members hired by company.

Depending on project & team members hired by company.

Please Login/Register to leave a comment.

ADVERTISEMENTS

A low voter turnout is an indication of fewer people going to the polls.

- Dan Quayle

ADVERTISEMENT

Sponsors