90 Percent

Project management, productivity, change management, and more!

What the client explained

Leave a comment

Respective Perspective

Respective Perspective
By Cécile Bérubé, PMP

Perspective:“A particular attitude toward or way of regarding something; a point of view”

What’s the relationship with PM you’ll say? Everything!
You may deliver on time and budget….yet, why are projects apparently performing well and then fail to satisfy stakeholders’ expectations?

Communicating expectations/requirements/specifications is subjective and stakeholders do their best to communicate them. However, it’s subjective and may easily get interpreted. Re-assessing expectations with an iterative approach ensures that expectations are accurate, ensuring alignment for stakeholders’ satisfaction. Having different backgrounds, experiences and expertise may introduce different perspectives, which may introduce high project risks.

What the client explained

  1. Ask. Clarify (“Why”), Re-validate. Understand. Get a holistic perspective at the beginning of the project. Assess expectations up front. Do not assume that all projects are the same. Invest early in the project.
  2. Gain trust….and perspective. Get to know the environment. Getting to know the clients’ perspective helps gain trust and understand his reality and challenges.
  3. Facilitate exchanges but do not judge or blame. Leadership qualities and communication skills are crucial in order to gain respect and collaboration from key stakeholders. Conflicts are normal, having our own respective perspectives. Resolve.
  4. Assumptions are just known unknowns! Transform the unknowns into knowns, earlier than later. Clarify system, product, project and stakeholders expectations.
  5. Facilitate but control. Use simple tools, such as short iterative follow-ups, (i.e. weekly, 15 minutes) but do not overload. Ask simple questions, speak the language, be relevant, be prepared, challenge.

#What’s your perspective, viewpoint?

Leave a comment

Risk management in a nutshell

Risk management is often overlooked, or done unofficially. Some practice it scarcely without even knowing that’s what they are doing. To add a little clarify to all this, here is a quick overview:

Risk management in a nutshell is

  1. Taking the time to identify potential risks in the project
  2. Identifying the impact of the risks should they happen
  3. Plan next steps regarding those risks before they happen
    1. Execute those next steps
  4. Monitor current and new risks till the end of the project
    1. For new risks, you go back to step 2 and 3

False assumptions about risk management

  1. Involves only the project manager
  2. Risks are only associated with technology (so the tech team)
  3. Is only done once at the beginning of the project
  4. Adds useless overhead to a project
  5. Risks are always negative
  6. Doesn’t require a particular budget

Reality about risk management

  1. Involves the whole team
    1. Everyone can contribute in identifying risks
    2. Anyone can be made responsible for monitoring and preventing a certain risk
    3. Mitigation plans can include building prototypes (amongst other examples) which involves team members other than the project manager
  2. Risks can be anything from the weather preventing to work, to team members leaving, to new technology being used. It is anything that can affect your project which was not planned.
  3. It’s done throughout the whole project
    1. new risk can be identified during the project
    2. the status of current identified risks can change, which can require to review the mitigation plan
  4. Can actually reduce project costs. If spending 100h on a prototype can prevent 250h of unplanned changes in the future, it’s a 150h reduction in the end.
  5. Risks can actually be positive but are called “Opportunities” in these cases instead of a “Treat”, see Risks: not always negative
  6. Risk management requires time. If no budget is planned for it, than the immediate reaction is to ignore risk management. Should risk management be done without budget, it will automatically be considered overage, and can then be perceived negatively. Risk management should have its own budget which gives a clear guideline when it comes to planning risks management and taking decisions on how you are going to act on each risks you identify.

In conclusion

This is a summary of course, there is much more to risk management, but hopefully this will shed some light for those who are still confused by the idea of risk management.

Call this a cheat sheet 😉