 |
 |
|
 |
|
How do I convince my management to spend some time at the front end doing the initial planning when they don't think planning is real work? |
|
1. First try the rational arguments using the simple analogies like "Measure twice, cut once". Open discussion regarding lack of planning as one of the major sources of project re-work and re-do efforts that cost more time and money than having taken the time to plan in the first place. 2. Make sure that your boss or client understands that planning is just getting the people together who make the project happen to think through and identify the necessary tasks, who will do what (roles and responsibilities), how long will tasks take, and what are possible risks we might see? The outputs of the "Who, What, Where, When, Why, and How" discussion becomes the project plan. 3. Another use of the plan is to establish the baseline. Without a plan, how do you know where you are with regard to Cost, Schedule and Performance? "If I've spent half the time and used up half the money, am I really half done?" 4. If you're really encountering resistance, sometimes you have to practice "stealth" project management. Schedule things like "Systems Review stage 1" or "Component Analysis" that sound like real work, and use the time to plan with your project team.
|
Suggested Learning Tool: |
 |
|
What can I do to pull a team together that includes all the differences related to:
|
|
1. First is for you the project manager to learn about the members of the team. For culture, go to one of the many books like Kiss, Bow or Shake Hands. For Personality, check out ZB Global's People Style Profile™ which includes how to work with different personality types. The more you try to learn, the more likely the folks on your team will accept your sincerity and efforts. 2. Try to have at least one face-to-face meeting. If you can't do that, do it with video conferencing or at least something like Web-ex or Web-meeting. Talk about yourselves and what your contributions should be (roles and responsibilities). 3. Agree on what we all have in common - a desire and need to accomplish the project within the given parameters. 4. Open discussion on what potential problems will be caused by the various differences and what can we do about it. 5. Mutually decide on the key aspects of the project culture that you mist have to succeed. Open and honest discussions, no hiding problems, asking for help, meeting commitments.
|
