Copyright © 2009 PMI RiskSIGNovember 5-6, 2009 “Project Risk Management – An International Perspective” RiskSIG - Advancing the State of the Art A collaboration.

Slides:



Advertisements
Similar presentations
Chapter 12 Health Care Information Systems: A Practical Approach for Health Care Management 2nd Edition Wager ~ Lee ~ Glaser.
Advertisements

Program Management Overview (An Introduction)
IT Governance and Management
Leadership in the Baldrige Criteria
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
4 4 By: A. Shukr, M. Alnouri. Many new project managers have trouble looking at the “big picture” and want to focus on too many details. Project managers.
project management office(PMO)
Purpose of the Standards
Information Technology Project Management, Sixth Edition Note: See the text itself for full citations.
Project Management Framework. PMBOK ® Guide, Third Edition.
PRESENTED BY TRUST THOMAS EROMOSELE STUDENT NO:
Oversight CHAPTER SIXTEEN Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Opportunities & Implications for Turkish Organisations & Projects
Privileged and Confidential Strategic Approach to Asset Management Presented to October Urban Water Council Regional Seminar.
Project Management Lecture 5+6 MS Saba Sahar.
Information Technology Audit
Project Management Fundamentals Project Organization and Integration
Project Human Resource Management
What is Business Analysis Planning & Monitoring?
Challenges Faced in Developing Audit Plans and Programs 21 st March, 2013.
PMP® Exam Preparation Course
Project Management: Still More Art Than Science Presented By Donald W. Larson AC Bronze, CL June 6, 2007.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Adaptive Processes Project Management Body of Knowledge
Organize to improve Data Quality Data Quality?. © 2012 GS1 To fully exploit and utilize the data available, a strategic approach to data governance at.
Introduction PMBOK® © Whizlabs.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 3 Project Management for Strategic Goal Achievement.
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
Application Form Part 1, Sections 4-9 How to Apply Seminar 16 th September 2010 – Copenhagen Kirsti Mijnhijmer.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
CSI - Introduction General Understanding. What is ITSM and what is its Value? ITSM is a set of specialized organizational capabilities for providing value.
Copyright 2009  Describe the five project management (PM) process groups, the typical level of activity for each, and the interactions among them  Understand.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Welcome to Session 3 – Project Management Process Overview
Chapter 3 Strategic Information Systems Planning.
1 Organizational Project Management Maturity Model (OPM3 ) استاد مربوطه : جناب آقای دکتر ساعدی جناب آقای دکتر ساعدی تهیه و تنظیم : ارمغان خلیل زادگان ارمغان.
District Leadership Module Preview This PowerPoint provides a sample of the District Leadership Module PowerPoint. The actual Overview PowerPoint is 73.
Proventures reconnect session on Project Portfolio Management (PPM)
MITM743 Advanced Project Management Dr. Abdul Rahim Ahmad Assoc. Professor College of IT, UNITEN Project Management Body of Knowledge PMBOK 4 (Section2)
Kathy Corbiere Service Delivery and Performance Commission
Project Management Training
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
CYSSC - Cluster 2.0 Partner Management Final Deliverable High Sensitivity Sep 2, 2011 Cluster 2.0 Project Team.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Project Management Institute, Northeast Florida Chapter Learning Materials PMI PMBOK(R) Guide A Guide to the Project Management Body of Knowledge Rita.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
The Project Management Process Groups
Info-Tech Research Group1 Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
Info-Tech Research Group1 Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
The Strategic Execution Ecosystem Putting It All Together Brian Grafsgaard, CSM, PMP, PgMP, PfMP Consulting Practice Director Q Consulting 600 Highway.
Agenda  Purpose  Processes  Deliverables  Executing Activities 4.3.
Phase-1: Prepare for the Change Why stepping back and preparing for the change is so important to successful adoption: Uniform and effective change adoption.
PRINCE2 and the PMBoK guide
Process and customizations
Attend|Learn|Grow Push Your Professional Growth to the Next Level
Project Planning: Scope and the Work Breakdown Structure
Start End What is a project? Definition from PMBOK -
Project Human Resource Management
Project Management (x470)
Project Integration Management
Project Management Processes
ITSM Governance is Imperative to Succeed
Establish Process Governance
Who Wants to be a PMP? Pre-Course Game 3
UNIT – OPERATION STRATEGY
Establishing a Strategic Process Roadmap
Bridging the ITSM Information Gap
Bridging the ITSM Information Gap
Presentation transcript:

Copyright © 2009 PMI RiskSIGNovember 5-6, 2009 “Project Risk Management – An International Perspective” RiskSIG - Advancing the State of the Art A collaboration of the PMI, Rome Italy Chapter and the RiskSIG

Slide 2November 5-6, 2009 Copyright © 2009 PMI RiskSIG Organizational Project Risk Management u Using PMI ® ’s Latest Standards

Slide 3November 5-6, 2009 Copyright © 2009 PMI RiskSIG Objectives u Understand the characteristics of portfolios, programs and projects that affect risk management u Develop the basis of an Organizational Project Risk Management model

Slide 4November 5-6, 2009 Copyright © 2009 PMI RiskSIG Discovering Organizational Project Management The application of knowledge, skills, tools and techniques to organizational management, as well as to project, program and portfolio activities to achieve the aims of the organization through projects.

Slide 5November 5-6, 2009 Copyright © 2009 PMI RiskSIG Organizational Project Risk Management u The integrated set of coherent risk management practices within the organizational project management environment  It is the rock on which to build the separate risk management policies and practices for each domain

Slide 6November 5-6, 2009 Copyright © 2009 PMI RiskSIG Agenda u Structural view u Risk Management across all three domains  Portfolios, programs and projects and the interdependencies u A model to link and align the different domain risk management processes and activities

Slide 7November 5-6, 2009 Copyright © 2009 PMI RiskSIG The Structural View u Overview of the domains: portfolio, program, project  link to mission, vision and action u Top-down view of the scope of responsibilities  Aligning the domains

Slide 8November 5-6, 2009 Copyright © 2009 PMI RiskSIG

Slide 9November 5-6, 2009 Copyright © 2009 PMI RiskSIG

Slide 10November 5-6, 2009 Copyright © 2009 PMI RiskSIG

Slide 11November 5-6, 2009 Copyright © 2009 PMI RiskSIG Understanding the Domains: Portfolios and Programs The overall intention is to achieve a value-added change u Project Portfolio Management  aims at strategic objectives. It charters… u Program Management  to provide the benefits that the strategy requires. This domain charters…

Slide 12November 5-6, 2009 Copyright © 2009 PMI RiskSIG Understanding the Domains: Projects … and Operations u Project Management  to create the deliverables defined within the specification of the corresponding program component. All of these lead to… u Operations,  to provide ongoing value-added service to the customer based on the capabilities and deliverables originating from the three other domains.

Slide 13November 5-6, 2009 Copyright © 2009 PMI RiskSIG Domain Neighbourhood Terminology Portfolio Program Project Component level Component level Sponsor level Sponsor level u Component level and Sponsor level

Slide 14November 5-6, 2009 Copyright © 2009 PMI RiskSIG The World of Organizational Change Management u The basis for change:  Vision – what the end state will look like  Mission – what needs to be achieved  Action – what needs to be done u Two additional definitions are also needed:  Governance – how it needs to be controlled  Objective – a description of how success will be evaluated. This is normally based on the mission statement, with the addition of success metrics.

Slide 15November 5-6, 2009 Copyright © 2009 PMI RiskSIG The World of Organizational Project Management The OPM environment is controlled by five interconnected systems 1.Strategy, rules and vision.  The ultimate authority 2.Planning for organizational change: defining the mission.  Planning to ensure long term viability. 3.Operational control.  Regulating tactical activities. 4.Monitoring and reporting.  Information collection and initial processing. 5.Action.  Planning and implementation to achieve the mission.

Slide 16November 5-6, 2009 Copyright © 2009 PMI RiskSIG Key Messages on Structure

Slide 17November 5-6, 2009 Copyright © 2009 PMI RiskSIG Message (1 of 2) u The dominion of each domain  Effective allocation of responsibilities and teamwork requires a clear definition of the type of outcome required from the work: Project Portfolio Management aims at strategic objectives. Program Management provides the benefits that the strategy requires. Project Management creates the deliverables defined within the specification of the corresponding program component. Operations provides ongoing value-added service to the customer based on the capabilities and deliverables originating from the three other domains.

Slide 18November 5-6, 2009 Copyright © 2009 PMI RiskSIG Message (2 of 2) u Visualizing the outcome  A coherent picture of what is required and how it is to be achieved requires a structured approach: Vision – what the end state will look like. Mission – what needs to be achieved. Action – what needs to be done

Slide 19November 5-6, 2009 Copyright © 2009 PMI RiskSIG Implications for Risk Management u The risks are  in the components,  between the components,  and inherent to the overall structure and content Senior Management Portfolio Program ProjectNon-ProjectProject Program Project Portfolio Project

Slide 20November 5-6, 2009 Copyright © 2009 PMI RiskSIG Domain Project Risk Management u Defining risk consistently for all domains u Risks in portfolios  Linking to programs or projects u Risk in programs  Linking back to portfolios  Linking to projects u Risks in projects  Linking back to programs or portfolios u Risk sharing between domains

Slide 21November 5-6, 2009 Copyright © 2009 PMI RiskSIG Defining Risk u Risk is “significant uncertainty” (Thank you David Hillson!)  What is significant depends on what matters to you u For portfolios, it is achieving the strategy u For programs, it is the outcomes and their benefits u For projects, it is related to the deliverables

Slide 22November 5-6, 2009 Copyright © 2009 PMI RiskSIG A risk is … u An event or series of events that could affect the success of the endeavour  the effect is measured in terms of the effect on the corresponding success parameters … for better or for worse

Slide 23November 5-6, 2009 Copyright © 2009 PMI RiskSIG Types of Portfolio Risk u Structural risks  From the composition of the portfolio Interactions, resources, etc.  From the way the portfolio is managed governance risks – maybe a separate category u Component risks  at the strategic portfolio level  or escalated from the program domain u Overall risks  The conjugated effect of the risks they do not even sum statistically!

Slide 24November 5-6, 2009 Copyright © 2009 PMI RiskSIG Charting Portfolio Risks

Slide 25November 5-6, 2009 Copyright © 2009 PMI RiskSIG Steps in Portfolio Risk Management

Slide 26November 5-6, 2009 Copyright © 2009 PMI RiskSIG Portfolio Processes and Risk Management

Slide 27November 5-6, 2009 Copyright © 2009 PMI RiskSIG Linking Portfolio Management to the other Domains Identify Portfolio Risks Develop Portfolio Risk Responses Monitor and Control Portfolio Risks Authorize Components Component Execution & Reporting

Slide 28November 5-6, 2009 Copyright © 2009 PMI RiskSIG The Missing Link? u Develop Portfolio Risk Responses may need action from a component  There is a need for the following output parameter: Directives Regarding Components This comes from Review and Report Portfolio Performance! –It is not clear how Develop Portfolio Risk Responses communicates with this process It also needs to be an input to the Program and the Project Management change control process

Slide 29November 5-6, 2009 Copyright © 2009 PMI RiskSIG Program Risks u Business environment  Any conflict with the portfolio? u Portfolio-related  Whose priority matters? u Program-level (structural)  Related to the architecture, “roadmap” and benefits map u Impacts on benefits and outcomes  The combined effects of component risks u Operations level  Related to transitioning components

Slide 30November 5-6, 2009 Copyright © 2009 PMI RiskSIG Charting Program Risks

Slide 31November 5-6, 2009 Copyright © 2009 PMI RiskSIG Linking to the Program Components u In the same way as for portfolios, the program-level risk response planning process may have to invoke change control within its components  In this case by invoking project-level Integrated Change Control or the Control Scope process Direct and Manage Program Execution needs an extra Output: Program Component Directive –That becomes an Input for the component-level change management process

Slide 32November 5-6, 2009 Copyright © 2009 PMI RiskSIG Project Risks u From the point of view of integrated risk management it is important that the project manager has  Full authority of the risks within their level of authority  An understanding of the success criteria at the sponsor’s level  The ability to escalate effectively any issues outside their control

Slide 33November 5-6, 2009 Copyright © 2009 PMI RiskSIG Delegated Risks u Risks can be delegated to the components:  These are risks the domain manager feels would be better dealt with at the component level  There needs to be a delegation (and negotiation) process for the component manager to incorporate the work into their scope Once again this should be included in the change management process at the component level

Slide 34November 5-6, 2009 Copyright © 2009 PMI RiskSIG Escalated Risks u Effective communication must be two-way  In the same way that risks and actions can be delegated to components,  the components must have the ability to escalate issues and requests back to the sponsor-level

Slide 35November 5-6, 2009 Copyright © 2009 PMI RiskSIG Linking back from the Program u Some program-level decisions or actions may be beyond the level of authority of the component manager  This can be linked through the Program Issues Register – which is managed at the program level But Provide Governance Oversight needs to have a new parameter, Escalation Request as an Output –and this needs to be an Input to a Portfolio Management Process (Review and Report Portfolio Performance)

Slide 36November 5-6, 2009 Copyright © 2009 PMI RiskSIG Project Escalation u In the same way as for programs, project managers need to be able to request support from the sponsor-level  e.g. by issuing an Escalation Request  This is missing from the PMBOK ® Guide There is no coordinated issue management process Direct and Manage Project Execution could be the right place for it

Slide 37November 5-6, 2009 Copyright © 2009 PMI RiskSIG Organizational Project Risk Management u Aligning domain risks u Process communications between domains u Risk consolidation between domains u Future work

Slide 38November 5-6, 2009 Copyright © 2009 PMI RiskSIG Alignment of Risks u In order to allow each domain to be “interested” in the risks of the related domains, their risks must be aligned u This requires that their definitions of “significance” should be consistent with each other

Slide 39November 5-6, 2009 Copyright © 2009 PMI RiskSIG Is my domain’s significance relevant to yours? Aligning Success Criteria Vision Project Mgmt Vision Program Mgmt Mission Program Mgmt Mission Portfolio Mgmt Action Program Mgmt Action Portfolio Mgmt Vision Org. Strategy Mission Project Mgmt Action Project Mgmt

Slide 40November 5-6, 2009 Copyright © 2009 PMI RiskSIG Delegation and Escalation

Slide 41November 5-6, 2009 Copyright © 2009 PMI RiskSIG Delegation between Domains u Where should the other domain’s risk “hand-offs” be handled initially? as a Portfolio or Program Component Directive  Out from? Governance (portfolios) or Integration Management (programs)  In to? I suggested Change Management  Effect The delegator remains accountable for the risk at their level

Slide 42November 5-6, 2009 Copyright © 2009 PMI RiskSIG Escalation between Domains u The PMBOK ® Guide does not provide projects with any links to intractable issues  This would belong in Integration to issue a Project Escalation Request u Programs do have an issue management process  Governance needs to be able to issue a Program Escalation Request Both of which are MISSING from the standards

Slide 43November 5-6, 2009 Copyright © 2009 PMI RiskSIG Future Work: Domain Consolidation u “No domain is an island”  Consolidating risks up the model Consolidating “composite” risks Consolidating contingency Overall domain risk u Here are 3 questions I will leave you with  I do not have the answers

Slide 44November 5-6, 2009 Copyright © 2009 PMI RiskSIG Consolidating Component Risks and their Causes u How to address risks in several components that, individually are “not significant”  But could sum to be significant  Depend on the same root cause u Asking component managers for too much risk information leads to overload  Too little and you miss these “composite” risks

Slide 45November 5-6, 2009 Copyright © 2009 PMI RiskSIG Consolidating Contingency u Consider contingency buffers … only those rolled-up from the project level  How should the program portfolio contingency buffers be calculated?

Slide 46November 5-6, 2009 Copyright © 2009 PMI RiskSIG Overall Risk Exposure u Assuming you know the risk profile for each component Impact-probability distribution  How should you calculate the sponsor-level overall risk

Slide 47November 5-6, 2009 Copyright © 2009 PMI RiskSIG Final Word u Align the levels  Vision, mission, action u Link the processes  across the levels u Consolidate the overall risk  From one level to the next

Slide 48November 5-6, 2009 Copyright © 2009 PMI RiskSIG Time for Questions Crispin (“Kik”) Piney, B.Sc., PgMP +33 (0)

Copyright © 2009 PMI RiskSIGNovember 5-6, 2009 “Project Risk Management – An International Perspective” RiskSIG - Advancing the State of the Art A collaboration of the PMI, Rome Italy Chapter and the RiskSIG