Ask Derek - Required Experience to take the PMP

I'm always looking for ways to help others in their quests to be better project managers.  It doesn't matter if it's about getting the PMP® certification, getting PDUs, or even finding good tools to make a given task easier.  I field questions from both emails and Twitter.  Today I read an email that was not unlike others I've answered directly.  But, I thought others would benefit if I answered publicly.  Here is the content of the email:

I read your article about how the PMP certification is commercialized and an example of a PMP holder hiding behind the credential.  I want to become a good IT Project Manager.  I read the requirements to become a PMP. According to requirements, a person needs 3 years exp before attempting this test. My question is, how can I get exp without a certificate or who would give me a job to get the exp as a project manager and thereby attempt my PMP certification.  Can you please help me set my goals in an orderly fashion so I can ultimately become a good Manager?

Does this sound familiar? It's kind of like the chicken and the egg.  First, I would like to say the person asking the question made a statement that resonated with me.  I want to become a good IT Project Manager. I really want to help because if they wrote that, they are half way there.  Let's be clear.  You don't need to have a PMP to be a good PM. I know very gifted people who do not possess the credential.  I would be a liar if I did not believe the deck is stacked against them.  Companies have bought into the idea that good PMs have PMPs.  But I digress.  Back to the question at hand.

It can be a challenge to become a project manager, if you have no experience.  If you have ever lead a team or managed a task, you have more experience than you give yourself credit for.  PMI will recognize that.  Remember, the PMP is not a test about something you are learning.  The PMP is an exam about what you should already know and do, but categorized within the framework of the PMBOK.  Let's say you're a QA Engineer.  I bet you have a lot of experience in the Monitoring & Controlling Process Group and specifically in the Project Quality Management knowledge area.  Document your experience around what you know and do.

In order to qualify to take the PMP exam, you do need to have experience in all 5 Process Groups (Initiating, Planning, Executing, Monitoring & Controlling, and Closing).  Honestly, you could have 99.9% of your experience in one process group and 1 hour in each of the remaining 4.  PMI doesn't care.  You just need to document that you have experience in all.  If you want to be a good PM, I would recommend you get exposure to each of the progress groups. Fewer things are as bad as a PM who does not empathize with all of the functional areas or have experience in the different phases of the project lifecycle.

On a practical note, I recommend you engage others in other functional areas of your current project(s).  Offer to help them in some way.  Don't go in with an ulterior motive.  Honestly, help someone and you'll get the experience you need as a byproduct.  The PMP should be for someone with overall experience. However, I do know managers in specific functional areas who also hold the credential.  I would recommend, if you want to be a good manager, to become educated through practical experiences and not solely through academia.  You can learn just so much from a book.

Did I answer the question?  Is it a good start?

Please post some comments and let me know.

How Do You Know Your Metrics Are Worth It

GQM Paradigm

So you want to create some metrics.  More importantly, someone has told you that you need to create some metrics.  How do you know if you're just making work for yourself or if you're just putting a spin on the same old data?

Ask yourself what the goals of your project are.

In trying to determine what to measure in order to achieve those goals, I recommend using a Goal-Question-Metric (GQM) paradigm. It can actually be applied to all life-cycle products, processes, and resources. I've been using this process for a few years and it really helps me creat a quality metric.  The GQM paradigm is based on the theory that all measurement should be [1]goal-oriented i.e., there has to be some rationale and need for collecting measurements, rather than collecting for the sake of collecting. Each metric collected is stated in terms of the major goals of the project or program. [2]Questions are then derived from the goals and help to refine, articulate, and determine if the goals can be achieved. [3]The metrics or measurements that are collected are then used to answer the questions in a quantifiable manner.

Here is an example of the GQM in action:

Goal (use this 4-step process to shape a goal)

[1] Purpose [2] Issue [3] Object (process) [4] Viewpoint

Goal 1

[1] Purpose [2] Issue [3] Object (process) [4] Viewpoint

Maintain a maximum level of customer satisfaction from the Help Desk user’s viewpoint

Question 1

What is the current help desk ticket trend?

Metrics 1 Metrics 2 Metrics 3 Metrics 4

Number of help desk tickets closed Number of new help desk tickets % tickets outside of the upper limit

Subjective rating of customer satisfaction

Metrics 5

Number of new help desk tickets open

Question 2

Is the help desk satisfaction improving or diminishing?

Metrics 6 Metrics 7 Metrics 8 Metrics 9

Number of help desk calls abandoned Number of help desk calls answered Number of help desk calls sent to voicemail

Subjective rating of customer satisfaction

As the great Lord Kelvin once said, "If you can not measure it, you can not improve it."

Image based on Basili, Caldiera, and Rombach "The Goal Question Metric Approach", 1990