Lawfulgood PMP Level 5

After reading a blog post by Dennis Stevens, I suddenly realized one of things about the family of PMI certifications that has been bothering me.  The family of credentials does not lend itself to the Dreyfus Model.  Dennis offered really compelling arguments about what does certification imply, about people who can’t or won’t earn certifications, and what he calls tilting at windmills. The Dreyfus Skill Acquisition Model, which Dennis references, identifies five stages of competence:

Novice: Rigid adherence to taught rules or plans.  No exercise of discretionary judgment.

Advanced beginner: Limited situational perception. All aspects of work treated separately with equal importance.

Competent: Coping with crowdedness (multiple activities, accumulation of information). Some perception of actions in relation to goals. Deliberate planning. Formulates routines.

Proficient: Holistic view of situation. Prioritizes importance of aspects.  Perceives deviations from the normal pattern. Employs maxims for guidance, with meanings that adapt to the situation at hand.

Expert: Transcends reliance on rules, guidelines, and maxims. Intuitive grasp of situations based on deep, tacit understanding. Has vision of what is possible. Uses analytical approaches in new situations or in case of problems.


PMI currently has 5 certifications.  You don't need to be an active PMI member (currently at 318,421) to hold one of these certification.  To get one of these credentials, you need to meet some educational and experience requirements and then pass a written exam.  Only the Program Management Professional requires a panel review.

Certification Total Active
Project Management Professional (PMP) 389,726
Certified Associate Project Manager (CAPM) 11,785
PMI Risk Management Professional (PMI-RPM) 393
PMI Scheduling Professional (PMI-SP) 327
Program Management Professional (PgMP) 436

What is missing here is some continuity between the credentials and something that indicates the level of expertise.  There is a difference between a PMP who met the minimum experience requirements and one who has been practicing in the profession for 20 years.  Would calling someone a Lawfulgood PMP level 5 with a 20 wisdom and 30 charisma help?  I'm not proposing we pull credential titles form Dungeon and Dragons, but rather something that will give the laymen an idea of experience.

Do I have an example?  I absolutely do!  Check out the International Consortium of Agile (ICAgile).  They are proposing a 3-phased, skill-based, certification.  If PMI borrowed from this model, the CAPM would be part of phase 1 (Associate), RPM, SP, and PMP would be part of phase 2 (Professional), and PgMP would be phase 3 (Expert).  PMI wouldn't necessarily have to mimic this framework exactly, but do you see how it puts it all into context?  If there would be a mighty uproar by the PMP community, suddenly being demoted to associate level, you could identify them as a PMP-1 or PMP-2, depending on which knowledge area(s) they have been certified in.

Any thoughts or comments?

Looking for clouds in a silver lining

For all of the haters and nay-sayers out there in the world, not every silver lining has to have a cloud. Regardless of what you say, I will continue to have a blind optimism of the world.  I will do what I can, with the time and budget I have.

Here's a quote for you.  I don't plan on doing this every day.  So, just enjoy it and shut up.

“Around here, however, we don’t look backwards for very long. We keep moving forward, opening up new doors and doing new things… and curiosity keeps leading us down new paths.”

–Walt Disney

Graphic: Frog Design

A PMI Dog Pile

Upon reading a piece featured on PM Hut, Certifications Don’t Make Project Managers, I was compelled to comment...twice.  So, what's the short story? I've been reading more and more articles from people who seem to be down right hostile toward the Project Management Institute (PMI). Richard Morreale, the author of the article, wrote

The Project Management Institute (PMI) and the Association of Project Management Group (APMG) are two of the biggest reasons that projects fail.

Dr. PDG added

In short, IMPO, PMI and to a lesser degree, APM and APMG have become nothing more than the AMWAY or Mary Kay Cosmetics of the project management world

Here's the long story.  I enjoyed the article, to include the comments from the likes of Robert Kelly, PMP and Dennis Stevens (fellows I admire).  I'll admit, I've been getting a little incensed recently after hearing stories of people who appeared to have gamed the system and got certification with no real education or experience other than a PMP boot camp.  But, most of this is hearsay.  I have been approached by people, asking for my help, who want the certification for no other reason than to bolster a résumé.  I do believe these cases are extremes and hopefully isolated incidents.

Based on your motivations and character, the outcomes of getting your certification can be completely different.  I got my certification because, at the time, I thought it was the only way I would be taken seriously.  I was dealing with a stakeholder who was being completely unreasonable.  She had a PMP and ignored everything outlined in the PMBOK.  Clearly, she had her own agenda.  Mine was a quest for knowledge in my profession and to hone my skills as a project manager.  This quest has exposed me to several different approaches, to include Scrum and Kanban.  I think I am a better project manager than I was several years ago because I am receptive to new ideas and approaches and don't necessarily walk around preaching one as PM dogma.

So, where am I going with this?  I think if your mind is open to it, you can learn a lot from preparing for the PMP exam.  I also think you can learn a lot from taking a level 400 class in Project Management at a University.  But, you have to be motivated by the desire to learn and satisfy your customer's wants and needs.  Don't think a certification will get you that dream job or make you a PM expert.  It will come back and bite you.  Sometimes being a PM means working on a project with specific knowledge area focus.  But sometimes you will be exposed to full lifecyle management, dealing with every process group.  Either way, it's not all textbook.

I think Dennis Stevens put it very well in his comment:

a PMP is like a recent college grad, a medical resident, or a 16-year old who just got their license. They have some situational awareness from having participated in projects, have been educated in the fundamentals and share a common language. But they are not prepared to be CEO of a business, an emergency room surgeon, or a cross country truck driver.

Some will argue that guns don't kill people, people kill people.  Just the same, PMI and APMG don't cause projects to fail.  Sometimes it's the PM, sometime it's the customer, and sometimes it's something that wasn't on your risk register and should have.  The noble thing to do is to try to fix the problem.  Mentor an associate PM.  Give a talk on your area of expertise.  Tell people how you failed on a project so they don't make the same mistake.  I think if we all put forth a little more effort, in helping each other become better project managers and leaders, the results could be transformative.

 

On the eve of a new phase

On this last day before our son starts his first day of public education, I look back and realize 5 years have passed in a blink of an eye. Project management can be a challenging profession but nothing can compare to being a parent. Sure, I feel guilt if I screw something up on a project, but in the end it's just money. What if we screw up our kids!? Because my wife and I figured family was more important than work (and money), my wife put her career on hold to ensure our son got the attention and nurturing he deserved. Our perspective and optimism of the future is represented in an awesome video created for the AARP U@50 video contest. You may have seen it before. It's worth the 2 minutes.

If anyone is looking for a technical writer, armed with a masters degree and years of experience, my wife may consider some part-time work. One thing is for certain, you know she has her priorities straight.

An evening in the ER

You sometimes forget how fragile life can be, until you find yourself sitting in a hospital emergency room. A few days ago, our son celebrated his 5th birthday.  My wife threw him two parties; one was with his friends and the other was with family.  We believe our adventure began at the first party.  Though the party was private, it was in a public place around lots of other people.  Within 48 hours of the first party, our son was lethargic and complaining of a headache.  He complained of being cold but was running a fever.  Next thing ya know, he was tossing his little cookies.  That's when his experience ended and my wife's began.  My wife then complained of a headache and waves of hot and cold.  The headache got worse...and worse...and worse.  Since she has a history of migraines, she took medication with the hope it would stop it.  Then she got sick to her stomach, just like our son.  Unlike our son, she didn't get better.

Sunday night into Monday morning was rough.  She didn't sleep due to the "migraine".  I stayed home from the office so I could take care of our son.  Monday night turned into Tuesday and still the migraine got worse.  But this wasn't a normal migraine and the medication wasn't stopping it.  She called her doctor and waited.  After a few hours, and her doctor not returning her urgent call, she had enough.  It was time to go to the Emergency Room.  We called a family friend, who picked up our son, and we were on our way to the next phase of our adventure.

When I think of the ER, I have thoughts of sitting in a waiting room for 6 hours with people bleeding profusely from their heads or coughing like they have tuberculosis.  We made our way to Frederick Memorial Hospital (FMH).  I have to say, I was pleasantly surprised by the service we received.  I could include a few project management analogies in here but I'll try to stick to the story.  It took about 5 minutes to check in.  (symptoms, medications currently taking, age...)  We sat in the relatively empty waiting room for about about 20 minutes before they took us to triage.  Before being called, we saw them call the oldest and the youngest in the room and someone they flew in by helicopter.  It was interesting to see the prioritized patients moving in and out of the waiting room.  While in triage, they asked a few more questions and slapped and armband on her wrist.  A nurse appeared and told us we were being taken to "Fast Track".  She escorted us through a few doors to an area I would describe as a medical cube farm.

Within an hour, she had been seen by a nurse.  30 minutes later, a physician's assistant came.  30 minutes later, my Vicodin drugged wife and I were leaving the hospital.  So, what was causing my wife this excruciating pain?  The staff believe she was exposed to a virus that has been going around.  Instead of just making her sick, it infected a cranial nerve.  The nerve was swelling, causing the pain.

I'm still a little pissed that her doctor didn't call her back until today.  Thanks for nothing!  I would give the hospital a pretty good rating on a few things.  They definitely managed client expectations.  I literally expected a 6 hour wait.  We were in and out in less than 3 hours.  They had free WiFi.  What can I say, I like my WiFi.  It helped pass the time.  They kept us informed of what was going to happen next.  I think communications is key to keeping the costumer happy.  The last part was someone from FMH contacted me via Twitter to check up on us.  Now that is a savvy hospital!

Thank you to all those on Twitter and elsewhere who saw my initial Gowalla post.  It was very nice to receive your supportive tweets.

See you all online!

Derek

Judging PMI Unfairly

new_pmps

Recently, I've been a bit vocal about my concerns of the volume of people getting the  Project Management Professional (PMP®) certification.  I often ask if quality is being sacrificed in order to certify more people.  Don't get me wrong, if being a PMP means you are a "quality" project manager, I think the more the merrier.  But, what if more PMPs means the Project Management Institute (PMI) doesn't have the necessary people to conduct proper audits?  I decided this question warranted a telephone call to PMI.  Though they would not give specific numbers, they stated

The number of audits have remained consistent over the last few years

Ah-ha!  Just the incriminating statement I was expecting, to support my theory!  Clearly the increased rate of people getting certified would mean a lower percentage were being audited.  Since numbers don't lie, I went back as far as I could and compiled the monthly PMP certification rate.  September 2006 was the earliest (easily accessible) date I could find.

Once I charted all of the data to date (June 2010), I was left scratching my head.  With the exception of June and July of 2009, the rate has been relatively consistent.

Average certifications per month (2006-2010): 4,401

Average certifications per month (2010): 4,350

Highest certification rate (June 2009): 13,920

Lowest certification rate (July 2009): 689

In reality, the average number of people getting the PMP certification is down in 2010.

Have I judged PMI unfairly?  Is the quality of the certification the same as it ever was?

Building on failure and action versus motion

I just listened to the 37signals podcast.  It was a playback of some of the brainstorming sessions leading up to the release of the book REWORK.  For those who don't know me, I'm a complete 37signals fanboy.  They just "get it".  I don't know if it's their no BS approach to business or that they have great products.  But, I've found many of the things they created, do, and say helpful in multiple areas.  It doesn't matter if you're an entrepreneur or a project manager.  They have something for everyone. There were two things from the book I wanted to note today.  First, they talked about building on failure versus building on success.  My takeaway is if you want to reach a goal (insert your project or product here), it is easier for you to build upon small successes than to fail and start over. Example: When you're [creating] an [product] for a customer, wouldn't you rather deliver small chucks and get acceptance from the customer along the way, rather than offer a big reveal at the end and risk delivering something they don't want?  If you fail, you have to start all over.  Out of a million possibilities, you've narrowed it down by ONE.  I agree with the PDCA approach (Deming cycle). You should refine, deliver, refine, deliver.  Don't forget to deliver.  If you get something 99% done, you still have nothing.  Deliver something (regardless how small), get acceptance, and repeat.

The Second thing I wanted to note from the podcast was the mention of an Ernest Hemingway quote

Never mistake motion for action

Things don't have to be hard.  If your business [process] requires you to do wasteful (time or money) things, don't do them!  You should be doing things because they provide value (save time/money or make money).  The rest is just fat and you need to trim the fat from every business [process].  Make your [processes or products] as lean as you can without hitting the bone.  Only then can you have a good baseline.  Only then can you build on top of something.  Anything beyond that and you may be wasting time and money compensating.

Do something because you need to do it.  Don't do it because you feel obligated.  Do you need to go to that next meeting because there is valuable information being communicated?  Or rather, if you don't go it will give the impression that you're being antisocial?  Meetings are perfect examples of an crime perpetrated by people that don't have enough actual work to do or those to feel obligated by people that don't have enough real work to do.

You know why I don't check my email every 5 minutes?  Because I have things I need to get done for the customer!  Sending me pictures of LOLcats is not going to help me get that work done.  Equally, expecting me to respond to that email within an hour of you sending it just reinforces the fact that you have more time on your hands than me.

Image courtesy Flikr: Travis S.

PMBOK and detailing leadership

I read an article the other day over at Project Manager Planet. This work by Herman Mehling was titled "Project Manager or Project Leaders - What's in a title?"  It's a simple enough question but can have a complicated answer.  Herman points out that, for some, the titles are virtually synonymous. What can be confusing about the English language, at times, is different words can sometimes have the same meanings. In this instance, that is not the case. These are not synonyms!

Upon reviewing the PMBOK on the word, I found an uncanny absence.   It's really only mentioned a few times in the entire book!

Page 26 Project Managers...this high profile role requires

flexibility, good judgment, strong leadership and negotiation skills, and a solid knowledge of project management practices.

Page 240

Successful projects require strong leadership skills. Leadership is important through all phases of the project life cycle. It is especially important to communicate the vision and inspire the project team to achieve high performance.

Page 417 Appendix G

Leadership involves focusing the efforts of a group of people toward a common goal and enabling them to work as a team. In general terms, leadership is the ability to get things done through others. Respect and trust, rather than fear and submission, are the key elements of effective leadership. Although important throughout all project phases, effective leadership is critical during the beginning phases of the project when the emphasis is on communication vision and motivating and inspiring project participants to achieve high performance....

If it states on page 240 that successful projects require strong leadership skills, why is it not more thoroughly listed in the 4th edition?  If it's critical in the beginning phases, as listed on page 417, why is it not detailed?  Since "expert judgment" is listed as a tool & technique throughout the body of knowledge, I think PMI missed an opportunity to include "acts of leadership".  Perhaps we should start by renaming the 4th PMI process group from Monitoring & Controlling" to maybe include & Inspiring.

Thoughts on the topic?

Image Source: Flickr James @NZ