• Home
  • Project Delivery
  • Project Management Consultants
  • Agile Services
  • Team Training
  • Training
  • Services

PM Partners

  • What We Do
  • Success Stories
  • Insights
  • Contact
  • Training

    TRAINING DELIVERY

    • Course List
    • Course Schedule
    • eLearning Courses
    • Specials and Promos

    LEARNING PATHWAYS

    • Scrum and Agile
    • Project and Programme
    • Business Analysis

    MOST POPULAR

    • Scrum Master Certified (SMC™)
    • Agile Project Management
    • PRINCE2®
    • Project Management Fundamentals
    • Business Analysis Fundamentals
    • Leading SAFe® 5.1
  • Project Delivery
  • Project Management Consultants
  • Agile Services
  • Team Training
  • Home
  • Insights
  • Risky Business: The Project Manager and Project Risk
April 13, 2021

Risky Business: The Project Manager and Project Risk

Risky Business: The Project Manager and Project Risk

Wednesday, 01 January 2020 / Published in Uncategorised

Projects, by definition, are uncertain. To be successful, a project manager needs to address risk management proactively and consistently throughout a project. A risk if it occurs, has a positive (opportunity) or negative (threat) effect on one or more project objectives such as scope, schedule, cost and quality.

Risk management should be an integral part of every project undertaken. Areas of risk to be addressed include the:

  • Business environment
  • Marketplace
  • Execution approaches (e.g agile versus traditional)
  • Availability and quality of resources
  • Development of deliverables

6 Steps to Successful Risk Management

  1. The extent, type and visibility of risk management on a project needs to be aligned with both the individual risks and the importance of the project to the organisation. How to manage risk is typically encapsulated by the project manager in a risk management plan or risk management approach, or even by simply collating a checklist to manage and control project risk.

As a guide, a risk management plan (or equivalent) includes:

  • Methodology (including tools and techniques)
  • Roles and responsibilities
  • Risk categorisation and severity
  • Budgeting
  • Timing
  • Definitions of risk probability and impact
  • Tracking
  1. Identification of risk is an iterative process – it is not just performed once off at the beginning of a project. New risks may evolve throughout a project, existing risks may need to be revised in terms of probability and impact, other risks happen.

Risks are logged in a risk register for subsequent management control and visibility. A clear expression of each risk is logged with its cause, the likely event and the effect the risk could have on the project.

Whilst the project manager is key to ensuring risks are defined and documented, remember that participants in risk identification should include project team members, customers, subject matter experts, other project managers, stakeholders and risk management experts. Everyone involved in the project should be encouraged to identify potential risks.

  1. Analyse. Risk analysis can be viewed from 2 aspects: qualitative and quantitative. Qualitative analysis is a quick and cost-effective way of establishing risk priority by assessing and combining probability and impact.

Quantitative analysis takes the resulting prioritised risks and looks at numerically analysing the effect on overall project objectives. The risk register is updated with the results from the analyses.

  1. Response. Once a risk has been identified and analysed, a decision must be made concerning which is the most appropriate risk response. Responses to threats include escalate, mitigate, avoid, transfer or accept. Responses to opportunities include escalate, exploit, share, enhance and accept.

A response plan can subsequently be embedded within the project plan and can then be actioned as appropriate. Where appropriate, contingent response strategies may need to be developed; these are often referred to as contingency plans or fallback plans and include identified trigger events that set the plan in effect.

  1. Implement. Risk responses, once agreed upon, need to be executed in order to address overall project risk exposure, minimise project threats and maximise project opportunities.

Often time and energy are expended on identifying and analysing risks, then documenting responses in a risk register, but no action is taken to implement the response. The implement step is important to ensure that risks are being managed proactively.

  1. Project managers need to monitor risks just as they track project progress. Throughout the project a project manager is continually alert to monitoring risk response plans, tracking identified risks, identifying and analysing new risks and the evaluation of the effectiveness of risk management for the project.

A Project Manager’s role is to manage risk within their projects in an integrated, iterative and systematic manner. By doing so they are required to ensure threats have a reduced impact on the project outcome, whilst at the same time improving the likelihood of opportunities for the project.

If your organisation requires assistance in executing complex programmes or transformation, contact us today on 1300 70 13 14.

What you can read next

Unearthing the PRINCE2 methodology
Making Agile Work
9 Tips for Embracing an Agile Mindset

GENERAL ENQUIRY
1300 70 13 14

CONTACT US
Send a message

FOLLOW US

Registered Project Management Education Provider

PM-Partners group is a DASA training partner, a Project Management Institute (PMI)® Global Registered Education Provider (R.E.P), an APMG-International Accredited Training Organisation (ATO), an AXELOS Certified Partner, an accredited partner of PeopleCert (Partner ID: 3800), an Endorsed Education Provider™ (EEP™) for the International Institute for Business Analysis™ (IIBA®), a Scaled Agile Silver Partner and a Microsoft® EPM Solution Partner. PMI, CAPM, Certified Associate in Project Management (CAPM), PMP, Project Management Professional (PMP) and PMBOK are registered marks of the Project Management Institute, Inc. PRINCE2®, AgileSHIFT®, MSP®, P3O®, MoP®, ITIL®, PRINCE2 Agile®, P3M3® are registered trade marks of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved. The Certified Partner, Partner Programme Logo and Swirl Logo™ are trade marks of AXELOS Limited, used under permission of AXELOS Limited. All rights reserved. AgilePM®, AgilePgM®, AgileBA® and DSDM® are registered trademarks of Agile Business Consortium Limited. All rights reserved. APMG International Change Management, APMG International Facilitation and APMG International Lean Six Sigma are trademarks of The APM Group Limited. All rights reserved. The APMG-International AgilePM, AgilePgM, AgileBA, Change Management, Managing Benefits, Facilitation, Lean Six Sigma and Swirl Device logos are trademarks of The APM Group Limited, used under permission of The APM Group Limited. All rights reservedSMC™ and SPOC™ are trademarks of SCRUMstudy. Scaled Agile Framework® and SAFe® are registered trade marks of Scaled Agile, Inc. IIBA®, the IIBA® logo, BABOK® Guide and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis. CBAP® and CCBA® are registered certification marks owned by International Institute of Business Analysis. Certified Business Analysis Professional™, Certification of Competency in Business Analysis™, Endorsed Education Provider™, EEP™ and the EEP logo are trademarks owned by International Institute of Business Analysis.

Privacy Policy | Sitemap | Timesheets | Terms & Conditions
Copyright © 1996-2021 PM-Partners Group. Delivery Advisory Capability. All Rights Reserved.

TOP