Archive for October, 2010

New project management articles published on the web during the week of October 25-31, 2010.  We read all of this stuff so you don’t have to!  Recommended:

  • Cornelius Fichtner continues his series in CIO on taking the PMP examination.
  • Samad Aidane continues his series of podcast interviews with movers and shakers in the project management world in an interview with Intel’s Jeff Hodgkinson, about the results of his survey of the benefits and career value of the Program Management Professional credential.
  • Vitaly Dubravin debunks the idea that a fixed price project can cut costs, in parts one and two.
  • Abdullah Alkuwaiti suggests an improved formula for re-calculating your budget based on your risk management planning activities.
  • The TechAmerica foundation is calling for major reforms in the way the U.S. federal government conducts IT project management.
  • BeMo – Project Intelligence and SharkPro Software have teamed up to offer Microsoft’s Enterprise Project Management under a “Software as a Service” (SaaS) model.  Here’s the BeMoPro home page.
  • Dave Nielsen describes the role of the database architect in the project, and the database administrator after the system is in production, and offers a glimpse into the future of project management.
  • Gary Hamilton, Gareth Byatt, and Jeff Hodgkinson write about green project management.  Yup, Jeff is everywhere this week.
  • Ari Tikka talks up the benefits (!) of change resistance.
  • Jimi Fosdick offers suggestions on how to know when Scrum is appropriate.

Enjoy!

Classically, the stakeholder management strategy is developed early in a project.  It considers the level of interest in the project for each stakeholder, and an assessment of the impact their level of participation, engagement, and support will have on the success of the project in order to select potential strategies for gaining support or reducing obstacles.  This strategy is then used to plan communications and otherwise manage stakeholder expectations.  But it may be helpful to consider the stakeholders not just as individuals facing a project, but as members of an organization facing problems with varying levels of agreement on what should be done, and certainty about how to do it.  To that end, let’s consider Ralph Stacey’s Agreement and Certainty Matrix.

Stacey’s model considers two dimensions with regards to management of organizations: Agreement and Certainty.  In the diagram above, the X-axis reflects the degree of Certainty, and the Y-axis the degree of Agreement, and regions representing specific degrees of Agreement and Certainty are plotted.  For the purposes of this model, Agreement is the degree to which the people in the organization “agree” on what is to be done, and Certainty is the degree to which they “agree” on how it can or should be done.  The region at the upper right, where Disagreement and Uncertainty are the highest, is referred to by many change management researchers as “The Edge of Chaos.”  Few projects facing these twin obstacles will succeed!  However, the other four regions each favor specific stakeholder management strategies.

When there is close agreement among the stakeholders as to what is to be done, and how to do it, the project manager should reasonably anticipate little conflict.  In this case, a strategy of “Telling” the stakeholders, in the form of status reports and progress updates should be effective in managing their expectations.

When there is considerable disagreement among the stakeholders on what is to be done, but little dispute on how, the project manager should anticipate conflict when defining the scope and goals of the project.  In this case, a strategy of “Selling” the stakeholders, in the form of a review of the business case, cost-benefit analysis, or similar destination-focused tools with the stakeholders, as a group, may be effective in getting them aligned to a single “vision” of the project.

When there is close agreement on the scope and goals of the project, but a great degree of uncertainty on how to proceed, the project manager should anticipate conflict when defining the technical approach, work breakdown structure, staffing plan, or scheduling the project.  In this case, a strategy of “Consulting” with the stakeholders, in the form of walkthroughs, demonstrations, and other process-focused tools may be effective in giving them confidence in the project.

When there is a moderately high degree of both Disagreement and Uncertainty, but still short of the Edge of Chaos, the project manager should anticipate conflict driven by the perception and reality of the risks facing the project.  In this case, “Collaboration” is called for, throughout the planning and execution of the project.  The stakeholders must be heavily engaged, from risk identification and planning of risk responses through monitoring of the status of identified risks.  It is also probably worth adjusting the change control process to more heavily weight the impact of proposed changes on both the individual risks being tracked in the Risk Register, and the overall project risk profile.  Communicating the status of both risk management and change control activities, as part of regular status reports and other stakeholder communications, will help keep the stakeholders actively engaged with the project, and with each other.

Delivering real and perceived value to the stakeholders is the principle measure of success in a project; consequently, effective stakeholder management is one of the keys to ensuring project success.  Effective project managers consider the degree of agreement and certainty that their stakeholders have toward the project at the beginning, and plan accordingly.

New project management articles published on the web during the week of October 18-24, 2010.  We read all of this stuff so you don’t have to!  Recommended:

  • Meredith Levinson analyzes the new list of the 100 Best Jobs in America, from Money Magazine and Payscale.com.
  • Gary Hamilton, Gareth Byatt, and Jeff Hodgkinson suggest how we can apply lessons learned in training fire fighters to training project teams.
  • Cornelius Fichtner begins a multi-part article in CIO magazine on preparing to take the PMP exam with a review of the eligibility requirements.
  • A new post on the PMI Career Central blog: 4 tips for making a good first impression.
  • Dana Brownlee tells us how to motivate your team during difficult times.
  • Mohammed Al-Taee interviewed Robert Lavigne, Enterprise 2.0 social media consultant and PMP, on branding yourself.  He also includes a link to a brief YouTube video of Dave Howlett, “real human being” and motivational speaker from Toronto.
  • While we’re on the subject, PMI is offering a discounted price of $25.55 for Elizabeth Harrin’s new book, “Social Media for Project Managers,” during the month of November.   Can’t wait?  Get it almost as cheap from the IT Project Manager Book Store.  No Kindle version yet, but I’ll be sure to let you know.
  • Andrea Brockmeier offers three tips to increase chances of good sponsorship of your projects.
  • Brad Egeland posted parts two and three of his series, Ten Actions to Better Project Performance.  Here’s part one, in case you missed it.
  • Judy Umlas blogs about work-life balance on the PMI Voices on Project Management.
  • Arpan Shah commented on what Microsoft’s new Office 365 cloud service will mean for Project 2010.  He also includes links to a great demo of how a project in Project Professional 2010 can be synchronized with Sharepoint 2010 task lists.
  • Jamie Gelbtuch and Conrado Morlan write about the risk of miscommunication in a global project team, in this month’s PMI Community Post.  Their anecdote about Helmut Kohl is funnier if you speak some German.
  • On a related topic, Thomas Cutting writes about communicating what matters.

Enjoy!