Beyond PMO Consulting

"welcome to my personal blog," Ammar W Mango

  • about me

    Organizational Project Management Consultant, using profession as a platform for learning beyond just work. My passion is learning more about self, people, universe, and God.
    I am into Religion, Meditation, Yoga, and Tai Chi. I love learning about human behavior and motivation.
    I am a gourmand who loves healthy food and following latest research into health and natural healing and remedies. I jog and swim whenever I get a chance.
    Please write and tell me about yourself
    Welcome to my blog
    Ammar

  • New!

    PMPNOW Download Link

    Download my new Mobile App PMPNOW! FREE

Posts Tagged ‘Consulting’

Pick A Consultant; Not Just Any Consultant!

Posted by Ammar Mango on August 7, 2013

pickaconsultantThere is more to consulting than just the consultant.  There has to be.  This is why the same consultant might do a splendid job for one organization and not so well for another.  Consulting is about the client, culture, and timing, as much as it is about the consultant.

Consultants vary in style and personality and that variation makes our experiences with the same consultant so different.  You might like him, I might hate him.  Actually, I might love a consultant on one day and hate him on another.  When hiring a consultant pay attention to their personal style as it will affect your ability to get the benefits you are seeking.

For example, some consultants are so non-committal style that they tell you everything is possible, and they would be right too.  For example, when asked if this approach might work, they will tell you it might, even if it had a chance of 1 in a 1000.  They are so concise that they might spook the untrained eye.  Some clients are comfortable with such consultants.  They can deal with the extra preciseness.  Others might not.

Some clients would shy away from the “non-committal” style consultant, and want an “Assuming” consultant.   Assuming consultants are the ones willing to take responsibility for decisions on behalf of the client.  For example, they are comfortable telling the client what to do and what not to do, or what would work and would not.  they would say it with almost certainty as they consider 90% confidence is good enough for them to dismiss the possibility of failure.  For example, they would tell the client, if you change this approach, you will get better results guaranteed.  Of course the consultant cannot guarantee the results, but he is trying to help the client take a decision.

Everyone has experiences with both types of consultants.  Personally, I remember once I was looking to buy a house in Michigan in the early 90’s.  I got introduced to an excellent Realtor who is a friend of a friend.  He took me through quite a few beautiful houses that fit my needs perfectly.  He never was bias.  When I asked him his opinion, he would objectively state the pros and cons of every house, but never pushed me to buy any.  the result of this non-committal approach was me not buying anything.  Not because I did not find anything I like, but because I needed a bit more help given my low level of experience with the market at that time in Michigan.  Five years later, he would have been the perfect Realtor to help me pick a house.  but at that early stage of maturity in my knowledge in the housing market I needed someone more aggressive, who would put his neck out, beyond his duty as a consultant, to “sell” me on a good idea or, in this case, a good house.

I have to admit that I have fallen in this trap with clients all too often; where my diligence in being an “honest” consultant, kept me in the non committal zone, with clients who needed a little bit extra help.  The result was confusion and frustration from the client.  With mature clients who understand fully my role as a consultant, and there responsibilities as clients, the approach worked perfectly for both sides.

There has to be an honorable mention of the “Zealot” consultant.    This is the consultant who is taking things too personally to be objective at all.  He would even take it personally if you do not follow his or her recommendations to the letter.  Even this type of consultant is needed also for some clients.  When the client lacks the discipline but wholeheartedly wants the results, then the zealot consultant is a good solution.  The zealot consultant is a hat that you were and it is not a personality necessarily, even though I have to admit some zealot consultants have this hat on even when they sleep.  They are zealots to the bone.  However, it is OK to act like the zealot consultant when your client is asking you to help them with discipline issues, not only structure or process.  A word of caution though: sometimes we wear the zealot hat when we are too attached to the client or the account.  For example, if you are somehow attached to the mission of the organization you are helping, then you might find yourself too critical and judgmental whenever they make a mistake.  You might even be pushy in getting them to do what they should do, and you might even get angry and lose composure when the client is not listening or not following agreed upon actions.  This is why a consulting company needs consultants to help them improve their own operation; internal consultants, no matter how experienced, are too attached and emotionally involved to objectively deal with the challenge.

So, when choosing a consultant, take into consideration your style, organizational culture, and the issue at hand, and see if their personality meets the specifics of your situation.

Advertisements

Posted in Uncategorized, Understanding OTHERS | Tagged: , , , , | Leave a Comment »

My Cool Neighbors

Posted by Ammar Mango on June 13, 2012

One of the perks of working out of Abul Haj Building in Amman is the really cool neighbors you have.  Innovators, original, and ready to go off the beaten track.  Many of them actually paved the beaten track that others follow.

I am not socially active per se, but every ride up or down into the elevator is a chance to bump into one of them.  Today, I invited one of them, principal at an IT company, for a cup of coffee early morning.

One of the key things amazed me during the enriching conversation was how eerily similar are the challenges and opportunities surrounding the Jordanian small businesses.  Staffing, Regulations, Regional Markets, Economic conditions, succession planning, and many other topics are so relevant and similar between our companies.  I started wondering if I got a chance to sit with other owners, managers in the building how enriching that would be, and how much we can help each other with ideas, opportunities, services, etc.

One thing I always felt about businesses in the region is that we are solo hunters; tigers, not lions. We do not like to hunt in groups, and we do not want to share leads, ideas, or opportunities and challenges with each other. With some, you feel that even the information they give you is propaganda to lead you off the hot business trail they are pursuing. I contrast that to my experience in the United States where I worked mainly for consulting companies.  We used to readily and easily lend fierce competitors resources for a project where they are understaffed, and vice versa.  We did not do it only out of the goodness of our heart, such a thing would be too civilized for the business world.  But we did it because we would get paid for it, and when we needed help, the other competitors would oblige.  Do not get me wrong, we had our bitter fights and even law suits, but we still cooperated.

My guest today was very open, friendly, thought provoking, and fun to be around. I know there are more like him in the small business world around me. I just have to look up to see them.  So, I am thinking seriously of starting a social group for company managers in the building.  A monthly get together, maybe an informal reception to chit chat and shoot the breeze.

Maybe this can grow into a business community for small business, a real one, not just a facade.  Enough dreaming and back to work 🙂

Posted in Understanding OTHERS | Tagged: , , , , , | 2 Comments »

Organizational Change is Like Riding a Bicycle

Posted by Ammar Mango on June 11, 2012

One of the toughest challenges on projects is managing the change that the project work and deliverables bring about. There a lot of similarities between organizational challenges from change and the challenges of riding a bicycle:

1. Expect to fall a couple of times before you get used to it:  Same with new systems and processes; be ready to be clumsy using them.  However, we need to remember that once you learn the new ways, they will bring better results.

2. In the beginning, walking is easier:   Just because we are really good in the old ways of the organization, does not mean we should not change.  We think we are good in the old ways, but that will do us no good if the whole way we are doing business is not fit for the new work environment.

3. In the beginning, walking is faster:  Change helps us do things more professionally, and even if we probably can get short term benefits faster taking shorcuts, however, learning how to do things the right way and professionally will pay off.

4. Doubting our ability to ever do it right: Other bicyclists make riding seem so easy.  Until we try it.  Then we find out it is not as easy as they make it look.  So, we get disappointed and not want to do it anymore.  If you want to master your profession, you need to put in the time to learn how to do things right.

5. We want to break records after first day of riding: We are used to see bicyclists zoom through the finish line and being hailed by the crowds.  However, we do not see the years of hard work and sweat and exercise that precede the events.  Same thing with change.  do not think that organizations who master their work got there without the hard work, the mistakes,

6. Someone running along holding the bike: It is OK to gradually build capacity, by bringing in consultants, trainers, support people, who have experience, until we are able to do it ourselves.

7. Do not buy race bike from day one: It is OK to get a bike with training wheels, or an easier to ride bike.  Same thing with organizations, do not rush into using complex tools and processes from day one.  Start with a simplified system, and build up into something more sophisticated as your team get the hang of it.

8. Get the right size bike: You might want a bike like the one your neightbor has.  However, you might need something higher or a thicker tire, then you need to get that.  Same with organizational change.  Do not borrow another company’s system and assume it will “fit” yours.  Customize your system to fit your needs and requirements and organization.

9. Don’t go off track too soon: Going on rough terrains when you did not get enough training will result in problems.  Same with organizational change.  try to tackle safer, easier projects rather than challenged projects, especially in the beginning, to build momentum and small success.  This will motivate team and prepare you for bigger more challenging projects.

10.  Try and Try again: Imagine if you stopped trying after falling off the bike for the first time.  No one would have ever learned to ride a bike.  Instead persevere and be ready to fall off and get back on track several times until you do it right.

Posted in The PMO | Tagged: , , , , , , , | Leave a Comment »

One Hundred Rules for NASA Project Managers

Posted by Ammar Mango on May 22, 2012

Follow my blog with Bloglovin
There are probably a 100 stories about where these 100 rules originated.  The important thing is that they have been around for quite a while.  Not many people know about them, however it is amazing how relevant they are still today.  I did not write these rules, and I do not know who to credit them to, but here they are:

One Hundred Rules for NASA Project Managers

The Project Manager
Rule #1: A project manager should visit everyone who is building anything for his project at least once, should know all the managers on his project (both government and contractor), and know the integration team members. People like to know that the project manager is interested in their work and the best proof is for the manager to visit them and see first hand what they are doing.

Rule #2: A project manager must know what motivates the project contractors (i.e., their award system, their fiscal system, their policies, and their company culture).

Rule #3: Management principles still are the same. It is just that the tools have changed. You still find the right people to do the work and get out of the way so they can do it.

Rule #4: Whoever you deal with, deal fairly. Space is not a big playing field. You may be surprised how often you have to work with the same people. Better they respect you than carry a grudge.

Rule #5: Vicious, despicable, or thoroughly disliked persons, gentlemen, and ladies can be project managers. Lost souls, procrastinators, and wishy-washies cannot.

Rule #6: A comfortable project manager is one waiting for his next assignment or one on the verge of failure. Security is not normal to project management.

Rule #7: One problem new managers face is that everyone wants to solve their problems. Old managers were told by senior management—”solve your own darn problems, that is what we hired you to do.”

Rule #8: Running fast does not take the place of thinking for yourself. You must take time to smell the roses. For your work, you must take time to understand the consequences of your actions.

Rule #9: The boss may not know how to do the work but he has to know what he wants. The boss had better find out what he expects and wants if he doesn’t know. A blind leader tends to go in circles.

Rule #10: Not all successful managers are competent and not all failed managers are incompetent. Luck still plays a part in success or failure but luck favors the competent hard working manager.

Rule #11: Never try to get even for some slight by anyone on the project. It is not good form and it puts you on the same level as the other person and, besides, probably ends up hurting the project getting done.

Rule #12: Don’t get too egotistical so that you can’t change your position, especially if your personnel tell you that you are wrong. You should cultivate an attitude on the project where your personnel know they can tell you of wrong decisions.

Rule #13: A manager who is his own systems engineer or financial manager is one who will probably try to do open heart surgery on himself.

Rule #14: Most managers succeed on the strength and skill of their staff.

Initial Work

Rule #15: The seeds of problems are laid down early. Initial planning is the most vital part of a project. The review of most failed projects or project problems indicate the disasters were well planned to happen from the start.

Communications

Rule #16: Cooperative efforts require good communications and early warning systems. A project manager should try to keep his partners aware of what is going on and should be the one who tells them first of any rumor or actual changes in plan. The partners should be consulted before things are put in final form, even if they only have a small piece of the action. A project manager who blindsides his partners will be treated in kind and will be considered a person of no integrity.

Rule #17: Talk is not cheap; but the best way to understand a personnel or technical problem is to talk to the right people. Lack of talk at the right levels is deadly.

Rule #18: Most international meetings are held in English. This is a foreign language to most participants such as Americans, Germans, Italians, etc. It is important to have adequate discussions so that there are no misinterpretations of what is said.

Rule #19: You cannot be ignorant of the language of the area you manage or with that of areas with which you interface. Education is a must for the modern manager. There are simple courses available to learn computerese, communicationese and all the rest of the modern “ese’s” of the world. You can’t manage if you don’t understand what is being said or written.

People

Rule #20: You cannot watch everything. What you can watch is the people. They have to know you will not accept a poor job.

Rule #21: We have developed a set of people whose self interest is more paramount than the work or at least it appears so to older managers. It appears to the older managers that the newer ones are more interested in form than in substance. The question is are old managers right or just old? Consider both viewpoints.

Rule #22: A good technician, quality inspector, and straw boss are more important in obtaining a good product than all the paper and reviews.

Rule #23: The source of most problems is people, but darned if they will admit it. Know the people working on your project to know what the real weak spots are.

Rule #24: One must pay close attention to workaholics—if they get going in the wrong direction, they can do a lot of damage in a short time. It is possible to overload them and cause premature burnout but hard to determine if the load is too much, since much of it is self generated. It is important to make sure such people take enough time off and that the workload does not exceed 1 1/4 to 1 1/2 times what is normal.

Rule #25: Always try to negotiate your internal support at the lowest level. What you want is the support of the person doing the work, and the closer you can get to him in negotiations the better.

Rule #26: If you have someone who doesn’t look, ask, and analyze; ask them to transfer.

Rule #27: Personal time is very important. You must be careful as a manager that you realize the value of other people’s time (i.e., the work you hand out and meetings should be necessary). You must, where possible, shield your staff from unnecessary work (i.e., some requests should be ignored or a refusal sent to the requestor).

Rule #28: People who monitor work and don’t help get it done never seem to know exactly what is going on (being involved is the key to excellence).

Rule #29: There is no greater motivation than giving a good person his piece of the puzzle to control, but a pat on the back or an award helps.

Rule #30: It is mainly the incompetent that don’t like to show off their work.

Rule #31: There are rare times when only one man can do the job. These are in technical areas that are more art and skill than normal. Cherish these people, but get their work done as soon as possible. Getting the work done by someone else takes two or three times longer and the product is normally below standard.

Rule #32: People have reasons for doing things the way they do them. Most people want to do a good job and, if they don’t, the problem is they probably don’t know how or exactly what is expected.

Rule #33: If you have a problem that requires additional people to solve, you should approach putting people on like a cook who has under-salted the food.

Reviews and Reports

Rule #34: NASA has established a set of reviewers and a set of reviews. Once firmly established, the system will fight to stay alive, so make the most of it. Try to find a way for the reviews to work for you.

Rule #35: The number of reviews is increasing but the knowledge transfer remains the same; therefore, all your charts and presentation material should be constructed with this fact in mind. This means you should be able to construct a set of slides that only needs to be shuffled from presentation to presentation.

Rule #36: Hide nothing from the reviewers. Their reputation and yours is on the line. Expose all the warts and pimples. Don’t offer excuses—just state facts.

Rule #37: External reviews are scheduled at the worst possible time, therefore, keep an up-to-date set of business and technical data so that you can rapidly respond. Not having up-to-date data should be cause for dismissal.

Rule #38: Never undercut your staff in public (i.e., In public meetings, don’t reverse decisions on work that you have given them to do). Even if you direct a change, never take the responsibility for implementing away from your staff.

Rule #39: Reviews are for the reviewed an not the reviewer. The review is a failure if the reviewed learn nothing from it.

Rule #40: A working meeting has about six people attending. Meetings larger than this are for information transfer (management science has shown that, in a group greater than twelve, some are wasting their time).

Rule #41: The amount of reviews and reports are proportional to management’s understanding (i.e., the less management knows or understands the activities, the more they require reviews and reports). It is necessary in this type of environment to make sure that data is presented so that the average person, slightly familiar with activities, can understand it. Keeping the data simple and clear never insults anyone’s intelligence.

Rule #42: Managers who rely only on the paperwork to do the reporting of activities are known failures.

Rule #43: Documentation does not take the place of knowledge. There is a great difference in what is supposed to be, what is thought to have happened, and reality. Documents are normally a static picture in time that get outdated rapidly.

Rule #44: Just because you give monthly reports, don’t think that you can abbreviate anything in a yearly report. If management understood the monthlies, they wouldn’t need a yearly.

Rule #45: Abbreviations are getting to be a pain. Each project now has a few thousand. This calls on senior management to know hundreds. Use them sparingly in presentations unless your objective is to confuse.

Rule #46: Remember, it is often easier to do foolish paperwork that to fight the need for it. Fight only if it is a global issue which will save much future work.

Contractors and Contracting

Rule #47: A project manager is not the monitor of the contractor’s work but is to be the driver. In award fee situations, the government personnel should be making every effort possible to make sure the contractor gets a high score (i.e., be on schedule and produce good work). Contractors don’t fail, NASA does and that is why one must be proactive in support. This is also why a low score damages the government project manager as much as the contractor’s manager because it means that he is not getting the job done.

Rule #48: Award fee is a good tool that puts discipline both on the contractor and the government. The score given represents the status of the project as well as the management skills of both parties. The project management measurement system (PMS) should be used to verify the scores. Consistent poor scores require senior management intervention to determine the reason. Consistent good scores which are consistent with PMS reflect a well-run project, but if these scores are not consistent with the PMS, senior management must take action to find out why.

Rule #49: Morale of the contractor’s personnel is important to a government manager. Just as you don’t want to buy a car built by disgruntled employees, you don’t want to buy flight hardware developed by under- motivated people. You should take an active role in motivating all personnel on the project.

Rule #50: Being friendly with a contractor is fine—being a friend of a contractor is dangerous to your objectivity.

Rule #51: Remember, your contractor has a tendency to have a one-on-one interface with your staff. Every member of your staff costs you at least one person on the contract per year.

Rule #52: Contractors tend to size up the government counterparts and staff their part of the project accordingly. If they think yours are clunkers, they will take their poorer people to put on your project.

Rule #53: Contractors respond well to the customer that pays attention to what they are doing but not too well to the customer that continually second-guesses their activity. The basic rule is a customer is always right but the cost will escalate if a customer always has things done his way instead of how the contractor planned on doing it. The ground rule is: never change a contractor’s plans unless they are flawed or too costly (i.e., the old saying that better is the enemy of good).

Rule #54: There is only one solution to a weak project manager in industry—get rid of him fast. The main job of a project manager in industry is to keep the customer happy. Make sure the one working with you knows that it is not flattery but on-schedule, on-cost, and a good product that makes you happy.

 

Engineers and Scientists

Rule #55: Over-engineering is common. Engineers like puzzles and mazes. Try to make them keep their designs simple.

Rule #56: The first sign of trouble comes from the schedule or the cost curve. Engineers are the last to know they are in trouble. Engineers are born optimists.

Rule #57: The project has many resources within itself. There probably are five or ten system engineers considering all the contractors and instrument developers. This is a powerful resource that can be used to attack problems.

Rule #58: Many managers, just because they have the scientists under contract on their project, forget that the scientists are their customers and many times have easier access to top management than the managers do.

Rule #59: Most scientists are rational unless you endanger their chance to do their experiment. They will work with you if they believe you are telling them the truth. This includes reducing their own plans.

Hardware

Rule #60: In the space business, there is no such thing as previously flown hardware. The people who build the next unit probably never saw the previous unit. There are probably minor changes (perhaps even major changes); the operational environment has probably changed; the people who check the unit out in most cases will not understand the unit or the test equipment.

Rule #61: Most equipment works as built, not as the designer planned. This is due to layout of the design, poor understanding on the designer’s part, or poor understanding of component specifications.

Computers and Software

Rule #62: Not using modern techniques, like computer systems, is a great mistake, but forgetting that the computer simulates thinking is a still greater mistake.

Rule #63: Software has now taken on all the parameters of hardware (i.e., requirement creep, high percentage of flight mission cost, need for quality control, need for validation procedures, etc.). It has the added feature that it is hard as blazes to determine it is not flawed. Get the basic system working first and then add the bells and whistles. Never throw away a version that works even if you have all the confidence in the world that the newer version works. It is necessary to have contingency plans for software.

Rule #64: Knowledge is often revised by simulations or testing, but computer models have hidden flaws not the least of which is poor input data.

Rule #65: In olden times, engineers had hands-on experience, technicians understood how the electronics worked and what it was supposed to do, and layout technicians knew too—but today only the computer knows for sure and it’s not talking.

Senior Management, Program Offices, and Above

Rule #66: Don’t assume you know why senior management has done something. If you feel you need to know, ask. You get some amazing answers that will astonish you.

Rule #67: Know your management—some like a good joke, others only like a joke if they tell it.

Rule #68: Remember the boss has the right to make decisions. Even if you think they are wrong, tell the boss what you think but if he still wants it done his way; do it his way and do your best to make sure the outcome is successful.

Rule #69: Never ask management to make a decision that you can make. Assume you have the authority to make decisions unless you know there is a document that states unequivocally that you can’t.

Rule #70: You and the Program Manager should work as a team. The Program Manager is your advocate at NASA HQ and must be tied into the decision makers and should aid your efforts to be tied in also.

Rule #71: Know who the decision makers on the program are. It may be someone outside who has the ear of Congress or the Administrator, or the Associate Administrator, or one of the scientists—someone in the chain of command—whoever they are. Try to get a line of communication to them on a formal or informal basis.

Program Planning, Budgeting, and Estimating

Rule #72: Today one must push the state of the art, be within budget, take risks, not fail, and be on time. Strangely, all these are consistent as long as the ground rules such as funding profile and schedule are established up front and maintained.

Rule #73: Most of yesteryear’s projects overran because of poor estimates and not because of mistakes. Getting better estimates will not lower costs but will improve NASA’s business reputation. Actually, there is a high probability that getting better estimates will increase costs and assure a higher profit to industry unless the fee is reduced to reflect lower risk on the part of industry. A better reputation is necessary in the present environment.

Rule #74: All problems are solvable in time, so make sure you have enough schedule contingency—if you don’t, the next project manager that takes your place will.

Rule #75: The old NASA pushed the limits of technology and science; therefore, it did not worry about requirements creep or overruns. The new NASA has to work as if all projects are fixed price; therefore, requirement creep has become a deadly sin.

Rule #76: Know the resources of your center and, if possible, other centers. Other centers, if they have the resources , are normally happy to help. It is always surprising how much good help one can get by just asking.

Rule #77: Other than budget information prior to the President’s submittal to Congress, there is probably no secret information on a project—so don’t treat anything like it is secret. Everyone does better if they can see the whole picture so don’t hide any of it from anyone.

Rule #78: NASA programs compete for budget funds—they do not compete with each other (i.e., you never attack any other program or NASA work with the idea that you should get their funding). Sell what you have on its own merit.

Rule #79: Next year is always the year with adequate funding and schedule. Next year arrives on the 50th year of your career.

The Customer

Rule #80: Remember who the customer is and what his objectives are (i.e., check with him when you go to change anything of significance).

NASA Management Instructions

Rule #81: NASA Management Instructions were written by another NASA employee like you; therefore, challenge them if they don’t make sense. It is possible another NASA employee will rewrite them or waive them for you.

Decision Making

Rule #82: Wrong decisions made early can be recovered from. Right decisions made late cannot correct them.

Rule #83: Sometimes the best thing to do is nothing. It is also occasionally the best help you can give. Just listening is all that is needed on many occasions. You may be the boss, but if you constantly have to solve someone’s problems, you are working for him.

Rule #84: Never make a decision from a cartoon. Look at the actual hardware or what real information is available such as layouts. Too much time is wasted by people trying to cure a cartoon whose function is to explain the principle.

Professional Ethics and Integrity

Rule #85: Integrity means your subordinates trust you.

Rule #86: In the rush to get things done, it’s always important to remember who you work for. Blindsiding the boss will not be to your benefit in the long run.

Project Management and Teamwork

Rule #87: Projects require teamwork to succeed. Remember, most teams have a coach and not a boss, but the coach still has to call some of the plays.

Rule #88: Never assume someone knows something or has done something unless you have asked them; even the obvious is overlooked or ignored on occasion, especially in a high stress activity.

Rule #89: Whoever said beggars can’t be choosers doesn’t understand project management, although many times it is better to trust to luck than to get poor support.

Rule #90: A puzzle is hard to discern from just one piece; so don’t be surprised if team members deprived of information reach the wrong conclusion.

Rule #91: Remember, the President, Congress, OMB, NASA HQ, senior center management, and your customers all have jobs to do. All you have to do is keep them all happy.

Treating and Avoiding Failures

Rule #92: In case of a failure:

  • a) Make a      timeline of events and include everything that is known.
  • b) Put down      known facts. Check every theory against them.
  • c) Don’t      beat the data until it confesses (i.e., know when to stop trying to      force-fit a scenario).
  • d) Do not arrive      at a conclusion too fast. Make sure any deviation from normal is      explained. Remember the wrong conclusion is prologue to the next failure.
  • e) Know      when to stop.

Rule #93: Things that fail are lessons learned for the future. Occasionally things go right: these are also lessons learned. Try to duplicate that which works.

Rule #94: Mistakes are all right but failure is not. Failure is just a mistake you can’t recover from; therefore, try to create contingency plans and alternate approaches for the items or plans that have high risk.

Rule #95: History is prologue. There has not been a project yet that has not had a parts problem despite all the qualification and testing done on parts. Time and being prepared to react are the only safeguards.

Rule #96: Experience may be fine but testing is better. Knowing something will work never takes the place of proving that it will.

Rule #97: Don’t be afraid to fail or you will not succeed, but always work at your skill to recover. Part of that skill is knowing who can help.

Rule #98: One of the advantages of NASA in the early days was the fact that everyone knew that the facts we were absolutely sure of could be wrong.

Rule #99: Redundancy in hardware can be a fiction. We are adept at building things to be identical so that if one fails, the other will also fail. Make sure all hardware is treated in a build as if it were one of a kind and needed for mission success.

Rule #100: Never make excuses; instead, present plans of actions to be taken.

Posted in The PMO | Tagged: , , , , , , | 1 Comment »

The PMO in cultural context

Posted by Ammar Mango on May 21, 2012

I was talking to a colleague today who works for one of the top five global consulting firms.  He is assigned to a PMO setup project in Saudi Arabia.  The discussion was on why many Project Management Office (PMO) setups in the region fail to achieve objectives.  Here are some of the causes we raised:

1) Not addressing culture in PMO setup: Many companies try to copy PMO setups foreign to the region, without taking into consideration the cultural aspects and current level of maturity of project management practices in the organization.

2) Lack of deep PMO experience for many of the consulting companies carrying out the PMO setup project.  Yes, they might be big companies with long experience and big names, but they do not have the experience in PMO setup.  Most of the companies good at this, even in other parts of the world are smaller size, more specialized companies in specifically organizational project management.

3) Many companies try to run a full fledged PMO without a clear gradual plan of bringing the PMO to its full functional state.  They are eager to get it working and they get entangled into having to handle too much too soon.

4) Many try to set up a PMO without a clear documented governance that ties to the organizational vision and strategy.

5) Focusing too much on software without having the processes or the people to get the job done.

6) Lack of real empowerment of the PMO at Executive level, where PMO is pushed to perform, without bringing departments and key stakeholders to support the PMO.

7) Passive resistance from key stakeholders who see the PMO as taking away from their authority or power in the company, or who are benefiting from the status quo, or who are not clear on the PMO and how it can help them.

8) Giving up too early on the PMO for the lack of understanding that PMO setup is a step in a journey that usually takes years to mature the PMO and really reap the benefits from it.

What do you think?

Posted in The PMO | Tagged: , , , , , , | 2 Comments »

 
%d bloggers like this: