Scribd
Upload
5 views3 pages

Effective Program Risk Management Guide

The document discusses establishing a robust risk management mechanism for a project. It outlines identifying risks across dimensions like schedule, scope, quality, process and people. It also discusses assessing and managing risks to enable predictable delivery.

Uploaded by

Harisankar Das
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views3 pages

Effective Program Risk Management Guide

The document discusses establishing a robust risk management mechanism for a project. It outlines identifying risks across dimensions like schedule, scope, quality, process and people. It also discusses assessing and managing risks to enable predictable delivery.

Uploaded by

Harisankar Das
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

PROGRAM RISK MANAGEMENT

PROGRAM RISK MANAGEMENT


A project can succeed only if there is a robust risk management mechanism

Approach

Establish Risk identification and tracking mechanism

Establish governance mechanism to review and report risks

Reduced Risks
• Best mitigation steps

Identify Risks Assess Risks Manage Risks Predictable Delivery


across multiple • Assess risk • Plan mitigations, • Time to market
dimensions potential for the establish
project communications
• Schedule, Scope, and constantly
Quality, Process, revisit risks
People, etc
RISK MANAGEMENT - DIMENSIONS
SCHEDULE QUALITY PROCESS Others (governance, utilization, dependency,
etc)
[Link] date will be [Link] design reviews [Link] of Project
affected management/Agile practices is low [Link] with other systems
[Link] not signed off
[Link] in meeting the [Link] Sprint planning and [Link] party interfaces may not be ready on
timelines for delivery to [Link] many code review comments grooming of stories time
testing team from customer
[Link] scientific estimation [Link] availability of required environments
[Link] may not happen in [Link] delivery delayed to testing methodology used
time phase [Link] support for customer for
[Link] much spill over of stories to clarifications/signoffs
SCOPE [Link] test strategy next sprint
[Link] automation - DevOps, Software
[Link] scope changes [Link] Unit testing engineering life cycle activities, etc

[Link] are not clear [Link] much defects leaking to PEOPLE [Link] Governance mechanism is not robust
testing phase
[Link] clarity on NFRs [Link] mismatch/low skill levels with [Link] Knowledge Transfer in Transition
[Link] practices maturity is many team members programs
[Link] criteria not low
clear [Link] productivity/velocity [Link] utilisation of people
[Link] NFR testing strategy
[Link] are changed [Link] many Unplanned leaves [Link] Kickoff not done for the project
inbetween sprint cycle 10. Low automated test coverage
[Link] is high

You might also like