Discussion Locked

Mad Ravings of a new PMP

0 helpful
20 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
blog root

20 replies

by vicki

Today I went to a presentation by a respected CIO.  He talked about how the organization is working on improving project management as an action to improve project success.  I asked him what strategies they were employing toward this goal.  The answers:

  • Project Management Framework followed by all
  • Lessons learned reviews of previous failed projects
  • Project status reports to include variance from initial project funding in addition to rebaselined budget

These are not consistent with PMBOK standards, but are workable.  My issue is there seems to be a big bullet missing from this list in terms of developing mature project managers.   I am sure it was simply an ommission since he was put on the spot, but it still raisers a red flag.  The percentage of project managers in our organization's employ with PMPs or even active involvement in the PMI is low. 

I can see there is some work to be done in promoting the PMI, PMBOK, and PMP as tools for successful project management.

 

by yeoman

 

  1. PMBOK, etc., are tools, not magic bullets. Get your PMs trained, but that's not enough.

  2. They must be partnered with good processes like that documented in ITIL. You can devise your own.

  3. A good governance framework must be implemented, covering the whole SDLC from business justification to controlled implementation.

  4. Good reporting helps identify problems early. A basic weekly report will provide costs vs budget, schedule vs plan, risks and mitigating actions, issues and actions to address the issues, and progress activities for the week. From this report you can see if deviations are increasing.

And you need one or more experienced PMs who can guide or mentor the others. And you need senior management commitment. Management will always want things done more quickly and more cheaply.  But that cannot be achieved by taking shortcuts.  That can be achieved by better project management.

by yeoman

 

  1. PMBOK, etc., are tools, not magic bullets. Get your PMs trained, but that's not enough.

  2. They must be partnered with good processes like that documented in ITIL. You can devise your own.

  3. A good governance framework must be implemented, covering the whole SDLC from business justification to controlled implementation.

  4. Good reporting helps identify problems early. A basic weekly report will provide costs vs budget, schedule vs plan, risks and mitigating actions, issues and actions to address the issues, and progress activities for the week. From this report you can see if deviations are increasing.

And you need one or more experienced PMs who can guide or mentor the others. And you need senior management commitment. Management will always want things done more quickly and more cheaply.  But that cannot be achieved by taking shortcuts.  That can be achieved by better project management.

by fe

PMI and PMBOK provide, like other best-practice frameworks, guidance.  However, they do not guarantee effective project management in practice.  I was recently appointed to fix a PMO that consists entirely of card-carrying PMI project managers.  The group is ineffective because they are too academically focused at the expense of actually delivering software on time and on budget.  The purpose of projects has become to practice the discipline, not to advance the business.  Business aligned-vision must be at the heart of any PMO.

by pmpsicle

I don't understand why you say these aren't consistent with PMBOK. Status reporting and lessons learned are both requirements of PMBOK. And the PMBOK is attempting to be the standard framework of choice. 

I must say, though, that I disagree with the standardized PM framework comment. I don't believe that a standard framework goes far enough. What is needed is a standardized system. What's the difference? SEI/CMM, ITIL, PMBOK, and ISO 9000 are all frameworks (aka standards in the rest of the world). They discuss basic requirements for providing quality in their area of expertise and identify the key elements for quality. A system, however, is a specific implementation of the elements needed by the organization. To illustrate ... the framework says a status report must be produced; a system says use this form, provide this information, give it to this person etc.. Just saying you need a consistent framework isn't enough (and for that matter isn't actually required). A quality system will need to be an implementation of multiple frameworks - SEI/CMM, ITIL, PMBOK are all required in a typical development/operations shop (they each cover different portions of the shop; CMM-development, ITIL-operations, PMBOK-project management).

And I agree with your comment about developing mature project managers. It seems that we have forgotten that good people will make even a bad system work -- but bad people will make a system fail - no matter how good. While I agree that the franchise model of systems is a good model - at some point the quality of your people begins to be more important than the system.

But then again it's not fashionable to say that you need good people and that you need to train them - and that it costs money.

by vicki

All good points.  I agree that any standard is simply a method to be consider and molded to each unique situation.  Probably referencing the PMBOK distracted from my true intent of the blog in that the CIO did not talk about the people of project management.  Where are the recruitment, training, and leadership strategies?  I mention PMI, PMBOK, and PMP as specific tools to assist the people in project management because I had worked 6-years without them and have seen the true benefit the have brought to me since in being able to manage projects more efficiently.   But as even the PMBOK points out, its not exactly a cookie cutter, while each tool should be considered there are times certain actions would not benefit the project.

Inconsitencies:

  1. I agree following a framework is consistent
  2. Lessons learned should not focus on only failed projects.  What went well with the projects that succeeded that we can follow?
  3. Status reporting is good, holding people to a budget is good, but holding to a budget that has since seen approved changes doesn't hold a lot value other than to say we need to improve how we develop original estimates.  But for the project at hand, current approved funding should be the basis for variance.

On  #3, I had a conversation with a finacial analyst looking at a project.  The original project was budgeted for 1, there were approved revisions that brought it to 1.5 (approved funding), management said in a status report that the current projection was for 1.4, under budget.  This analyst did not agree it was under budget since the original plan was 1.  I am concerned that if this is the trend then project quality will suffer due to a relunctance to approve needed change requests for fear of the appearance of being "overbudget".

by jamesrl

Others have attempted to adrdess the original post, and some of the issues therein. I would reiterate that mature PMs doesn't necessarily have to include PMI/certification. Some of the best I have ever met do not have certs nor need them. A mature organization can either develop a mature project framework from elsewhere or develop one and be successful

Your point on the rebaselined budget. One of my projects 5 years ago addressed this very point. It was a project tracking system to give a quick view on a monthly basis of the entire portfolio including variance to original and to rebaselined budgets and schedules. The variance on the rebaselined was the most important.

The budget may change for a number of reasons outside of planning issues - so to me, the variance has to be measured on the last budget that all the stakeholders approved. If you do a project reset and get new agreements on timing budget and deliverables agreed to by all stakeholders, that what you measure against.

James

 

by wayne m.

Gaping Hole: Who is Responsible?

The biggest hole I see is that there is no plan for accomplishing the steps listed by the CIO.  The CIO needs to take responsibility for teaching the project managers how to meet his expectations.

PMBOK provides a reasonable reference on steps to take but it does not cover the real world situations.  Just reading PMBOK is like just learning the rules of Poker and then playing in a high stakes game; you will lose your shirt.  Also, note that one cannot even apply for a PMP without existing experience; if one relies on PMP certification, then people need to screw up a couple of projects first!

Setting goals without a plan to meet them is just wishful thinking (at best).

 

by dc guy

There was a post on another thread a couple of days ago saying that it's okay if a manager is feared by his subordinates, that in fact being feared would make him more effective than being loved.

Welcome to the Fifteenth Century, slaves!

There is indeed more to management than the PMBOK.

by buffalo-john

PMI teaches that experience alone is insufficient - doing the wrong things over and over again doesn't improve maturity.

Experience teaches that rules alone are not sufficient - the game is played to conclusion whether there's agreement on the rules or not.

You need to have rigorous rules AND experience to be successful. At least that's what's I am shooting for. 

by buffalo-john

PMI teaches that experience alone is insufficient - doing the wrong things over and over again doesn't improve maturity.

Experience teaches that rules alone are not sufficient - the game is played to conclusion whether there's agreement on the rules or not.

You need to have rigorous rules AND experience to be successful. At least that's what's I am shooting for. 

by fakir0059

People think that Managers can do wonders. They can only do so much.
What they can do is very limited. The Hackers can do more than the
managers. They can undo what the managers are trying to achieve.

This is discussed at
http://www.newerawisp.blogspot.com/

This is because the internet infrastructure has given the power to undo
the work done by the 10's of thousands of clients presided over by IT
managers  to the hackers by virtue of the role of the servers. The
sole role of the servers is to send the documents, stored in the
servers, to the clients inspite of the limitations placed by the
security software in the form of firewalls.

Many IT managers have admitted their frustration on the internet by posting messages.

THe way to stop the hackers is to redevelop the infrastructure to take this power away.

by fakir0059

People think that Managers can do wonders. They can only do so much.
What they can do is very limited. The Hackers can do more than the
managers. They can undo what the managers are trying to achieve.

This is discussed at

http://www.newerawisp.blogspot.com/

This is because the internet infrastructure has given the power to undo
the work done by the 10's of thousands of clients presided over by IT
managers  to the hackers by virtue of the role of the servers. The sole
role of the servers is to send the documents, stored in the servers, to
the clients inspite of the limitations placed by the security software
in the form of firewalls.

Many IT managers have admitted their frustration on the internet by posting messages.

THe way to stop the hackers is to redevelop the infrastructure to take this power away.

by alan.hurshman

While I stronly support _valid_ certification programs, PMP certification

as provided by the PMI is not one I would put a lot of faith in. The work

experience requirement is meaningless since no attempt is made to

determine if you were actually successful at the projects you managed.

The same is true, I believe, for the educational requirements. Having run

a few project rescues in my time it seems to me that in an organization

with a number of project managers on staff, the best rarely have PMP

designations. The reason? The best managers are too busy handling

the important work while the less competent have the time to attend PMI

meetings and do course work taught by people who most of us wouldn't

trust to run a lemonade stand.

 

--

AlanHurshman

 

by vicki

I had already experienced this phenomenon at work, but for some reason I was surprised when I came across it here.  But of course, people are people whereever you are and our differences is what provides stimulating conversation.

Me (three days after passing the PMP):  Does anybody on the IT Steering Committee or staff have a PMP?

QA Manager:  No.  But so what?  The only thing a PMP designation indicates is the the person can pass a test.

I was surprised by this person's reaction since they are a big supporter of the PMI in our area. She was the one that convinced me to join.

Before I head too far down this tangent, I guess I should say I understand where it comes from. In a past life (career) I was an accountant with minimal education working with another accountant who had just finished her BA and was studying for her CPA. Now this gal just didn't get some things and studying for the CPA probably wasn't going to make her any smarter. On the other hand, I never heard that she passed it. But at the time I decided education and credentials were obviously useless since I was so much smarter than her when it came to accounting and I had neither of those. That was a long time ago.

So why did I decide to pursue the PMP credential 15 years later? Well I had since earned my BA after recognizing no matter who smart I was, employers were going to have an easier time taking me serious if I completed that education goal. I had also completed a 9-month Project Management Certification course when one of my classmates pointed out the upcoming changes in the PMP test. In an effort to make myself more marketable in my job search, I decided I should do it and use the cutoff of the existing examination as my time limit. And I'm so glad I did.

Honestly, after working on a large project for 6 years and taking the 9 month course I thought it would be a no-brainer to pass the PMP. I knew some study would be needed to memorize some of the lingo and such, but I know project management. Oh my did I have things wrong. Luckily I allowed myself plenty of time for study and followed a strict schedule and process to make sure I suffiently learned all that I needed to.

This most amazing thing to me was the number of times I learned a new tool or process and went "Ah, if only we'd been doing that then X issue could have been avoided". Some of the things I knew about but didn't consistently follow and others were brand new concepts. Also, seeing a roadmap (so to speak of the PMBOK) of the things to be considered and in what order, turned processes that were based on instinct and common sense into a tangible must-do's that I could sell to those that want to take short cuts.

Notice I use the word "consider" above. I agree with everyone that says PMBOK is a guideline and not all processes and tools will be valuable on all projects. But having an armory of processes to consider will be helpful to ensure that I don't overlook important steps in project management.

So I have a theory that those who belittle the value of the PMP are probably coming from the same context I did 15 years ago with my CPA wanna-be coworker. These are smart people that implement successful projects and don't need a guideline to follow because they have it all figured out. But I still can't help but to feel that many of these people and their projects would benefit from learning tools such as Earned Value Management, that a WBS is not slapping tasks into MSProject, a Risk Register and how to assign values to risks, and what is ethical in communicating project status. Okay, so most of your non-PMPs out there already know some or all of this. But studying and passing the PMP is the single best way to learn about and understand all of the processes and tools recommended by PMI through the PMBOK. By hiring a PMP you are assured that the person has had exposure to all of the recommended tools, processes, and recognized ethics standards. Admittedly, this does nothing to ensure they are a good project manager in practice. For me, it's a no-brainer to use those tools and processes that people smarter then I have spent 30 years developing and refining. I don't want to reinvent the wheel. Hopefully as I gain more personal experience I can figure out how to shape the wheel to work the best for me.  I think I'm admitting I'm not necessarily as smart as I've let myself beleive over the years.

A final thought on the PMP test. I have heard two misconceptions. The first I listed above (it's just a test), the second was a non-PMP project manager who said "well the PMP test may test hard skills, but what about the soft skills (people skills)". Well let me say that the PMP test is so much more than "pick the correct definition of 'work package'". This test is very intense with 2 to 3 of 4 choices being correct, but having to select the BEST answer, needing to know Maslow's Hierarchy of Needs (just for example), and the PMP Code of Ethics. Please visit PMI's Sample Questions to get a better feel for the test before you judge those who have passed it too harshly or without respect. It is a serious test and most of those who have studied and passed it take Project Management seriously.

by shawn t. futterer, pmp

Congratulations on earning your PMP Cert!!

No matter what anyones view is on the PMP Certification, it is currently the Global standard in Project Management. For the "Nay Sayers" out there, I implore you to visit monster.com or careerbuilder.com and search for Project Manager jobs. You'll notice that the majority of employers "Prefer" if not require PMP Certification as a qualification.

The PMP Exam may only be a test and a fairly difficult one at that, but at the root of the PMBOK is some very industry agnostic methodolgy that can be applied to any project whether IT or Construction. The PMBOK is not designed to be a specific roadmap to every projects destiation, but rather the map itself with many routes available. All you have to do is choose the best road to follow. What that means is: It's all in the way you shoose to apply the PMBOK's teachings.

I believe in the value of the PMP. Did you know:

  1. The PMP Cert was recently ranked the No. 4 Hottest Certification for 2006. 
  2. Having a PMP Certification means you can command a higher salary Payscale.com has the details.

Congratulations again!

Shawn Futterer, PMP

Visit www.readysetpass.com for your PMP Exam Preparation needs. Quickly and Easily Learn To Pass The PMP Exam. We offer hands-on Project Management Professional Exam Preparation materials, online exam simulation and e-learning virtual classroom training. All over the World, we help individuals, companies and organizations leverage Project Management knowledge and education. Our methods create productive benefits for employees, customers, and other internal and external organizational partners. Our customers choose when, where, and how they want their training solutions delivered.

 

by vicki

I've seen the debate here on the PMBOK, what it represents, how useful it truly it is project management.  Some comments I received to my first blog posting:

  • PMBOK, etc., are tools, not magic bullets.
  • PMI and PMBOK provide, like other best-practice frameworks, guidance.  However, they do not guarantee effective project management in practice. 
  • PMBOK provides a reasonable reference on steps to take but it does not cover the real world situations.  Just reading PMBOK is like just learning the rules of Poker and then playing in a high stakes game; you will lose your shirt. 

While I like to think that I understand the intention of the PMBOK, and to some extent I'm sure I do, the best description of the purpose of the PMBOK can be found in the November 2005 PMItoday; "...the guide is intended as a 'foundational reference.'  It is 'neither comprehensive nor all-inclusive,' but a 'subset of the Project Management Body of Knowledge that is generally recognized as good practice."..."The PMBOK Guide is not a methodolgy, a how-to or specific set of procedures."

So it would seem that PMI agrees with the sentiment here.

by gjucan

I definitely like your poker comparison. Remember the catch phrase in the WPT Texas Hold-Em televised shows: ?It takes a minute to learn, a life time to master it!?? This is a perfect description for Project Management as well.

Many people read a book (e.g. PMBOK) and think that they?re ready for anything a project will throw at them. When they hit rough waters they try to hide behind the book, missing the point that PMBOK should be understood, not learned. PM?s competency will show into how he/she adapts the best practices to the unique project characteristics to achieve project success.

by vicki

What do these three things have in common?  Two are bigger than a breadbox and the final somewhat intangible. But they do have one very important thing in common.  They are all the results of a project.  Someone had to have an idea, initiate the idea, plan for the completion, execute and control work, verify the quality, and finally deliver a needed product. 

The question that comes to mind at this point is would an exemplary steelworker be put in charge of planning, controlling and verifying quality on an entire bridge without education in project management?  I think for the safety of those crossing that bridge (or flying on that airplane), we should breath a sigh of relief that the answer is likely ?no?.   There are very specific credentials expected at the engineers that lead these large projects.  At the same time I would not want the best educated and credentialed project manager in the world assembling the airplane I fly to vacation on.  The truth is steel working, assembly line work, and project management are very different skill sets.

The project management skill set involves communication, defining the project, leading, planning, risk management, change management, monitoring, and most importantly, learning from experience to manage the next project with even better success.  With the airplane and the bridge, people?s lives depend on the fact that the project manager is very capable in all of these areas.  But I don't believe it is any less critical in other types of projects.  The impact on cost and schedule is just as critical with software development and on occasion faulty software can impede the safety and health of people.  A couple of examples include a parole tracking system or a medical reference website.

The moral of the story is don't shortchange your project by assigning those without training and the required skillset to manage your project.

by wayne m.

Software Development is Not a PMI Project

Software development, unlike building a single airplane or a single bridge, does not culminate in a single deliverable.  Software development, quite correctly, needs to be developed iteratively as a sequence of deliverables.

Managing a software delivery effort as a single project prevents one from developing a sequence of planned deliveries and eliminates most negotiations with users.  It is either now or never.  Applying a full PMI project management approach to an individual deliverable requires too much overhead to be applicable to a small deliverable and thus preempts the ability to create small delivarables.  This puts pressure on projects to commit to ever expanding monster deliverables to justify the cost and complexity of the management.

While I agree that the proper skillset is necessary, I don't necessarily believe that PMI properly addresses the necessary skillset for effective software development.

 

This discussion is closed to new replies.