Project Management

7 Guidelines for Meaningful Project Performance Management

From the pmStudent Blog
by
Ranting and raving about project management and systems engineering.

About this Blog

RSS

Recent Posts

The Problem with Project Management

The Problem with Project Management

The Problem with Project Management

LinkedIn Recommendations Are Easy

The Catch-22 of Project Management Certification and Experience

Categories

Agile, Career Development, Certification, Change Management, Communications Management, Cost Management, Documentation, Earned Value Management, Education, Integration and Test, Kanban, Leadership, Lean, Lessons Learned, Methodology, Misc, Multitasking, New Project, Operations, Planning, PMP, Productivity, Professional Development, Project Estimation, Project Leadership, Quality, Requirements Management, Risk Management, Schedule Management, Scope Management, Software, Systems Thinking, Tools, Video, Work Breakdown Structures (WBS)

Date

linkedin twitter facebook Request to reuse this  

Categories: Productivity


Project Performance ManagementI've been asked about this recently, and thinking about it on my own too for my own teams.  Here are some guidelines I suggest for myself and others to evaluate existing cultures and create new  project performance measurement processes that are meaningful and do what you want them to do.

1.  What Adds Value?

Measure only what gives a true picture of performance and adds value.  What impacts the bottom line?  Are you REALLY going to use the data you are gathering?  If not, why are you gathering it?

2. Don't Measure Everything

Project managers can be a controlling bunch.  Many of us want to measure EVERYTHING.  In my experience, there are probably around 3 things you want to measure some aspect of.  Not much more, and not much less.  This has held true for me across multiple industries and some examples from my past include a) cycle time/velocity b) customer/stakeholder satisfaction and c) on-time delivery.

3.  Stay Out of the Weeds

I've seen detailed gathering of performance metrics you wouldn't believe.  Be very aware of the balance between level of detail and the effort/morale of the team to report the detail.  If people start asking for a new charge code to account for the time they are spending accounting for their time, you've gone too far!

4.  Consistency

Be consistent.  "Flavor of the month" means gaming the system, not a focus on performance.  Whatever your objectives are, they had better have a life span of more than a month or a quarter.

5.  Beware of Gaming

Beware of gaming the system.   If possible measurements should be so transparent that gaming is not possible.  Self-report data is prone to this, even unintentionally and subconsciously.  This is why objective measures like physical percent complete and cost/schedule performance data from an external group is so important.

6.  Focus on Methods

Don't use metrics for an incentive program of any kind.  For instance, don't penalize people in any way for their estimates being wrong.  If you want to get better at doing estimates, great.  Focus on methodology, not who was close or not close on their estimates.  Use the results as an indicator for what is working and what needs improvement.

7.  Eliminate Internal Competition

If your performance management system is generating competition between individuals or teams, you're doing it wrong.  In the call center world you see this all the time with "contests" that pit teams or sites against each other.  These result in animosity towards competetors and incent a decrease in quality in favor of whatever the "flavor of the month" stat is you are touting in the contest.  They usually create the appearance of performance.

"Hey, what do you know?  We made call handle time a key metric in this contest, and our average call handle time went down!  Yippie!"  (You're doing it wrong)

Customers, teams, and organizations lose.


Posted on: October 06, 2010 08:49 PM | Permalink

Comments (9)

Please login or join to subscribe to this item
mande
great article, wow my mind. Any more detailed in aplication or daily operational with example per each point will be very valuable.
regards,

avatar
Josh Nankivel Engineering Project Manager| Apple Sioux Falls, Sd, United States
Thanks!


You are right, more depth on this topic would be good. I will put it on my list of potential topics to write or create videos about going forward.


Thanks for commenting!


-Josh, learn.pmStudent.com



clock
I agree with Mande. Great article, but examples of how to avoid the pitfalls in #7 would be helpful.

avatar
Josh Nankivel Engineering Project Manager| Apple Sioux Falls, Sd, United States
Thanks Lenworth. I'd love to share my thoughts on that topic, it sounds like you might have an idea for a case study I could use as a basis for diving a bit deeper. (no real specifics, but a general situation)

If so, please let me know http://pmstudent.com/contact/

-Josh

avatar
Indrek Kuldkepp CEO| Ganttic LLC Rahinge, Estonia
I like "Stay out of the weeds" part. Has strong point in it.

avatar
Josh Nankivel Engineering Project Manager| Apple Sioux Falls, Sd, United States
Thanks Indrek! We have to keep reminding ourselves, just because something is quantitative and detailed doesn't mean it's necessarily adding value!


-Josh

avatar
Doug Fitzgerald Mawson, Act, Australia
Some nice thoughts. I sponsor several projects in my organization, and I have them report four major issues: will the product be fit for purpose, delivered within the schedule tolerances and within budget. The last thing I want to know is that my organization is not holding the project up by not providing something the project team needs to progress. All green - keep talking, but only to ensure there's not something brewing. Amber - starts the discussion about whats going on and how it might be fixed. Red - time to get down to what remediation will be done, when, when will it change the situation.

avatar
Josh Nankivel Engineering Project Manager| Apple Sioux Falls, Sd, United States
Nice Doug, I like it!


Thanks for the great comment!


learn.pmStudent.com

avatar
Ann Satar Lawrence Township, Nj, United States
Can you elaborate on the on time delivery as a metric and cycle time next? Maybe I just need an example. I understand OTD is about delivery per schedule. If you have risks activated that impact schedule then there should be new OTD, or not? Cycle time measured from the activity based task? If the task takes longer or shorter, then the metric is greater than or equal to 1, right?

Please Login/Register to leave a comment.

ADVERTISEMENTS

"I must say that I find television very educational. The minute somebody turns it on, I go to the library and read a book."

- Groucho Marx

ADVERTISEMENT

Sponsors