Risks, Opportunities, Issues - Management and Analysis Form

Risks, Opportunities, Issues -Management and
Analysis Form
Project Name: PEG Project risks - pooled as Learning/Reference
Project Manager: Gopal Ranaj
Delivery Head: Gopal Ranjan
PQAL: NA
Version History
[This section should provide a history of changes to the document. Keep the latest version on the top]
Date Version Update Author Reviewer
19-Sep-18 1.0 As per latest LV MK
tempalte
14-Mar-19 2.0 1. Added Risks of AK AD
New Projects
2. Updated Risk
Status of existing
database
28-Feb-20 3.0 1. Added Risks of AK AD

New Projects
2. Updated Risk
Status of existing
database
26-Aug-20 4.0 New Risks updated VS MK

SEPG changes as
PEG, Sorted on date/
Project
Note:Risks are discussed during SMR, which is typically on monthly basis.

If there is no update since a long time (refer Last Update Date), PM is required to check with the SMR ppt Risk status as w
In SMR ppt, it is suggested to "Take the information from Project risk register/ Project Plan or provide link to the risk "regist
n on the top]
Approver
CG
CG
CG
GR
the SMR ppt Risk status as well.

r provide link to the risk "register file.
Project Risk Management Form Project Manager Delivery head
name
VFS24X7 VFS24X7_ RiskRegister Jitendra Patkar Gautam Makkar

The Conference Board TCB_CFD_Risk Amit Chauhan Sandeep Arora

VFS24X7 Management Form
VFS24X7_ RiskRegister Jitendra Patkar Gautam Makkar
nSights \ TruBI Implementation TruBI_Imp_Risk_and_Iss Harshula Tulapurkar Hemraj S.
NAPF Support 2020 ue_Register
SPoFNAPFSU20001_Risk Mayur Kshirsagar Gautam Makkar
NAPF Support 2020 Register
SPoFNAPFSU20001_Risk Mayur Kshirsagar Gautam Makkar
UNICEF Register
Unicef TP_Risk Register Ashwini Tamane Gautam Makkar
UNICEF Unicef TP_Risk Register Ashwini Tamane Gautam Makkar
UNICEF-EPP2.0 UNICEF-EPP2.0_Risk Ashwini Tamane Gautam Makkar
FAO SSC Register
FAO Amit Samaiya Sonali Karnik
ISG-CQ Module SSC_Risk_and_Issue_Re
ISG-CQ module_Risk Radha Bhiwandkar Amit Dalvi
The Conference Board gister_
management form
TCB_CFD_Risk Amit Chauhan Sandeep Arora
UNICEF-EPP2.0 Management Form
UNICEF-EPP2.0_Risk Ashwini Tamane Gautam Makkar
FAO SSC Register
UNICEF-EPP2.0 SSC_Risk_and_Issue_Re
UNICEF-EPP2.0 gister_
Register
FAO SSC Register
IOM Intranet Phase-2 SSC_Risk_and_Issue_Re
IOMINPH2_RiskRegister Yogesh Govekar Sonali Karnik
Cash forecasting gister_
UNICEF_Riskregister Ashwini Tamane Gautam Makkar
SPADES 3 SPADES_RiskRegister Milesh Malji Gautam Makkar
ePHR Lite ePHR Lite - Risk Register Raghavendra Gautam Makkar
ePHR Lite ePHR Lite - Risk Register Deshpande
Raghavendra Gautam Makkar
IOM Intranet Phase-2 IOMINPH2_RiskRegister Deshpande
Yogesh Govekar Sonali Karnik
IOM Intranet Phase-2 IOMINPH2_RiskRegister Yogesh Govekar Sonali Karnik
IOM Intranet Phase-2 IOMINPH2_RiskRegister Yogesh Govekar Sonali Karnik
DDSR S08WTODDSR17_Risks Jitendra Patkar Gautam Makkar
nSights \ TruBI Implementation (2)
TruBI_Imp_Risk_and_Iss Harshula Tulapurkar Hemraj S.
nSights \ TruBI Implementation ue_Register
AGIMS ue_Register
S08WTOAGIMS17_Risks Jitendra Patkar Gautam Makkar
DLR UAE Identify New
DLRIdentify_Risk Sandeep V R Ashokkumar
AGIMS Register
AGIMS New
DDSR New
S08WTODDSR17_Risks Jitendra Patkar Gautam Makkar
DDSR (2)
nSights \ TruBI Implementation (2)
UN Water SDg 6 Dataportal ue_Register
UN Water SDg 6 Sonali Karnik Sachin Rane
UN Water SDg 6 Dataportal Dataportal
TCB Dataportal
TCB_CFD_RiskManagem Amit Chauhan Sandeep Arora
ent Form
The Conference Board TCB_CFD_Risk Amit Chauhan Sandeep Arora
ISG-CQ Module Management
ISG-CQ Form
module_Risk Radha Bhiwandkar Amit Dalvi
Axis Bank Trade Finance Implementation management form
AxisBank_RiskRegister Himanshu Pandey Amit Sharma
Axis Bank Trade Finance Implementation AxisBank_RiskRegister Himanshu Pandey Amit Sharma
Axis Bank Trade Finance Implementation AxisBank Himanshu Pandey Amit Sharma
DDSR S08WTODDSR17_Risks Jitendra Patkar Gautam Makkar
DDSR (2)
Axis Bank Trade Finance Implementation (2)
De La Rue - BSP Phase - 2 S08DLRBSP17001_Risk_ Gautam Makker ---
De La Rue - BSP Phase - 2 Register
S08DLRBSP17001_Risk_ Gautam Makker ---
Axis Bank Trade Finance Implementation Register
nSights \ TruBI Implementation nSights \ TruBI Harshula Tulapurkar Jigisha S.
nSights \ TruBI Implementation Implementation
nSights \ TruBI Harshula Tulapurkar Jigisha S.
ISG-CQ Module Implementation
DLR UAE Identify management form
DLR UAE Identify Register
GHB II Register
GHB_Risk Management Amit Dalvi Sachin Rane
GHB II Form
GHB II Form
GHB II Form
Cash forecasting Form
UNICEF_CF UNICEF_CF_Risk_Regist Bobby Prasad Subu Achyutuni
Cash forecasting er
Cash forecasting UNICEF_Riskregister Ashwini Tamane Gautam Makkar
UNICEF_CF er
UNICEF_CF_Risk_Regist Bobby Prasad Subu Achyutuni
Cash forecasting er
Cash forecasting er
Cash forecasting UNICEF_Riskregister Ashwini Tamane Gautam Makkar
UNICEF_CF er
UNICEF_CF_Risk_Regist Bobby Prasad Subu Achyutuni
De La Rue - BSP Phase - 2 er
UNICEF Mozambique Register
UNICEF MOZ-Risk Sonali Karnik Subu Achyutuni
Hotus Implementation Register
HOTUSGOV-RiskRegister Sonali Karnik Subu Achyutuni
ISG-CQ Module ISG-CQ module_Risk Radha Bhiwandkar Amit Dalvi
VFS24X7 management form
VFS24X7_ RiskRegister Jitendra Patkar Gautam Makkar
DLR UAE Certify DLRUAECert_Risk Sheetal Par R Ashokkumar
DLR UAE Certify Register
DLRUAECert_Risk Sheetal Par R Ashokkumar
DLR UAE Identify Register
LMS Support Register
LMS Support Harish Kohli R.Sethumadhavan
UNICEF Mozambique UNICEF MOZ-Risk Sonali Karnik Subu Achyutuni
Cash forecasting Register
CapitalFirst_LAP_Bill er
CapitalFirst_LAP_Bill_Ris Pankaj Gupta Amit Sharma
Hotus Implementation kReigester
UNICEF Mozambique UNICEF MOZ-Risk Sonali Karnik Subu Achyutuni
KPI Tool Register
KPI_Risk Management Nishigandha G. Amit Dalvi
Form
DLR UAE Certify DLRUAECert_Risk Sheetal Par R Ashokkumar
DLR UAE Certify Register
DLRUAECert_Risk Sheetal Par R Ashokkumar
KPI Tool Register
KPI Tool Form
KPI Tool Form
DDSR Form
DDSR3 (2)
DDSR3_Risk Register Sheetal Subu Achyutuni
Parekh/Jitendra Patkar
DDSR3 DDSR3_Risk Register Sheetal Subu Achyutuni
TCB TCB_CFD_RiskManagem Parekh/Jitendra
Sandeep VaradkarPatkar Subu Achyutuni
The Conference Board ent Form
TCB_CFD_Risk Amit Chauhan Sandeep Arora
Hotus Implementation Management Form
Hotus Implementation HOTUSGOV-RiskRegister Sonali Karnik Subu Achyutuni
Hotus Implementation HOTUSGOV-RiskRegister Sonali Karnik Subu Achyutuni
UN Water SDg 6 Dataportal UN Water SDg 6 Sonali Karnik Sachin Rane
UNICEF Mozambique Dataportal
UNICEF MOZ-Risk Sonali Karnik Subu Achyutuni
KPI Tool Register
KPI Tool Form
KPI Tool Form
De La Rue - BSP Phase - 2 Form
De La Rue - BSP Phase - Gautam Makker Subu Achyutuni
ISG-CQ Module 2
nSight Implementation project management form
VFS24X7_ RiskRegister Shahnawaz Ahmed Shashi Bhargawa
DDSR3 DDSR3_Risk Register Sheetal Subu Achyutuni
De La Rue - BSP Phase - 2 S08DLRBSP17001_Risk_ Parekh/Jitendra
Gautam Makker Patkar ---
De La Rue - BSP Phase - 2 2
ISG-CQ Module 2
DDSR3 management form
DDSR3_Risk Register Sheetal Subu Achyutuni
NAPF Support 2017 NAPF Risk Register Parekh/Jitendra
Milesh Malji Patkar Subu Achyutuni
NAPF Support 2017 NAPF Risk Register Milesh Malji Subu Achyutuni
De La Rue - BSP Phase - 2 S08DLRBSP17001_Risk_ Gautam Makker ---
LMS Support 2
Pacific Life ACG S08PLMIG17001_Risk_R Pankaj kularni Subu Achyutuni
Pacific Life ACG egister
S08PLMIG17001_Risk_R Pankaj kularni Subu Achyutuni
De La Rue - BSP Phase - 2 egister
Libra Replacement 2
S07HSFLibRep161_RiskR Milesh Malji Subu Achyutuni
NAPF Support 2017 egister_F0102
NAPF Risk Register Milesh Malji Subu Achyutuni
Libra Replacement egister
Pacific Life ACG egister_F0102
LMS Support egister
ISG-CQ Module egister
BATA ODS management form
BATA_ODS_Risk Niraj Nagrecha Amit Sharma
BATA ODS Management_New
The conference board Management_New
TCB_CFD_Risk sandip varadkar Subu Achyutuni
NAPF Support 2017 Management Form
BATA ODS BATA_ODS_Risk Niraj Nagrecha Amit Sharma
NAPF Support 2017 Management_New
NAPF Support 2017 NAPF Risk Register Milesh Malji Subu Achyutuni
The conference board TCB_CFD_Risk sandip varadkar Subu Achyutuni
Libra Replacement Management Form
Libra Replacement egister_F0102
BATA ODS egister_F0102
10BUBHDEVNSEB - UKMU Development Management_New
Development NSEB Santosh Dalvi R. Ashok Kumar
NSEB Scrum
10BUBHDEVNSEB - UKMU Development Scrum
NSEB Scrum
NSEB Scrum
LMS Support Scrum
10BAUFVTest1701 - Functional Validation - Functional_Validation_R Santosh Dalvi R. Ashok Kumar
Visual Cobol Upgrade
10BAUFVTest1701 - Functional Validation - isk register_V1
Functional_Validation_R Santosh Dalvi R. Ashok Kumar
Visual
Digital Cobol Upgrade
Dispute Settlement Registry isk register_V1
SWTODDSR15_Risk Sheetal Parekh Subu Ahyutuni
BATA ODS Register_New
Digital Dispute Settlement Registry Management_New
Digital Dispute Settlement Registry Register_New
Digital Dispute Settlement Registry Register_New
LMS Support Register_New
BATA ODS BATA_ODS_Risk Niraj Nagrecha Amit Sharma
VFS24X7 Management_New
VFS24X7_ RiskRegister Jitendra Patkar Subu Achyutuni
The conference board TCB_CFD_Risk sandip varadkar Subu Achyutuni
VFS24X7 Management Form
10BUBHDEVNSEB - UKMU Development Development NSEB Santosh Dalvi R. Ashok Kumar
NSEB Scrum
VFS24X7 Scrum
NSEB Scrum
LMS Support Scrum
NSEB Scrum
NSEB Scrum
NSEB Scrum
VFS24X7 Scrum
VFS24X7 VFS24X7_ RiskRegister Jitendra Patkar Subu Achyutuni
LMS Support LMS Support Harish Kohli R.Sethumadhavan
PQAL name Latest Risk Date of Risk Process Area / Process
update No. Identification Phase / Requirement
Functional Area
[Use Risk
Sofia Kunvar 10-Jun-20 13 10-Jun-20 CategoryRisks
Contract from Project execusion
Validation or
Sofia Kunvar 10-Jun-20 14 10-Jun-20 refer to/ it]
Resource Resource/
Infrasturcture Infrastructure
Vaishali Shirsat 27-Mar-20 4 6-Apr-20 Deployment and Impact of Covid-19
Sofia Kunvar 20-Mar-20 12 20-Mar-20 Support
Environment break out
Environment
Poonam Patil 27-Feb-20 6 31-Jan-20 Visualization Availability
Sofia Kunvar 27-Feb-20 1 1-Jan-20 Schedule Support, KVA
Sofia Kunvar 27-Feb-20 2 1-Jan-20 Integration development
Integration Testing
Sofia Kunvar 27-Feb-20 1 3-Dec-19 Resource / Resource/
Sofia Kunvar 27-Feb-20 2 3-Dec-19 Infrasturcture
Business Infrastructure
Budget and
Sofia Kunvar 27-Feb-20 3 3-Dec-19 (Budget/Costs)
Delivery Schedule
Deliverables
Sofia Kunvar 27-Feb-20 4 3-Dec-19 Delivery Deliverables
Sofia Kunvar 27-Feb-20 5 3-Dec-19 Delivery Clarifications/
Sofia Kunvar 27-Feb-20 6 3-Dec-19 Domain Questions
Data
Sofia Kunvar 27-Feb-20 3 22-Nov-19 Resource / Testing
Vaishali Shirsat 27-Feb-20 7 15-Nov-19 Infrasturcture
Delivery inexperince AWS
Bhagyashree 27-Feb-20 10 13-Nov-19 Resource / team
Availablity of
Jamkhandikar
Vaishali Shirsat 27-Feb-20 3 1-Nov-19 Infrasturctureand
Deployment required number of
PHP development
Sofia Kunvar 27-Feb-20 2 18-Oct-19 Support
Testing resources for
Quality Assurance
Vaishali Shirsat 27-Feb-20 2 11-Oct-19 Project development
Requirement
Sofia Kunvar 27-Feb-20 1 4-Oct-19 Management
Project Management
Project Scope
Sofia Kunvar 27-Feb-20 1 4-Oct-19 Management
Requirements Planning and
Project
Vaishali Shirsat 27-Feb-20 6 6-Sep-19 management
Delivery Verification
Requirements and
Dependent
Sofia Kunvar 27-Feb-20 4 19-Aug-19 Environment Sprint Planning
migration
Execution data
Sofia Kunvar 27-Feb-20 5 6-Aug-19 Resource / delay
Resource
Sofia Kunvar 3-Aug-19 11 3-Aug-19 Infrasturcture
Delivery Resource/
Sofia Kunvar 27-Feb-20 12 15-Jul-19 Project Infrastructure
Requirement
Sofia Kunvar 27-Feb-20 13 15-Jul-19 Management
Resource / Gathering
Technical
Sofia Kunvar 27-Feb-20 14 11-Jul-19 Infrastructure
Deployment and implementation
Requirement
Sofia Kunvar 27-Feb-20 15 11-Jul-19 Support
Deployment and Gathering
Development
Sofia Kunvar 27-Feb-20 1 21-Jun-19 Support
Deployment and Technical
Sofia Kunvar 27-Feb-20 2 21-Jun-19 Support
Environment implementation
Environment setup
Sofia Kunvar 27-Feb-20 3 21-Jun-19 Deployment and Development
Sofia Kunvar 29-May-19 10 29-May-19 Support
Delivery Resource/
Vaishali Shirsat 27-Feb-20 1 6-May-19 Schedule Infrastructure
Requirement
Vaishali Shirsat 27-Feb-20 2 6-May-19 Contract Risks Scope
Sofia Kunvar 27-Feb-20 1 3-May-19 Resource / Execution
Sofia Kunvar 27-Feb-20 2 3-May-19 Infrasturcture
Resource / Execution
Sofia Kunvar 27-Feb-20 3 3-May-19 Infrasturcture
Resource / Execution
Sofia Kunvar 27-Feb-20 23 16-Apr-19 Infrasturcture
Delivery Cost
Poonam Patil 27-Feb-20 5 5-Apr-19 Project client
Poonam Patil 27-Feb-20 3 4-Apr-19 Management
Domain communication
Requirement
Poonam Patil 27-Feb-20 4 4-Apr-19 Project Management
client
Sofia Kunvar 27-Feb-20 6 1-Apr-19 Management
Technology communication
Vaishali Shirsat 27-Feb-20 4 21-Feb-19 Requirements Requirements
Sofia Kunvar 27-Feb-20 3 1-Feb-19 management
Contract Risks management
Sofia Kunvar 27-Feb-20 1 16-Jan-19 Resource /
Sofia Kunvar 27-Feb-20 21 25-Dec-18 Infrasturcture
Testing Process
Sofia Kunvar 27-Feb-20 22 25-Dec-18 Business Requirement
Cost
Poonam Patil 27-Feb-20 2 19-Dec-18 (Budget/Costs)
Project Requirement
Poonam Patil 27-Feb-20 1 18-Dec-18 Management
Resource / Management
Project
Sofia Kunvar 1-Dec-18 8 1-Dec-18 Infrasturcture
Technology management
GIS Compatibility
Availability of UAT
Study the SDMX
Sofia Kunvar 1-Dec-18 5 28-Nov-18 Environment and Prod
Development and
Sofia Kunvar 1-Dec-18 6 28-Nov-18 Technology Environment
SME is needed for
Resource / implement as per
Sofia Kunvar 1-Dec-18 7 28-Nov-18 Data collection
Infrasturcture plan
Vaishali Shirsat 1-Feb-18 2 12-Nov-18 Functional and analysis
Migration of SME
existing data based
on new mapping
Vaishali Shirsat 27-Feb-20 2 12-Nov-18 Functional Migration of
Bhagyashree 27-Feb-20 9 8-Nov-18 Project existingresponses
Timely data based
Jamkhandikar
Vaishali Shirsat 27-Feb-20 7 2-Nov-18 Management
Project on
from new
Timely mapping
Client
responses
Vaishali Shirsat 27-Feb-20 8 2-Nov-18 Management
Resource / fromservers
Timely
The
The client
servers on
responses
should
Project
Infrasturcture queries,
be sign-offs
available as per
Vaishali Shirshat 2-Nov-18 7 2-Nov-18 from
should client
be on
Management
Resource / the project
Vaishali Shirshat 2-Nov-18 8 2-Nov-18 queries,
available sign-offs
as per
Infrasturcture timelines
Sofia Kunvar 27-Feb-20 19 1-Nov-18 Delivery the project
Atleast one existing
Sofia Kunvar 27-Feb-20 20 1-Nov-18 Schedule resource
timelinesshould
Resource
Requirements
have been a part of
Availability
Vaishali Shirsat 27-Feb-20 6 26-Oct-18 Schedule Requirements
gathering
the team for
gathering tobe
to be XI
CCN
Vaishali Shirshat 2-Nov-18 6 26-Oct-18 Schedule
completed
completed as per as per
Ashish Deshpande 27-Feb-20 13 20-Oct-18 Deployment plan
plan
Ashish Deshpande 27-Feb-20 14 20-Oct-18 and Support
Integration
Vaishali Shirsat 27-Feb-20 4 17-Oct-18 Schedule Customer should
Customer
have properto should
clarity
Vaishali Shirsat 27-Feb-20 5 17-Oct-18 Schedule RG
RG session
session to
have
on proper
the asasper
progress clarity
plan
Vaishali Shirshat 2-Nov-18 4 17-Oct-18 Schedule progress per
on
to the
requirements
cover 1 geo 1 at a
Vaishali Shirshat 2-Nov-18 5 17-Oct-18 Schedule plan to cover
requirements
time with allskilled
Vaishali Shirsat 27-Feb-20 1 15-Oct-18 Skills geo at a time
Technically with
Technically
products skilled
Vaishali Shirsat 27-Feb-20 2 15-Oct-18 Resource / of
all resources
products
Number of itshould
in in it
Infrasturcture of
be resources
available
resources to asbeper
Vaishali Shirsat 27-Feb-20 3 15-Oct-18 Technology For OCR, Forms
should
Number
available
needs tobe of per the
the requirements
as
be of
Vaishali Shirshat 2-Nov-18 1 15-Oct-18 Skills
Resource / available
resources
this projects
project plan
standardized as
to per
be
Vaishali Shirshat 2-Nov-18 2 15-Oct-18 For OCR, Forms
Infrasturcture the requirements
available as per
Vaishali Shirshat 2-Nov-18 3 15-Oct-18 Technology needs to be
Project of this
the project
projects
Requirement plan
Poonam Patil 19-Sep-18 2 19-Sep-18 standardized
Management
Project
Poonam Patil 19-Sep-18 1 18-Sep-18
Infrasturcture management
Bhagyashree 27-Feb-20 8 12-Sep-18 Resource / Key resource
Jamkhandikar
Vaishali Shirsat 27-Feb-20 2 20-Aug-18 Infrasturcture
Resource / availability
Project for the
Vaishali Shirsat 27-Feb-20 3 20-Aug-18 Infrasturcture
Resource / project deliverable
management
Project
Vaishali Shirsat 11-Jul-18 3 11-Jul-18 Infrasturcture
Project management
Achieve 75%
Vaishali Shirsat 11-Jul-18 4 11-Jul-18 Management
Project certainity foronallthe
Monitoring
Vaishali Shirsat 11-Jul-18 2 10-Jul-18 Management
Skills sub-processes
basis of actual
Key resource
Vaishali Shirsat 11-Jul-18 1 9-Jul-18 Project control limits
availability
Timely responses
Sofia Kunvar 27-Feb-20 5 21-Jun-18 Management
Schedule throughtout
from Client the and
Communication
Poonam Patil 27-Aug-18 5 21-Jun-18 Schedule project
Project planning and
Communication
Sofia Kunvar 27-Feb-20 6 15-Jun-18 Project Project planning
Achieve 75%
Project certainity
Monitoring foronallthe
Poonam Patil 27-Aug-18 6 15-Jun-18 Management
Project sub-processes
basis of
Achieve 75% actual
Project control limits
certainity
Project sub-processes
basis of actual
Delivery Signoff
Project control
Deliverylimits
Signoff
Sofia Kunvar 27-Feb-20 1 25-May-18 Management
Project Requirement
Sofia Kunvar 27-Feb-20 2 25-May-18 Management
Project
Poonam Patil 27-Aug-18 1 25-May-18 Infrasturcture
Project management
Requirement
Poonam Patil 27-Aug-18 2 25-May-18 Management
Project
Ashish Deshpande 27-Feb-20 12 30–Apr-18 Infrasturcture management
Ashish Deshpande 27-Feb-20 11 25-Apr-18
Sofia Kunvar 7-May-18 4 10-Apr-18 Schedule Dependancy
Sofia Kunvar 2-Apr-18 6 2-Apr-18 Processes used Execution
Bhagyashree 27-Feb-20 6 2-Apr-18 (any
Skillsnew Key resource
Jamkhandikar
Sofia Kunvar 1-Apr-18 9 1-Apr-18 processes,
Technology availability for the
Process
Poonam Patil 27-Feb-20 3 27-Mar-18 procedures,
Project project deliverable
Requirement
Poonam Patil 27-Feb-20 4 27-Mar-18 methods,
Managementetc
Requirements Management
Requirements
Vaishali Shirsat 27-Feb-20 1 27-Mar-18 management
Project management
Requirement
Resource
Management / Management
Ashish Deshpande 13-Mar-18 7 13-Mar-18 Functional
Infrasturcture
Sofia Kunvar 7-May-18 3 10-Mar-18 Schedule Schedule
Sofia Kunvar 27-Feb-20 4 8-Mar-18 Schedule Requirement
Poonam Patil 27-Aug-18 4 8-Mar-18 Schedule understanding
Requirement
Vaishali Shirsat 28-Mar-18 1 5-Mar-18 Testing understanding
Customer team to
Sofia Kunvar 2-Apr-18 5 1-Mar-18 Products used provide on time
Technology
Sofia Kunvar 7-May-18 2 1-Mar-18 (any new free-
Schedule support for the SIT
Communication
Vaishali Shirsat 26-Feb-18 7 22-Feb-18 ware/open
Resource / Communicate new
source, etc)
Infrasturcture error routine
component to the
developers
Poonam Patil 27-Feb-20 1 20-Feb-18 Requirements Requirements
Poonam Patil 27-Feb-20 2 20-Feb-18 management
Resource / management
Project
Vaishali Shirsat 26-Feb-18 6 20-Feb-18 Infrasturcture
Domain management
Project scope to be
Vaishali Shirsat 26-Feb-18 4 16-Feb-18 Project freezed 75%
Achieve
Vaishali Shirsat 26-Feb-18 5 16-Feb-18 Management
Project certainity
Sofia Kunvar 27-Feb-20 18 15-Feb-18 Management
Schedule sub-processes
basis
Cost of actual
Sofia Kunvar 9-May-18 2 Ongoing Project control limits
Imporatant Mail
Management commuication need
Sofia Kunvar 9-May-18 4 15-Feb-18 Schedule Cost
to be stored this
Vaishali Shirsat 1-Feb-18 1 6-Feb-18 Technology will enable
User shouldback up
be able
Vaishali Shirsat 27-Feb-20 1 6-Feb-18 Functional and
to
User traceability
feature
shouldproduct on
be able
Sofia Kunvar 2-Apr-18 1 1-Feb-18 Schedule the
to projectproduct
feature
Communication without
Sofia Kunvar 2-Apr-18 2 1-Feb-18 Contract Risks any
Scopereliance on PST
or mail box
Sofia Kunvar 2-Apr-18 3 1-Feb-18 Resource / login accounts to
Execution
Sofia Kunvar 1-Dec-18 1 20-Jan-18 Infrasturcture
Schedule be created for
Sofia Kunvar 7-May-18 1 20-Jan-18 Schedule developers
Dependancy
Vaishali Shirsat 26-Feb-18 2 14-Jan-18 Skills Expertice required
Vaishali Shirsat 26-Feb-18 3 14-Jan-18 Skills for Hibernate
Key resource
Vaishali Shirsat 26-Feb-18 1 9-Jan-18 Project transaction
availability
Timely responses
Ashish Deshpande 27-Feb-20 10 Management management
throughtout
from Client the
28-Nov-17 Integration Dependency on
Ashish Deshpande 20-Oct-18 10 28-Nov-17 Integration project
Dependency on
integration
Bhagyashree 27-Feb-20 5 5-Nov-17 Testing integration
Availability of
Jamkhandikar
Poonam Poatil 15-Oct-17 1 3-Oct-17 Project required data in
Backup process
Sofia Kunvar 9-May-18 1 30-Sep-17 Management
Resource / UAT
Resource/
Ashish Deshpande 27-Feb-20 9 30-Sep-17 Infrasturcture
Technology Infrastructure
Dependency on
Ashish Deshpande 20-Oct-18 9 30-Sep-17 Technology Dependency on
integration
Ashish Deshpande 27-Feb-20 8 5-Sep-17 Business integration
Dependency on
Ashish Deshpande 20-Oct-18 8 5-Sep-17 Business
(Budget/Costs) Dependency
integration on
Bhagyashree 27-Feb-20 4 2-Sep-17 (Budget/Costs)
Resource / integration
Gather &
Jamkhandikar
Sofia Kunvar 9-May-18 3 20-Aug-17 Infrasturcture
Contract Risks communicate
Follow up mail to be
Sofiya 11-Aug-17 5 11-Aug-17 Business requirements
done
CL/CRby Sales team
development
Sofiya 11-Aug-17 6 11-Aug-17 (Budget/Costs)
Business accurately
to get the
CL/CR contract
development
Ashish Deshpande 27-Feb-20 7 (Budget/Costs) on time
1-Aug-17 Technology Standards
Ashish Deshpande 20-Oct-18 7 1-Aug-17 Technology Standards
Resource /
Ashish Deshpande 13-Mar-18 6 28-Jul-17 Functional
Infrasturcture
Sofiya 10-Jun-17 13 19-Jul-17 Technology Development of
Sofiya 10-Jun-17 9 11-Jul-17 Skills utility
Availability of
Sofiya 10-Jun-17 11 11-Jul-17 Skills resources of
Availability
Sofiya 10-Jun-17 12 11-Jul-17 Resource / (developers)
resources
Follow delivery
Ashish Deshpande 27-Feb-20 1 10-Jul-17 Infrasturcture
Integration (developers)
timelines
Readyness of all
Ashish Deshpande 27-Feb-20 2 10-Jul-17 Integration modules for of all
Readyness
Ashish Deshpande 27-Feb-20 2 10-Jul-17 Integration integration
modules
Dependency for on
Ashish Deshpande 27-Feb-20 3 10-Jul-17 Integration integration
Dependency on
Ashish Deshpande 27-Feb-20 4 10-Jul-17 Resource / integration on
Dependency
Ashish Deshpande 27-Feb-20 5 10-Jul-17 Schedule
Infrasturcture Follow delivery
integration
Ashish Deshpande 27-Feb-20 6 10-Jul-17 Project Communication
timelines
Ashish Deshpande 20-Oct-18 1 10-Jul-17 Integration
Management Readyness of all
Ashish Deshpande 20-Oct-18 2 10-Jul-17 Integration modules
Readyness forof all
Ashish Deshpande 20-Oct-18 2 10-Jul-17 Integration integration
modules
Dependency for on
Ashish Deshpande 20-Oct-18 3 10-Jul-17 Integration integration
Dependency on
Ashish Deshpande 20-Oct-18 4 10-Jul-17 Resource / integration on
Dependency
Ashish Deshpande 20-Oct-18 5 10-Jul-17 Infrasturcture
Schedule integration
Follow delivery
Ashish Deshpande 20-Oct-18 6 10-Jul-17 Project timelines
Communication
Sofiya 1-Jul-17 10 01-Jul-17 Management
Technology Technology
Sofiya 11-Aug-17 4 28-Jun-17 Business CL/CR development
Sofiya 10-Jun-17 7 9-Jun-17 (Budget/Costs)
Resource / Availability of
Sofiya 10-Jun-17 8 9-Jun-17 Infrasturcture
Skills resources
Follow delivery
Sofiya 1-Jul-17 9 07-Jun-17 Technology (developers)
timelines
Technology
Sofiya 10-Jun-17 5 26-May-17 Resource / Adequate usage of
Sofiya 10-Jun-17 6 26-May-17 Infrasturcture
Products used User quotatool
Migration
Resource /
(any new free- should work on
Ashish Deshpande 13-Mar-18 5 10-May-17 Functional
Infrasturcture
ware/open minimum
source, etc) conditions
Sofiya 10-Jun-17 1 5-May-17 Resource / 24X7 support
Sofiya 10-Jun-17 2 5-May-17 Infrasturcture
Environment Delta should be
Sofiya 10-Jun-17 3 5-May-17 Processes used available
Follow delivery
Sofiya 10-Jun-17 4 5-May-17 (any new
Performance timelines
No migration during
Bhagyashree 27-Feb-20 2 2-May-17 processes,
Risks
Skills US
Keydaytime
resource
Jamkhandikar
Shainaz Rehamatulla 20-Feb-17 7 20-Mar-17 procedures,
Requirements availability
nSight Reports
Shainaz Rehamatulla 20-Feb-17 8 20-Mar-17 methods,
Testing etc throughtoutofthe
Availability key IT
Shainaz Rehamatulla 16-Mar-17 2 6-Mar-17 Integration project
stakeholders
Integrate Productduring
Sofiya 42958 3 26-Feb-17 Resource / UAT
Video
BackupAdminSystems tool
Shainaz Rehamatulla 20-Feb-17 6 2-Feb-17 Infrasturcture
Performance changes
Proper data
Sofiya 11-Aug-17 1 24-Jan-17 Risks
Schedule requirement
Support, KVA
Sofiya 11-Aug-17 2 24-Jan-17 Integration development
Integration Testing
Shainaz Rehamatulla 16-Mar-17 1 5-Jan-17 Performance Download/Print
Sofiya 1-Jul-17 1 1-Dec-16 Risks
Resource / functionality
Resource / should
Sofiya 1-Jul-17 2 1-Dec-16 Infrasturcture
Business work
Businessand should be
Infrasturcture
Sofiya 1-Jul-17 3 1-Dec-16 (Budget/Costs)
Schedule responsive
(Budget/Costs)
Schedule
Sofiya 1-Jul-17 4 1-Dec-16 Technology Technology
Sofiya 1-Jul-17 5 1-Dec-16 Contract Risks Contract Risks
Sofiya 1-Jul-17 6 1-Dec-16 Schedule Schedule
Sofiya 1-Jul-17 7 1-Dec-16 Technology Technology
Sofiya 1-Jul-17 8 1-Dec-16 Resource / Resource /
Shainaz Rehamatulla 20-Feb-17 5 15-Nov-16 Infrasturcture
Delivery Infrasturcture
Milestone
Achievingsign-offs
of
Performance on time
Ashish Deshpande 10-Nov-16 6 10-Nov-16 committed Sprint
Risks Availability of
Ashish Deshpande 10-Nov-16 1 10-Nov-16 Skills Velocity
Availability of
Resource / skilled resources
Ashish Deshpande 10-Nov-16 4 10-Nov-16 Buffer Resources
Infrasturcture
Resource /
Ashish Deshpande 13-Mar-18 4 5-Nov-16 (Testing)
Functional
Infrasturcture
Suman Khalia 10-Oct-17 1 24-Oct-16 Testing Availability of Build
Suman Khalia 10-Oct-17 2 24-Oct-16 Environment for Defect Fixes
Availability of Citrix
Suman Khalia 10-Oct-17 3 24-Oct-16 Development System
Availability of Build
Suman Khalia 10-Oct-17 4 24-Oct-16 RA Stable Build
Suman Khalia 10-Oct-17 5 24-Oct-16 Environment Availability of
Suman Khalia 10-Oct-17 6 24-Oct-16 Contract Risks environment,
Agreed and user
Suman Khalia 10-Oct-17 7 24-Oct-16 Contract Risks Access
accepted
Agreed Scope for
contract
Suman Khalia 10-Oct-17 8 24-Oct-16 Contract Risks Test Cycle
SOW sign offruns before
Suman Khalia 10-Oct-17 9 24-Oct-16 Testing project
Test kicked-off
Cases sign off
Sofia Kunvar 4-Oct-17 3 14-Oct-16 Resource / before%test
Some of
Shainaz Rehamatulla 20-Feb-17 4 13-Oct-16 Infrasturcture
Regulators execution
allocation
GST detailsofare the
Sofia Kunvar 4-Oct-17 2 13-Oct-16 Resource / existing
required
Some % team
to
of
member
implement should
Sofia Kunvar 4-Oct-17 1 12-Oct-16 Infrasturcture
Resource / Some
have % ofofinthe
allocation
been
Infrasturcture system
existing
allocation team
Sofia Kunvar 4-Oct-17 4 12-Oct-16 Resource / Atleast
continued oneof the
existing
till the
Resource /
Infrasturcture member
existing
resource should
team
should
Ashish Deshpande 13-Mar-18 3 12-Oct-16 Functional
new team member
Infrasturcture have
member
have been
been should
a part of
Shainaz Rehamatulla 20-Feb-17 1 5-Oct-16 Requirements Product
is
continued Technical
comfortable tillCCNwith
the
Shainaz Rehamatulla 20-Feb-17 2 5-Oct-16 Requirements have
the
Support
the been
team
system is
Administrationfor
required
andX
new team member
continued till the
Shainaz Rehamatulla 20-Feb-17 3 5-Oct-16 Skills for
Key Community
Monitoring
resource
is comfortable Tool with
new
versionteam
required member
ofinTalend
Talend
Sofia Kunvar 11-Oct-17 7 15-Aug-16 Delivery availability
24X7
the
is system
comfortable with
Shainaz Rehamatulla 16-Mar-17 3 20-Apr-16 Integration which will be
throughtout
CID system
project used
- the
the
in project for
Sofia Kunvar 11-Oct-17 6 1-Feb-16 Delivery project
Migrationinofnodata
Increase of
development
Expected
from different Network
Ashish Deshpande 10-Nov-16 5 20-Jan-16 Environment tickets
speed
database
Sofia Kunvar 11-Oct-17 5 1-Jan-16 Delivery to upload in onto CID
Resource / Availability
database
correct websites of
Ashish Deshpande 10-Nov-16 4 7-Oct-15
Infrasturcture
Resource / Buffer
and Resources
follow Maker
Ashish Deshpande 13-Mar-18 2 18-May-15 Functional
Infrasturcture Availability
Checker Concept of
Ashish Deshpande 10-Nov-16 1 9-Mar-15 Skills
Resource / skilled resources
Availability of
Ashish Deshpande 10-Nov-16 2 9-Mar-15
Infrasturcture Functional SMEs
Availability of
Ashish Deshpande 10-Nov-16 3 9-Mar-15 Skills
skilled resources
Sofia Kunvar 11-Oct-17 4 14-Dec-14 Delivery to work on Clients
Sofia Kunvar 11-Oct-17 3 9-Dec-14 Environment New
Server template
Connectivity
Sofia Kunvar 11-Oct-17 2 5-Dec-14 Technology Licenses required
Sofia Kunvar 11-Oct-17 1 19-Nov-14 Resource / Payroll Employees
Resource /
Infrasturcture
Ashish Deshpande 13-Mar-18 1 30-Jun-14 Functional
Infrasturcture
Mode of Failure Risk Description Impact Impact On Impacted
[what may go wrong with [detailed description of the mode of description [what Party
the Requirement] failure, from perspective of affected Parameter- [Refer list of
party] Schedule / interested
Expiry of Contract Non availability and delay in Legal Effort (Cost) / Customers
Cost parties]
signing Contract as it will expire in Requirement Quality]
Unavailbility of adequate Due to covid customer has reduced
Nov 2020 Customer Effort Customers
resource The
the customer
head count has
in the put a fewnow
project, Satisfaction
Data is not been made avaliable Less utilization Managemen
Reduction in new change significant
the ticket count changes it gettingspecific to to Costing
requests for visualization.
normal and headcount With Data
is due Entry of resources
Visualization
The Tasks t
Schedule slippage China
Since
Since Market
same
Lockdown Team is deployed
has started to Connectivity may Schedule Customers
Screens
As NAPF
insufficient
Covid-19 yet to
application
pandemic, be developed, might
lead tonot
dependant
NAPF beon Reports
Data not avaliable for for support as well Team as forhas KVA schedule Customers
Dashboard few data
communicates
started WFH. pointswith needs to be
multiple appealing
this delivery
application
slippage. for delivery
Schedule slippage development is deployed, this Schedule Customers
made
systems, avaliable
Availability/bottleneck
VPN is being weused areinfor order
using ofto make
connecting POCimpacted
may
integration with
Quality of deliverables could lead to SLA breach and Customer may Quality Customers
Visualization
simulators
resources
office desktops. here screens
(Infrastructure,
to perform heavily
might at
various
It other
impact
Availability KVA delivery slippage not get required Schedule Customers
testing,Creep
Support)
Scope This may – Impact
impact onon the customer
system
the projectmay endnot Budget & Service
Scope Sometimes Team face functionality
Customer may
qualityinof
Budget
Delay andfeedback
delivery
Schedule onconnectivity work properly
timelines and Schedule Providers
Feedback from Client issue, Unavailability of Connectivity not get required
Customer may Schedule Customers
Deliverables
Delay in Deliverables and budget
It might impact
Delay, Quality Delay
may lead in response scheduletoslippage. functionality
not get required Schedule Customers
quality oftoDeliverables the
It might
projectimpact Service
Delay clarifications
Delay
Production in Data Go / Availability
questions
Live for Release from functionality Schedule
timelines
the
Delay project
in and Providers
Service
Availability UNICEF’s
1 may be delayed internal ifsystems QA and Schedule
budget and
timelines
schedule/
Application Schedule/ Providers
QA Regression can be UAT Testing Schedule is Customers
delayed due to Contract On AWS implementation vendor budget
velocity
Customer
development dis- velocity
Project
Lack of expertise of AWSand delayed due
Because of attrition
to unavailability
in the Team of Customers
on boarding issues
implementatiaon for is lacking
Since the in experince.
complete scope of the variance
satisfaction
might get Delivery
Unavailablity of required QA team
there
New TCB
mayat E-com
beUNICEF
impact site–onnew KPI's PHP Schedule
Schedule, Availability
Release
number 1 Expected
Change
Project isinnot
Coverage
requirement
clear orfor known
after
test impacted
Delay
Schedule,
Defining in project
and
Delay in of resources for
Requirement like resolution%
site developmentand road backlog%
map plan Efforts
ScheduleEff Customers
development scenarios
BRD
and has
signdeviatedoff
may and notplanning
from
be possiblethe mayif backlogs
Requirement
Effort,
deliverablesReworkmayfor
Test Scenarios and BDD is not shared with Dev team Lack of priority ort and Customers
review timely feedback
affects
original the
Work team Ordernot
schedulereceived
provided in increase
and
Delay
each Delay
in in
Milestone,
Changesmay not be
to the Since the priorities of features prevents Schedule
quality Customers
completeScope
Requirements and due to Lack of during
(delivery
the Sprint.
proposal, date). it is difficult to plan QA/UAT
schedule
Commitment ScheduleEff
Planning related are not communicated clearly, business critical ScheduleEff Customers
time orindelayed
activities, feedback
Execution, and commit
Data
Chandan was has nottoproperthe expected
resigned and and post and formalizing
Manually ort and Cost
Delay delivery/ impact on user stories are developed as features
As to be
user stories ort and Customers
by Product owner
Monitoring,
schedule Controlling of deliverable
migration
currently he ( is
contentCustomer
taking wascare expects
not of the acceptance
insertion
If SRS data
approval
Dependent proper available. developed,
not being Schedule
quality Customers
Project
migration data delay completion
showing
Delay
release proper
inactivities
UAT of of75% data
forwithout
Milestone on live1the
Impact – of delayed
fromProject
Project
is drupal
Timeline
there
Schedule Velocity
Release
reviewed
Non to
taskbe
availability
and Schedule Customers
definition
website
Home
plateform
User Page
stories of Total
through
and Scope
Department
are created CD-CI in ) deliverables
backend
impacted
are chances
Non-identical Environment Customer APIs are widely used met.
could
the be
approved,
of dataany via Schedule Customers
pipeline
VSTS basedfor UAT on theandrequirement
production that there will
Unavailbility of resource for
SRS
Heavythe has application
flood beendue submitted development
to raining to
can impacted
scope
API
We or change
will its
be in Schedule
Quality/ Customers
which
captured
have has may
widespreadfrom result in
Collabera
impactdelay in be
Sprintimpact
0 due
based
onto
Non-availability of approval where
Collabera
TDD data been
onis3-Jul-19
fetched
submitted foron
from tovia problem
later
access postwill lead Productivity
and cost due Customers
Schedule
on captured user stories will release
however
Collabera
business of these
the delivery
informed
operations userthat stories
ofneware the
invoice
in backup can not not
Issue in access of customer these APIs.
approval.
Collabera Collabera
onIf3-Jul-19
there is informed
issue
for with development
to delay in to rework
and
Schedule
cost due Customers
lead
API to rework
widely useddevelopment
in project.
not beingisreviewed
wrapper
Customer API
being by used
aredeveloped
being by development
be raised.
available Also
Rework during access
that
approval
it isof being
and
these was
reviewed
APIs partwill ofby Sprint
lead
DHR to may lead
testing,
Delay to re-
in release to rework
and
Schedule
cost due Customers
application
phase if any deviation from Collabera.
them
for project
for access development.of third party Since already
any change
Unavailabilitydoneinof
Technical architect half
team.
0
UATdeliverables.
of/ Any
the environment
STI development
delayThis in approval
delay asisteam
should work
development
of new and thus
wrapper to rework
and cost due Customers
requirement
implementation captured tool,development
the also there is plan change will in be considering
technical
the
Rework UATdue / SITto
Schedule slippage willready
may
impacting
be not
have beduring
Sprint
impact
able tosprint
0onfetch
basedschedule
0/1 where schedule
and
will thus impact
have cost
and Schedule
to rework Customers
existing
done based API on expected.
these API delay in there
approach
will
change willinbe
impact may
API
the Schedule &
UAT / SIT will get impacted andwill
invoicing
we cost beas well as
setting upfurther
the cost.
and
on schedule
the Sprint Customers
if UAT and SIT environment delivery
analysis,ofany thischanges
wrapper,inAPI API minimal
have
testing
will impact
have orimpact
plan not of
and Cost
Schedule &
Change in APIs will lead to approachenvironment
required on development for UAT delivery Customers
are
more not madeof
efforts available
compare tobythe may lead
done to impact due
by Customer on schedule,
to change
strategies
thus
on schedule
schedule Cost
Unavailbility resource and SIT.
Less Requirement Discussion in
Government Delay
We willinbe in Quality/ Customers
Customer
efforts considered during cost
change
There
Statutory are in chances
implementation of additional required
and
problem costdue in
of the
the
to Schedule/
Productivity Service
Requirement Sign-off Requirement
Delay in CCNX Analysis
and CCN (RA) XI requirement
initial approach
scope needed will have
for theimpactproject on submitted
project
Project Scope SRS Cost/ efforts Service
Schedule/ Providers
Scope project
Creep estimation Closures/Mandatory
phase
UAT will further delay officein to closures
sign in backup not
sign-off
and thus will impact on the schedule
success
Delay in VPN and Accounts
during cost
theas these
execution for of impacted
Project
availableTimeline Cost/ efforts Providers
Schedule Delay
off andinGo 4 Virtual
LIVE.Its Machines
time for with Schedule Customers
schedule and cost changes
the project
Datamatics will lead to rework impacted
Project Timeline
Schedule full SharePoint
Delay
senior in
management
Accounts setup & team for to to
access be Schedule Customers
impacted
Project Timeline
Schedule Datamatics
Version
involved Control
since development
client is team
and existing Schedule
Quality/ Customers
DelayClarity
Lack in Infrastructure
of business readiness impacted
Customer
Delay in delivery. Quality source code
stretching the sign-off on one of Project Customers
reduction in the system. at client site may
requirements dueaffectto lowon client satisfaction
Delay in
Delay in Infrastructure the RFC
Delay where weand
in feedback are signoff
trying to ifHigh
the count
concept of is Schedule
Margin Customers
Schedule
readiness slippage.
at client site project schedule.
business understanding may schedule
Requirement understanding do key
on the testing
documents alonglike with BRD,them Defect/
ifnot
theclear about
follow-up Quality Customers
leads to more
Because defects and
the proiroites are not Delay in
Unavailability of
delay in sign off from client but they
UAT
Gaps sign do offnot
in understandingetchavemay resources
affect
will havethe software
the
is not quality
application
done on Schedule
Training/ Customers
rework
communicated clearly so , schedule may
Resources
Process and Domain and even
schedule.
impact on marisa
the issues is not to able
be to therethere
Selection
time will be of
might Knowledge Customers
Knowledge developed stories may not get impact Schedulean
Delay in delivery/ impact on provide the
delivered
Contract time is not done
Renewal problem
User
be delayed
stories
in and for Transfer
Quality/ Customers
schedule closed which
Marisa not testing woyuld thelead to scheduled d quality Managemen
both the parties and contract
Due to Dependency will endwe in mid will feb
not knowing the
Sprint
escalation and Project
velocity variance.
application as per the RFC deliverables
Testing to be t
Unavailability of Resources 2019to delivered the Issues on
able issues
from legal & Effort
Margin Customers
(HR, Softwares) document
Budget
Change will
in approved
requirement
get impacted by after
WTO.
if we since on
done oneRFC Managemen
Outdated Technology Time compliance and Quality
As a result,
continue
BRD signwith offmanyand
all the support
planning
resources may Resource
and
High not onis
effort t
Managemen
Delay in delivery. Quality Resource unavailability due to billing issue as Effort
reduction issues
of
affects
CCNXI are
thetill identified
teamthe sign
schedule and
off is Available
application
variation
Delay in only level t
Changes tointhe the system. unforeseen reasons or well have to
May Schedule Customers
Schedule
Requirements slippage. reportedtool
received.
(delivery
Current as
date).CCN X / XI issues.
not supporting GIS as per in
schedule
Delay the
Current
Unavailabilitynot
tool of Resources resignations during the project keep ouot of Schedule Customers
compatible data.
Un-availability of UAT
Hence and notProdable contract
schedule
supporting GIS duration may impact the project scope/
Schedule may Quality Customers
Un-availability of UAT and to plot
Env
Technical
at theUNcomplexity
respective
WATER may ArcGIS
on leadSDMX to
compatible
More time isdata needed to schedule. Customer
impact
be impacted
due to Schedule Customers
Prod Environment mapstoinunavailability
delay
Development
Due deliverablesmay lead of Datato delay Schedule,
study isand
SME notunderstand
available for dissatisfaction
un
due availability
Scheduleto more may Customers
in deliveries
collection and analysis SME, the Efforts
SDMXcollection
Data development and R&D time
impact dueonto Schedule Customers
schedule may delay
analysis
Data will not be visible The new database structure SDMX
un
Wasavailability
increasing Schedule, Customers
properly on admin tool and provided by the client was not complexity on Efforts,
website feasible considering all the the code level Quality
scenerions. and may have
increase the
latency time on
website for
Was increasing
complexity on
the code level
and may have
The new database structure
increase the Schedule,
provided
Lack
Any of Client
delay by withthe commitment
client was
regards to or not
Data will not be visible latency
The time on
delivery Efforts, Customers
properly on admin tool feasible
delay
responses in sign-off
considering on critical
/ clarification all the/ work
Delay in responses fromand website
dates
The for
delivery
may Schedule
Quality Availability
website
Client in providing the scenerions.
product
questions
Any delay may /with impact
sign-offsregards whole
/ to
Delay The delay in availability of fetching
extend
dates
The the
installation
may Schedule Customers
responses from customer project delivery
Production
responses and schedule.
/ clarification / there will be an
Delay in availability of servers may impact the data,delivery
extend as the
schedule
The may Schedule Customers
Delay
serversin providing the sign-offs/Environments
questions / sign-offs / delays impact on
installation
The delay intimelines availability of data
extend
dates
The get
may
installation Schedule Customers
responses
Delay in availability
from customer of will impact Project Schedule
Production testing
To cover if the
up the
servers
Since
CCN Xbothand
maythe CCN
impacttesters
XI theUAT in the should increased.may
extend
schedule Schedule Customers
servers sign-offs/Environments delays tester is we
timeline not
Unavailibility of the exisiting installation
team
complete are new, before
timelines
the 21-Dec.
quality may extend Quality Customers
resource will impact Project Schedule havingto plan
need Schedule Managemen
Unavailbility of resource get hampered.
Knowing
The delayWTO in requirements
and the The project
complete
the UAT t
Delay is requirements availability
gathering
The delay will ofrequirements
in resources
hamper the for UAT, schedule
The project may Schedule Customers
Delay
gatheringis requirements knwledge in
schedule about
this looks of
timelines
gathering difficult.
willthe projectthe
hamper extend may
schedule Schedule Customers
gathering the functionality
client premises
After deployment noticed timelines
Kiosk of thecan project extend
Due tomodule continuous be best in
changes
the need of large screen If the
viewed product is generalized The delivery
requirements, the project butfor
BSP Web in 55 inch
services screen,
required
Due to improper clarity,
display across
BSP
Telleringhas geos then we
implemented
modules is can 32inch
present go datesdelivery
The may Schedule Customers
Due to improper
requirements sharedclarity, execution
Due to will be delayed
continuous changes and in
customer changed theare
plan ahead
If theinproduct
screen with
TVs, the isenvironment
they plan
generalized
to cover 1 extend
dates
The delivery
may Schedule Customers
requirements
varying
to coverin1 each shared
productRG session
fortheare
all
only
requirements,staging
will affect the schedule the project to
have plan and
customer changed product
across
replace
not yet geos
for all55
with
moved thengeos
to inchweelse can
in
Production. 1 ityears
go
will extend
dates
The delivery
may
Additional Schedule Customers
varying in each
geos to cover 1 product RG execution will of
Unavailability betechnical
delayed and
plan hamper
ahead
Unavailability
time. whole
with theofimplementation
plan to cover 1
sufficient extend
dates
The project
efforts may
to be put Schedule Customers
session will affect the
resources during scheduleProject
for all geos of technical
Unavailability product forduring
resources all geos else it will
Project extend
schedule
in by the will Schedule Customers
resources development
For OCR, if the may formsresult areinnot
Unavailability of resources hamper whole
Execution mayimplementation
result in extra extend
available
The
Additional
delivery Effort Employees
schedule slipage
standardized
Unavailability to
of identify
technical unique
Forms are not standardized efforts by available
Unavailability of sufficient
resources resources
dates
The
efforts
project
may
to be to put Schedule Customers
Unavailability of technical
to identify the unique identifier for
resources during
the page Project then it will
and scheduel
resources during slippage
Project meet
extend the will
schedule
in by the Schedule Customers
resources
Unavailability
Forms are not
identifier for the ofpage be difficult
development
For
ChangeOCR,inifto the implement
may
requirement formsresult are OCR.
innot
after
Execution may result in extra deadlines
extend
available
The delivery Effort Employees
resources
standardized to identify schedule
standardized
BRD sign slipageoff and to identify
planning unique may Delay in
efforts by available
Resource unavailability resourcesdue to resources
dates may to Schedule Customers
the uniquetoidentifier
Changes the for identifier
affects the forteam the page schedule then it will schedule/ Schedule/
and scheduel
unforeseen slippage
reasons or meet the
extend Customers
the page
Requirements
Unavailability of be difficultdate).
(delivery
Unavailibility to of implement
BA cum Tester OCR. velocityin
Delay velocity
resignations during the project deadlines
Project Schedule Customers
Resources in Mumbai
Target velocity location is due to ML
impacted due variance
schedule
Unavailability of key duration may impact the project deliverables will Schedule Availability
resource for the project may
to DLR
Target require developers
velocity more is efforts
being
impacted which
ondue Delay in
schedule. get delayed Schedule Customers
deliverable sudden
may
to DLR impactleave the project
developers schedule
getting schedule
Delay in
Schedule Customers
pulled in other support project. schedule
Not achieving 75% certainity Project does not achieve 75% Productivity Productivity Management
for alldata
POC sub-processes
doesn't show any certainity
Project for all sub-processes
estimation, planning and declined
Productivity Productivity Management
improvements
Unavailability of key using PPM
monitoring
Non-availability
Sudden may
is done
resignation impact
ofon thebasis
the
client’s
of Key IT of
resource declined
The delivery Schedule Customers
resource with required
Delay in responses from business
POC
may data
be
resources objectives
and
difficulty
for may
Lack of Client commitment or inlead
hiring
integration to failure
a feature dates may
knowledge and experience by utilising
resource in more
the efforts
Team, in work
PPM Delay in
Client
Non availability of client IT delay
may in sign-off
result in delay on inwhich
critical may extendmay
dates Schedule Customers
in theavailability
Domain and Project
and
affectin the does
Control
product estimation,schedule
may impact not
Charts achieve
due
whole to the 75% schedule
resources.
Non of client IT development
Project
Non-availability and release
planning
of client’s ITproject
of and
the extend
Delay in schedule Schedule Customers
Technology
resources. of 75%
the certainity certainity(Or
learning
delivery
resources curve
and drop below)
forisschedule.
integration for all
feature Managemen
Not achieving overall project.
monitoring done" on the basis Quality affected Productivity
application
for developed sub-processes
may result in delay using PPM may
in development Productivity t
Managemen
POCalldata
sub-processes
doesn't show any of POC data and may lead to Productivity
improvements impact
and release the business
ofnot theachieve
overallobjectives
project.in" declined t
Not achieving 75% certainity failure
Project by
does utilising more75% efforts Quality affected Productivity Management
for alldata
sub-processes Feedback
certainity(Or not received on time
POC doesn't show any PPM and
Project in drop
estimation, Control below)Charts
planning forand all Productivity Productivity Management
improvements from UNICEF
sub-processes
monitoring is done on
usingon deliverables
PPM the maybasis of Project
declinedTimeline
Delay in giving sign-off Schedule Customers
submitted
Changes
impact
POC data theand by may
received
business Datamatics after
objectives
lead to due may
signing-
failure impacted
Delay in giving sign-off Resource
Feedback unavailability
not received on time to Project Timeline Schedule Customers
resul
off
by of in
utilising schedule
requirementmore overrun
specifications
efforts Delay in
Changes to the from UNICEF
unforeseen on deliverables
reasons orin PPM impacted Schedule Customers
during
and theby
in Control
submitted system Chartsdesign,
Datamatics may schedule
Delay in
Requirements
Unavailability of Resources resignations during the mayproject resul Schedule Customers
delay
in schedulethe schedule.
overrun schedule
Changes to the duration
Changes may
received impact afterthe project
signing-off Delay in schedule Schedule Customers
Requirements
Unavailability of Resources of requirement
schedule.
Resource unavailabilityspecifications due to Delay in schedule Schedule Customers
during
unforeseen
Timely the
receiptsystem
reasons of design, may
or resignations
master data in
delay the
during the schedule.
project duration may
required
BSP follows format margining
for Custodian different
impact the
Unavailability project schedule.
Deliverables UAT Testng
database
process twoof
for
atservice Sitescritical
branchesand BSP
from resource
in Features will not Schedule Customers
Process not identified Workflows
in Mumbai
Client
(Required
manila, internal
thisfor due
will Go to
process marriage
impact
live not
phase)
smooth be fully
Project
Schedule Schedule Customers
Unavailability of key identified
leave
Change
OMS
process and infor
Reports taking
another
requirement
stories approvals
resource be for
to after due functional
deliverables will Schedule Availability
accessing system and verifying Delay in
resource forTraining
inadequate the project
and to ML planning
sprint
assigned
Existing may
VFS toimpact
BHABHA
project the
meeting
will may the
project
squad
be are get delayed
Customer Impact On Management
deliverable
System knowledge deliverables
Migrated to requirement
Sitecore which is in schedule/ Schedule/
Changes to the deliverable
affects
not
Changeyet the matured
in team and
velocity.
hence after noto Satisfaction [what Customers
discussion between VFS velocityinon
Impact
Delay velocity
Requirements
Delay in delivery/ impact on work can
sprint planningbe startedmeeting onand this.
may Parameter-
Schedule Customers
schedule Datamatics,Proposal to be variance
schedule
schedule/
Only very Schedule/
Schedule /
Changes to the affects
Trainee the
Resource
team velocity. Replacement Customers&
Customer
Non-identical submitted velocity
Demanding velocity
Customer
Effort (Cost)&/
Requirements in place ofbut anSeems resource to be exit,risk on Project
Environment gettingin
Delay the Sitecore support
response to variance
Applications Quality] team
Project
Communication gap which
finalization
contract willsinceimpact
of the services.
tools and Future Schedule team
Customers
clarifications
technology for /the
Workfow
development
questions from Are
Delay Affected
in
deliverables may Schedule
Unclarified requirements part is sidealready getting done by one Customers
client
forms(Infopath, may result in schedule and quality
Unclarified requirements Delay
fo the in
schedule
response
vendor impact. of PowerApp,
VFSto clarifications / impact
Delay in schedule Schedule and Customers
Customer team is not SharePoint
questions
Due to dependency Ex) clientonside
from may to
customer The delivery quality
Schedule Customers
available
Tool Impactduring the SIT result in schedule
complete
Estimation SIT,
done their forimpact.
unavailability
development dates
Projectmayschedule Efforts Customers
Communication gap will not
are
Scopeimpact realisticthe schedule
finalization for calender and extend
Future Schedule Customers
Implementation of new Metadata
Lack of awarness columns of new deliverables
Failer to use may
the Code Customers
error routine component framework of classes for handling impact
new error efficiency
not understood error routines features, developer routine
may fail to use the components component
efficiently efficiently
Since the priorities of features
are not communicated clearly,
certain user stories are
Resource unavailability due to Selection of
developed but could not be Schedulean
Delay in delivery/ impact on unforeseen reasons or User stories for Customers
schedule closed due to unavailability of Delay in d quality
Unavailability of Resources resignations during the project Sprint Schedule Customers
dependent stories and their schedule
Changing project scope duration may
Unexpected impactare
changes thereceived
project The delivery Schedule Customers
implementation.
aftera sign-off mayachieve lead to75%schedule dates may
Not achieving 75% certainity schedule.
As
Project result,
does not delay in UAT sign Productivity Productivity Management
for extension Production
extend
POCalldata
sub-processes
doesn't show any certainity
off will affect
Project for all
estimation, to sub-processes
schedule
planningand and declined
Productivity Productivity Management
improvements using PPM
monitoring may
is done impact on thebasis the support
declined issues Managemen
Unavailbility of resource Margin as well as willthe impact of Effort
business
POC dataand objectives
and may of lead to failure SLA will get t
Crash of Mail box server closure
As a result of SLA
mails notproduction
stored at Client Quality Management
by utilising
central more some
location, effortsimportant
in PPM impact.
communication/
support issues.
Unavailbility of resource anda in
As Control
result,
communication delay Charts
mayin UAT sign off
be missed Production
Evidence willwill
be Effort Management
will affect to schedule Complexity
Functionality and UI gets The approach providedand by Margin
the support issues
lost.
Complexity will Quality Customers
affected The
as well
client approach
wasas willnot impact provided
feasible. by the
the closure get increased
SLA increased
get will get
Functionality and UI gets Quality Customers
affected client
and SLA was ofnot not
productionfeasible. support while
impact.
while featuring
featuring
Communication gap Feedback received on time Project Timeline Schedule Customers
issues.
from HOTUS on deliverables the
the product
product
impacted
Scope Creep There are chances of additional Project Scope Schedule/ Service
ShareGate Liceneses are submitted
scope
Deley
The needed
in login
project byschedule
Datamatics
for the was
account projectresulting
creation
planned impacted
Future
Project Timeline Cost/
Schduleefforts Providers
Service
login
limitedaccount creation in schedule
success during overrunthe execution
considering
for developers multiple may lead to of
licenses forthe impacted
deliverables Schedule Providers
Customers
gets delayed project
parallel execution. However client
Communication gap delay in
Deley in login
delivery account creation for may impact
Future Schedule Customers
Unavailability of currently
developers
Unavailablity has of provided
experienced only 1 deliverables
The project may Schedule Customers
experienced resource
Unavailability of key in license
resources
Sudden in Hibernate
resignation of Key transaction
resource impact
schedule
The may get
delivery Schedule Customers
Hibernate
resource
Delay transaction
with
in responsesrequired
from management
may of
Lack beClient
difficulty mayinget
commitment impacted
hiring aor on extended
dates
The may
management
knowledge
Client changes and experience As
delay a result
schedule
resource in sign-off of non
in the Team, approval
on critical which work of
may extend
dates may
Critical as per As a result of non approval offor 3
Application
extensions Cost Customers
in the Domain and critical
Lack of
affect themay
product changes
sample
schedule
impact from
data duewholeDLR,
in UAT
to the the
project extend
Critical
the BSP changes as per the
requirement critical changes from DLR, the may not be fully
development Cost Customers
Technology
BSP requirement of the expectations
ERM
learning
delivery to andSAPschedule.
curve of BSP
push in will
UATnot
Unavailability of required expectations of BSP will not functional
may have Quality Availability
application
data developed meet.
environment may impact the
Data inlossUAT DLR
Data
meet. to finalise
backup of clientthe approach
side data not of incorrect
Client side data Schedule Management
UAT
available,
Unavailbility of resource As a resulthence
reporting and
of Productionrisk of printing
receipt client
support side in loss
functionality
As a result of Effort Customers
As
data a loss.
resource result of changes
released to in Extension
Frequest releases of the coordination
As a result of with
changes 7 another
Layer’s.in unavailibility of
Extension Cost Managemen
Accounting
project, pressure Extension, on CCN rework X team integraton
exisitng will
resource, Managemen
Frequest
required releases
resources of the
for Accounting Extension, rework integraton will Cost tt
required resources for may
may occur,
occur, which
which would
would leadlead to to not
3 extensions
be delivered
response to
integration
Scope creep As a occur,
may
DLR result of
which expectations
thewould lead from to not be delivered
integration the to
impact
If
delay TRF
in finalise
the
CCN requirements
project
X delivery approach
timelines
and are of
not 3 extensions
on time
will
Efforts
not may
customer bequeries Schedule Customers
Scope creep BSP
impact regardng
the project reporting
timelines and in on Schedule Customers
reporting
reduction in quality
understood and receipt
by the developer in printing maytime
will not
delivered
increase be&on
be delayed Effort &
Requirements not receipt
coordination printing, with delay
7 Layer’s. in delivered
and may onbe
not Availability
understood Nasik then the estimation and time
delivery dates Schedule
Unaware of Contract development
As a result of no ofnew Telleringproduction production
time
of good quality Quality/ Management
renewalcost may get schedule
support may
contract get impacted
received and we may
support extend
work Project
Project extension
As
Ajay amay
result notmay
ofget notoccur,
Business
expectations which
implementing Visafromfor Projectwill
which Margin
lead to Effort (Cost) Management
impacted
Project cost may get are
180
would
the
PF
BSP providing
days,
De
may LaifRue
lead
ask
regardng continuos
such
to
Onsite case
impact
specified
support
reporting support
arises
project for to
and may
Projectgo Margin
customer on hold, Margin
Effort (Cost) Management
impacted client
another
short
timelines
hardware
receipt which may
Candidate’s
duration, atof
printing, BSP affect
which for
delay Visa
mayproject
inandled to
Tellering which would lead
dissatisfaction
3 extensions
Not following the As a result
margin. not implementing Only
to very
customer Quality Customers
Not followingstandards
the Travel
increase
systems,
Trainee needsin the
Resourcetooverall
failure beofprocessed,travel
Replacement
implementing cost may not be fully Quality Customers&
Customer
technology
Non-identical development
the
which Demay Rueofspecified
La afffect Tellering
project margin. dissatisfaction.
Demanding Customer &
technology standards as
the
in compare
place
project ofat to
an the
deliverable planned
resource may one
exit, functional Project
Environment extension
hardware
and thus may
affect BSP occur, for
the services.
project which
Telleringmargin. Applications Project team
Migration schedule may occur,
which
Utility
would for
systems, will
which
lead impact
towould
updating
failure ofthe
impact lead
datato
project
implementing at Migration will be Schedule team
Customers
affect SharePoint Online Are
delayedAffected
Migration schedule may quality
If theproject
timelines
the issues
required SharePointmay
deliverable Migration will be Schedule Management
affect
Migration schedule may capability
If the required
occur, which is not retained
SharePoint
would leadtilltoproject delayed will be
Migration Quality Management
affect
Migration schedule may end,
Businessthis
capability
quality issues will
is
User impact
not retained
Unavailability the schedule
till project
during delayed
Go live process Schedule Customers
of
end,themay deliverable
affect issues in ISA7
existing UAT
As a this
result will
leadofimpact
to
lack scheduletheawareness
of quality
slippage of will be delayed
Extension Schedule Customers
the deliverable
SDK as there
existing issuesisinnot ISA7 of ISA7
As a result SDK, of lack integrationof awareness failure integraton will
Extension Quality Customers
control
SDK
lack ofasknowledge
over
therethe is core
notof may
of
As ISA7
a occur
result SDK, which
of lack integration
would
of exposure lead
failure to not be delivered
integraton
Extension may Schedule Managemen
system overextension
control
Accounting
Unavailability theof core
required affect
may
to
As Accounting
a occur
the schedule
result which Extension,
would leadofto
of unavailability onextensions
have
integraton
3 timedefects
will Schedule t
Managemen
system
resources
Unavailability for integration
of required affect
integration
Accounting
As the quality
a result with
ofextension,ICMS may fail
unavailability of not
will
3 be delivered
extensions
not be Schedule tCustomers
Delay in feedback
resources for integration which wouldof
implementation
webservices
As
As a a result
result oflead
developed
delayed
lack delaytoofaffect
may bythe
awareness BSP, on time
delivered
will
3 extensions
not beon
Extension Schedule Customers
Communication gap schedule
occur,
delay
responses
As a
a result
of ISA7
As inwhich
result integrating
SDK, from
of
ofwouldindirect
lack BSP,
integrationofthe
leaddelay
3to
awareness may
failure time
delivered
will
Communication
not beon
integraton will Quality Customers
existing issues in ISA7 SDK As a result
schedule
extensions
occur
communication
while of
slippage
may lack
developingwith of BSP
occur, exposure
which
the Extension
time
delivered
gap willdelivered
impact
on Schedule Customers
as there issues
is not in control over may
of ISA7 occur SDK, which integration
would lead failure to not be
Extension
existing ISA7 SDK to
As Accounting
would a result
required
stakeholders,
lead of
to unavailability
Extension,
functionalities,
schedule
communication of integraton may Quality Customers
thethere
as core system
is not control affectoccur
may the schedule
which would slippage which
lead to time
quality
onextensions
integraton
3 time will Managemen
lack of knowledge of over integration
Accounting
As
would
gap a result with
ofextension,
unavailability
ICMS
which may fail
of have defects Schedule
the core system
Accounting extension affectmay lead
the occur,
to
quality schedule would
slippage not
will
3 be delivered
extensions
not be t
Managemen
Unavailability of required which
implementation
webservices
As a result
would
lead to quality issuesof lead
developed
delayed
delayto affect
may by the
BSP, Schedule
resources for integration onextensions
3 time
delivered
will not beon t
Unavailability of required schedule
occur,
delay
responses
As inwhich
a result integrating
from
ofwould BSP,
indirect the
leaddelay
3to may Schedule Customers
resources for integration timenot beon
delivered
will
Delay in feedback schedule
extensions
occur while
communication slippage
may
developing occur,
with BSP which
the Communication Schedule Customers
time
delivered on
Communication gap would lead
required
stakeholders, functionalities,
to schedule
communication slippage
which gap will impact Quality Customers
time
Project cost would
gap
CR may
list lead
being to
occur, schedule
prepared which slippage
bywould
Customer quality
Cost Cost Management
Wastage of team's that
lead
PF may
may to in be
quality shared
future askattoend
issues share of July.
the Resource Cost Effort (Cost) Management
productiveschedule
Migration time andmay hence Considering
efforts
Resource spent the
on closure
(developer) the CBT not date
CL/CR (31st
availableand Migration will be Schedule, Management
cost
affect
Migration schedule may July)
defects
Limited of thesince
or no project, to bethe
itknowledge resources
performedon by delayed
Migration will be Efforts
Schedule, Management
affect
Schedule Slipage, Cost required
the dedicated
SharePoint for CR development
resources
Certain technical challenges faced deployed. may delayed
The project Efforts,
Schedule and Share holders
not
This
duringbe
may available
lead
implementation to forwaste CR of ofmayCRs and schedule will Quality
Migration activity may stop Resource
development throttling
and thusissue will impact Migration willget
be Cost
Schedule, Customers
productive
fixing theduring team
issuesworking time
may impact and on the impacted due
Migration activity may stop happen
Tool
on the
unwantedmay stop
quality migration
(if
adjustment done by
as other
done in
delayed
Migration will to
be Efforts
Schedule, Customer
Customers &
Non-identical Experienced
overall projectResources activities and onthus Degradation
delay
delayed in not Customer
Efforts &
developers),
CBT development delivery in and
year thus
2015. Project
Environment notice period
deadline and cost noticeable
resolution of Project team
customer confidence. team
certain defects
Network down, Internet not Non availability of Infrastructure Migration activity Schedule may Customers
working, delta will not be
Updated will have
After freezing impact on project
SharePoint 2010 will not work
Customer will impact
Quality Customers
Because
schedule of sudden resignation customer
available
Future deliverables may be before
Delay inmigration feedbackiffor anydeliverables
user not get to start
Future Schedule, and Customers
of Key Resource, there may be quality
delyed
User may experience collaborates
High resourceduring utilization migrationon time with
The
User the
deliverables
may may
delivery Quality and
Efforts Customers
performance difficulty
then the delta in hiring a
will during resource
not get migrated in Sharepoint
impact Efforts will
Unavailabilityissuesof key production server experience
dates may Schedule Availability
resource [with required the Team,
migration, which may
system performance affect the Online
performancedue impact DGSL
Delay in providing nSight Delay in providing nSight Report extend
The delivery Schedule
business Customers
knowledge andofexperience
Report estimation/schedule
may get degraded
Requirement may result due to the unavailability
issues may of
Unavailability key IT Unavailability of key IT in Project datesdelivery
The
upated delta Schedule Customers
in the Domain
stakeholders andonUAT
during learning
Schedule
stakeholders curve
slippage
during UAT as pertool extend
dates may
Different versions LIVE The new requirement of Video It will impact Quality Customers
Technology
and Staging
Schedule of the
slippage revised
had oneplan
Learning change
from due toCenter
in
server GSTimage Details
crash extend
considering
NAPF application Schedule Customers
application developed] incorporation
-page,
Since which
the server is in
codedsource
images forsystems
Center-
will be different
servers version
are
Data anomalies Data anomalies identified during Customer may Quality Customers
Schedule slippage may
given
ETL
Since result
tier2execution
and
for NAPF
same in
Center
TeamDelay Tagging
project
is deployedagain, there for on LIVE
unavailiable
not
The get
Tasks required Schedule Customers
Quality of deliverables functionality.
are
support
As changes
NAPF as of crashing
well
application KVA and face
as forcommunicates functionality
dependant
NAPF on
application Quality Customers
Functionality gets affected similar
development
withnew
The situation
multiple and thus
is deployed,
systems,
requirement may
this
weHighMaps
of are this deliverywith
integration
Download/Print may Quality Customers
cause
could
using loss
lead
simulators
was having various of
to resource
SLA here challengesand
breach effort
to and
perform KVA
in impacted
various heavily
other
functionality
Infrastuture not availiable Infrastructure
team frustration Unavailabilitty
to rebuild due
whole The resource Schedule and Customers
Sprint planning delivery
testing,
terms
to of
connectivityslippage
This
Business Useragainmultiplemay or impact
bars
Access as
Unavailability during on
it
to the
would
HSF at
Thecustomer
system
might
productive may
not
product end
not
work
hours
may Cost
Schedule Customers
environment
quality of delivery
affect download/print and work
properlyproperly
and
Insignificant schedule environment
Sprint
Scope planning
Changes
-responsiveness
This may have may and
may lead
impact Sprint
lead to
ontoschedule
Review
project are
not
Scopenot
match utillized
change and Cost and
Schedule Customers
Slippage
Migration process - partially slippage
may
scheduleimpact
Migration the
slippage
Tool functionality.
quality of the page
and
will might
hence
business
lead not
user
to extra Cost
deliverables as capabilities
well may The
be
migration
completely
Schedule Customers
Payment approval, deliverable
limit the
Delay in signtypeoff of fordatadeliverables
that can be impact
expectation
efforts
mayContract
The of
and the
hence
partially sign
fail and Cost
Schedule Management
migrated from SP 2003 to SP2016 responsive
cost
cost
or anddelayed
Resources cost
Schedule Slipage may lead User
Business to delayed
Unavailability payments during offdoes
gets
Functiality notcheck and Cost and
Schedule Customers
schedule.
match
Production migration failure UAT may lead to
There is no data available on schedule slippage
Test and GOthe
Production on the Cost
Schedule Employees
Schedule Slipage As a result
server
If the for Geo
required of sites
< Product
SharePoint other than Owner expectation
migration
New may Schedule,Cost Customers
As a result
unavailability of <resource
for Story Sign Off
Delay in milestone sign-off London
capability
Delay in which
requirement is not
Providing may
with leadcritical
retained
Milestone
key totill project
Sign- face
The unforeseen
recruitement
delivery
Lead to impact of and quality
Schedule Customers
Not Achieved committed Session
unexpected
end,
As amay
this
result >,
will < rollover
issues
ofimpact during of stories
migrating issues.
Impacting work
Sprint Velocity
off's
technology>,
in PROD
sprints
lead
> may << skills
to unavailability
schedule
occur,
themismatch
quality
impact
which in
of SP developer
dates may
of scrum team Schedule DGSL
Unavilability of skilled and
BufferSchedule
resources of the >, deliverable
< shortfall may
and
lead
extend impact
thereby
to on
delivery
or requirements not being performance
quality, Quality Customers
Resources of buffer
Unavailability would
meeting lead to <impact
business on causingschedule
delay in
understood
Velocity > may commitments
variance> occur, which schedule
and cost and not Cost DGSL
Customer &
resources (Testing)
Non-identical > may
Junior occur,
Resource which would
Replacement lead schedule
slippage
Degradation Customer &
would lead to <below expected Project
Environment to
in < loss
palce
quality of of
delivery revenue
senior > and
resource exit, cost
noticeable Project team
Unavilability of Build As a result
productivity of as<showstopper
well> or high In case of delay Schedule team
Customers
Unavilability of Citrix System priority
As a result defects reported>, <delay
of <unavailability of in such fixes,
Impacting the
work Schedule Customers
Unavilability of Build in defect
Citrix
As system>
a result fixing> may may
of <unavailability occur,
occur, whichwhich
of testing
and schedule
thereby
Causing delay in Schedule Customers
would lead to <blocking
<delay of further
in schedule>. will be impacted
causing delay
Unstable build build>
As a mayof
result
testing>.
occur,
<unstable which would
build schedule
Causing delay inin Schedule Customers
lead
receivedto <delayforofTestingin schedule> > may schedule
Unavailability of As a result <Factors like occur, schedule
lead to delivery Schedule Customers
environment,
Scope Creep user Access which would
unavailability
As a result of <Any lead tochanges
of environment, <delay to in the schedule
Lead to impact Schedule Customers
schedule>.
delay
Scope in providing
otherofthan user
what is testaccess,
agreed slippage.
Schedule Effort
Scope Creep As a result <additional cycle Lead to impact Schedule Customers
delay
and
runabeyondin resolving
accepted the> may queries
estimated occur, >>which
may
may Schedule Cost
Effort
Project executed without As
occur, result
which of <delay in getting Lead to impact Financial DGSL
would
occur, leadofftowould
which <impact lead to
delivery
SOWexecution
Test sign off kicked off SOW
As sign
a result
<delivery
schedule>. of would
><delay
schedule mayslippagelead
occur, towhich
in getting <impact
>. sign financial wherein
potential impact Cost
SLA DGSL
without test cases delivery
would leadschedule>.
to <impact financial delay in getting
Unavailibility of thesign off
exisiting off afor
As test of
result cases> may occur,
unavailibility of on leakage
Customer of Financial
Efforts Management
resource wherein
which
exisitngwould delaylead
resource, in getting
to <potential
response to payments
highter
satisfactionUAT
Delay in GST details Enhancements
payments>. to underlying The delivery Schedule Customers
impact
customer
Source on leakage
queries
systems of
may
may delay higher
be delayed
due UAT to defects
dates may
Unavailibility of the exisiting As a result
defects>. of unavailibility of Customer Schedule Management
resource and
GST may
impact
exisitng not
resource, be of good
responseofto quality extend
satisfaction
Unavailibility of the exisiting As a
which result of
will queries unavailibility
lead to customer Customer Quality Customers
resource
Delay in delivery. Quality customer
exisitng
Senior
As a result resource,
Resource may
response
of unavailibility be delayed
Replacement ofto satisfaction
Defect Leakage Quality Customer
Customers &
Non-identical dissatisfaction Degradation
reduction in the system. and may
customer
existing
in not
palceresource, be
queries
of seniorthe of good
may bequality
CCN
resource delayed
X exit, to customer not Customer &
Project
Environment
Schedule slippage. which
and may
developmentwillnot lead be
may toofcustomer
good
have quality
high noticeable Project team
Unavailability of Product which
More will may
RnD
dissatisfaction impact require services.due toeffort Customer may Quality team
Customers
Technical
UnavailabilitySupport
of in Talend which
and will
schedule
unavailability lead of to
variance.customer
Product
Non availability of Administration Technical not
The get required
Administration dissatisfaction
Support for Community version of functionality
Unavailability ofand key and Monitoring
Key Resource Tool induring
attrition the version dates may
Monitoring
resource
if any politicalToolissue/heavy Talend
useda of
Project
As
Because which
resultTalend
Execution ofmay
of Natual lead
<innetwork
the
may to schedule
project
result
calamities may
in
and extendmay
dates
Unavailability of Impact On Customers
rain/Typhoon/Hurricane/Vo
Requirement is not crystal slippage
impact
Politicalschedule.
schedule
slowness
Incorrect slipage
issues>, <will
data inover-stretching
Nasik
be deliverwe would to theby extend
Team
The delivery [what
Quality Customers
lcano
clear
to be and changing
analyse at the time of not
Suddenbe
client,ofdue
way able
extra tounclear
to
increment workinwith
efforts full
to complete
tickets dates
lead
SLA and may
to delivery
Quality Parameter-
Impact On Customers
As a result
strength of <it unavailability
in Nasik which
was 90impacts of Schedule
frequently.
tickets
Network acceptance
Slowness or it will scope/requirement
volume,
their respectiveearlier assigned tickets
work extend.
schedule Schedule/
[what Customers
Buffer
As
SLA aof resources
result
the of
projects.< >,
only < shortfall
Few key in lead to delivery Effort
be failure on SLA part
if the notepad is not used, and
to
As anow
deliver
Websites result increased
onofplanned
Languages <resource tocan110 betickets
end date > Incorrect
It will be data
slippage. Quality(Cost) /
Parameter- Customers
Unavailability
websites can beof buffer meeting
resources
since Dec
interchanged business
with
2015 in 24 commitments
knowledge Hrs. of schedule
will be
complete visible.
loss at Quality] /
Schedule
may
If occur,
requirement
Richa Rathore which
with (Team would
key lead to
critical
Lead) Cost DGSL
Customer &
resources
Non-identical
interchanged > may
SWIFT
As a result occur,
being of which
available
<interview would asoflead new slippage
VFS due toand
Degradation
Impacting worknot Customer
Effort (Cost)&/
<impacther
extend
technology>, on MLwhich
quality
< skills of maywork>
mismatch impact Project
Environmentof skilled
Unavilability to < loss ofto
previously
resources revenue
groomed
fill the immediateand to
mid cost
noticeable
and
Impacting
thereby
interchange work
of Quality] team
Project
therequirements
or services not being Quality Customers
team
Resources of Functional
Unavilability productivity
senior
requirement resources as
>, well>
<recruitment
have left the of causing
and
Impacting
thereby
languages delay
workin
on
understood > may occur, which Schedule Customers
SMEs
Unavilability of skilled organization
lower proficiency >, < level> lower than may Websites
schedule
causing
and therebydelay in
would lead to <below expected Quality DGSL
Resources required
occur, whichknowledgewould lead leveltoof< scheduledelay in
causing
Time needs to be managed qualityisdelivery
There a possibility > that when we TAT will impact Quality Customers
SWIFT
potential
start working > low
may performing
on Newoccur, which schedule
will be unable to upload and Possibility of VPN link template
NOT Alternate VPN Schedule Customers
download the websites would
resources
(Device lead
Ready) within
to <
TAT lower
the will team
increase andVFS
will be unable to work asto working/outage
As there is NO license thus impacting
versions of Will need to Quality Customers
workthe
per oncustomer
request request productivity
hence
Work/Ticket productivity
Photoshop/Flash, >
and will lead Resolution/New
to closure reduction>
there of lessWeb
is likely highlight
place pertaining to number
Site Creation
possibility ofof tickets
Tickets a day may miss SLA customer and
Photoshop as tickets related to follow-up to be
photoshop/flash to be taken care done for closure
by VFS
If with current set of resources Quality
Attrition/Absconding With high percentage of contract only 8 months Effort/ Customer &
Customers
Non-identical having
employeesoneinmonth
the teamnotice period
of VFS247 Reduction
contract can be Customer
Quality/ & Project
Environment leaves
Project, project
there is then impact
possibility of on
quick Unacceptable
signed Project
Scheduleteam team
the Services will be very high
attrition to the Client
Severity [S] Cause of Risk Source Occurrence [O] Detection
Mode of [Internal, [O] Mechanism
[S] [Values in drop Failure Vendor, [Probability of the [Values in drop [how to detect
down are Customer] occurrence of the down are based this cause]
Critical_impact 6 based on Delay from Customer cause]
Highly_likely 7 on Severity Expiry date
Severity used Customer used for
Moderate_impa 3for calculating We
sidemay Customer Somewhat_likely 5 calculating by Creating BCP
ct RPN] miss
Covid-19 SLA RPN] Business of the
Critical_impact 6 and see Internal Somewhat_likely 3-Jan-00
break
increase out in customer
Critical_impact 6 Unavailabilit Customer Highly_likely 7 Continuous
Moderate_imp ythe backlog Continueus
monitoring of
3-Jan-00 Same Customer Somewhat_likely 3-Jan-00
act Unavailabli
Infrastructu monitoring
Connectivity.of
Incomplete 3rd
Critical_impact 5-Jan-00 resource Internal Somewhat_likely 3-Jan-00
Minimal_impac ty
re of prod resources
party
Followup with
31-Dec-99 usage
This is Internal Not_likely 1-Jan-00
t
Catastrophic_i environme usage
plackage/templ
Project
CITNO team.
8-Jan-00 projected
This is Customer Somewhat_likely 5-Jan-00
mpact
Moderate_imp nt ates
Planning
Project
4-Jan-00 risk is
projected
This Internal Somewhat_likely 5-Jan-00
act
Catastrophic_i Planning
Project
8-Jan-00 risk is
projected
This Customer Somewhat_likely 4-Jan-00
mpact
Catastrophic_i Planning
Project
8-Jan-00 risk is
projected
This Internal Not_likely 2-Jan-00
mpact
Catastrophic_i Unavailabit Planning
Project
8-Jan-00 risk is
projected
This Customer Somewhat_likely 5-Jan-00
mpact
Catastrophic_i y of QA Planning
Project
8-Jan-00 risk
projected Customer Highly_likely 7-Jan-00 Project Plan/
mpact
Moderate_imp Testing
Outsource Planning
3-Jan-00 risk Customer Somewhat_likely 4 Schedule/
act
Moderate_imp team to
work at Observed
4 Vendor Somewhat_likely 3-Jan-00 Milestone
act Critical_impa UNICEF
AWS internally
Customers 5-Jan-00
Delay in High Attrition Internal Somewhat_likel 4
Moderate_imp ct end
vendor y3-Jan-00 Delay in
4 Requireme
Unavailabili Customer Somewhat_likely
act
Moderate_imp unstable
Unavailabili Requirement
Internal testing
2-Jan-00 nt of QAand
ty
Scope Internal Somewhat_likely 4 Schedule and
act
Moderate_imp feature
ty of Review from
Request
4 reviewer
Detailed Customer Somewhat_likely 3-Jan-00 Deliverables
act specificatio
priority in client
Modules and
Critical_impact 7-Jan-00 Requireme
Delay in Customer Definitely_likely 9 Planning and
ns
selecting
Client User Stories
Critical_impact 2-Jan-00 nts not
UAT of Customer Highly_likely 7 Requirements
Moderate_imp User
doesnot available to
Informed in
4 available 1
Milestone Customer Somewhat_likely 3-Jan-00 Management
Provide SIT
act stories for
provided
Release Work Order
client
Critical_impact 7 – Home Customer Highly_likely 7 and UAT
Delay in
Minimal_impac each
data
activities
31-Dec-99 Page and Internal Not_likely 31-Dec-99 environment
release
t sprints
dependenc
Critical_impact 6 Departmen
Approval
We need to of Customer Somewhat_likely 4 activities
by Creating BCP
ySet back
Infra issue up Follow-up
API accesswith
Critical_impact 6 t
requiremen Customer Somewhat_likely 3-Jan-00
Moderate_imp at
in Customer PM
through
4 ts placeinto
Delay Customer Somewhat_likely 4-Jan-00
act
Moderate_imp Customer
control development
Follow-up with
4 requiremen
Delay inthis Customer Somewhat_likely 3-Jan-00
act
Moderate_imp end
kind of environment
Customer
Followup with
PM
4 t approval
TDD
wrapper
Unavailabili Customer Somewhat_likely 3-Jan-00 Continuous
act
Moderate_imp issues Customer PM
4 approval
developme
ty of UAT Customer Somewhat_likely 3-Jan-00 follow-up with
Continuous
act
Moderate_imp
4 nt SIT
&
Customer
by Customer Somewhat_likely 3-Jan-00 customer with
follow-up
act
Moderate_imp
4 Customer
environme
API Customer Highly_likely 6-Jan-00 API analysis
customer
act Less not
Items
Critical_impact 6 nt may
change
We Internal Somewhat_likely 4 by Creating BCP
Minimal_impac discussion
initially
lead in in to Frequency
Item identifiedof
2 Delay Customer Highly_likely 6-Jan-00
t
Moderate_imp sdelay
identfified
Due in RAtoofin discussion
not
Verify
mapping
the
4 approval
Delay Customer Highly_likely 6-Jan-00
act phase
during
resource
support the with traceability
access and
Critical_impact 7 and in
approval
Delay Customer Highly_likely 7 Verify the
proposal
unvailbility
delivery in matrixof VPN
login
Critical_impact 7 allocation
and
approval Customer Highly_likely 7 access and
case
phase
at
Delay BCP
client in is accounts
Critical_impact 7 of
allocation
notresource
and planned Customer Highly_likely 7 login of VMs
side
Infrastructu
testing Delay in
Critical_impact 5-Jan-00 of resource
allocation Customer Somewhat_likely 5-Jan-00 Detectableand
Accounts
is not
re
low client Infrastructure
Critical_impact 5-Jan-00 of resource Customer Somewhat_likely 3-Jan-00 source
UAT defect
code
Moderate_imp happening
readiness
business readiness at
3-Jan-00 Delay
Communic
At client in Internal Highly_likely 6-Jan-00 and client
act
Moderate_imp and
at
understand
client
the client site
Delay in sign
3-Jan-00 sign off
ation
Failure
side gap Customer Somewhat_likely 3-Jan-00 demo
act build is on
site
ing off from client
Critical_impact 5-Jan-00 from client
between
Selecting
Communic
regression Customer Somewhat_likely 3-Jan-00 Detectable
Moderate_imp hold
3 team gap
User
ation
testing and is Internal Somewhat_likely 3-Jan-00 UAT
act
Critical_impact 5-Jan-00 Clientwhich
stories
between
done in Internal Somewhat_likely 3-Jan-00 Detectable
Critical_impact 5-Jan-00 Stability
sprints
sales
client team
is Customer Highly_likely 6-Jan-00 Detectable
Critical_impact 5-Jan-00 and Client
expecting
Due to old Customer Highly_likely 6-Jan-00 Detectable
Moderate_imp unstable
Health
2-Jan-00 us to do
Technolog Internal Somewhat_likely 3-Jan-00 Detectable
act
Moderate_imp feature
issue/unpla Request
No/Delayed from
3-Jan-00 ythe same Customer Somewhat_likely 3-Jan-00
act
Moderate_imp specificatio
nned client
Frequent
response
More effortsfrom
2-Jan-00 in our as Internal Somewhat_likely 3-Jan-00
act ns
leave/ Absentism
client
customer
are taken on by
Critical_impact 8 well
During in their Internal Definitely_likely 10
Resignatio Env statusfor
resources
No/Delayed
Critical_impact 7 enviornme
proposal
Dependenc Customer Highly_likely 7
Moderate_imp ns R&D
response from
5 nton
ynot
Complexity Internal Somewhat_likely 6
act
Moderate_imp client
5 visualized
customer
of
Client
SDMX has Customer Somewhat_likely 5
act
Critical_impact 6 Improper
if feasible
to
technology
not prepare Customer Somewhat_likely 3-Jan-00 Check the
client
or not
Env
provided approach
requiremen
the SME povided by
t client in the
on time scope document
Check the
Improper approach
client povided by
Critical_impact 6 The Customer Somewhat_likely 3-Jan-00
Critical_impa requiremen client in the
Delay/No
Customers 5-Jan-00
business
The
Testers vendor Client is busy Customer Somewhat_likel Delay/No
6
ct t y5-Jan-00 scope
response
response on on
from
Critical_impact 5-Jan-00 teamnot
may
need is
ti be Customer Somewhat_likely
Moderate_imp document
the
the queries
queries
Vendor on
4-Jan-00 busy/not
deliver
given
Onsite the
time Vendor Somewhat_likely 4-Jan-00
act raised
raised
the delivery
No/Delayed
Critical_impact 6 available
H/W
and
UAT
The on
proper
will Customer Somewhat_likely 6
Moderate_imp status
response from
5 time
KT
help
RG
business
The session
us to
vendor Vendor Somewhat_likely 5
act No/Delayed
customer
Critical_impact 5-Jan-00 to
address
sessions
teamnot
may have is Customer Highly_likely 6-Jan-00 Detectableafter
Moderate_imp response on
follow-up from
2-Jan-00 complete
the
are
The
busy/not
deliver issues
not the Internal Somewhat_likely 3-Jan-00 Detectable
act customer
conducting
In each RGafter
RG
Critical_impact 6-Jan-00 knowledge
and
conducted
business
available
H/W on Customer Somewhat_likely 5-Jan-00
follow-up
session
session, on
Critical_impact 7 about
resolved
as
do
time
RG per
not Customer Somewhat_likely 6 In each RG
Business conducting
different RG
application
the
planned
have
sessions same session,
unit has session
requirements
In RG session,
level
their
frequency
proper
are itself
not different
decided to are
business
provided unit
Critical_impact 7-Jan-00 clarity
conducted on Customer Highly_likely 6-Jan-00 requirements
go with the
The for
started
the same
giving
Critical_impact 7-Jan-00 the
as per Customer Somewhat_likely 4-Jan-00 are provided
started giving
plan
resources
Resource to products
requirements
Critical_impact 8 requiremen
planned
The Customer Highly_likely 7 for the same
requirements
cover
are
working not1 on-on No/delayed
with
In thisthe
plan
Requirement
Critical_impact 8 ts from all
frequency
business
Business Customer Somewhat_likely 5 products
Check
product for
boarded
other
Current responses
No/delayed
Check
gathering the
Critical_impact 5-Jan-00 stake
do
unit not
hasthe Internal Somewhat_likely 3-Jan-00 resources
all geos
having
assignment
system from the check
responses
resources
session,
Critical_impact 5-Jan-00 holders to
have
decided Internal Somewhat_likely 3-Jan-00 assignments
required
/new
don't use recruiters
from the
assignments
the forms
Critical_impact 7-Jan-00 proper
go with the Customer Highly_likely 6-Jan-00 as per thefor
technical
resources
any recruiters
as
which
Critical_impact 6 clarity
plan
The toon Internal Somewhat_likely 4 MAPS the
per OCR
reportis
skillson
not
standardiz MAPS
to be report
Critical_impact 6 the
cover
resources
Resource 1 Internal Somewhat_likely 4
boarded
ed forms implemented
Request from
Critical_impact 8 requiremen
product
are
working
Current not for
on-
on Customer Highly_likely 7
Moderate_imp client
Frequent
4 ts
all
boarded
other
system from
unstablegeosall Customer Somewhat_likely 4
act
Moderate_imp Absentism
3 Client
stake use
having
assignment
don't
feature Side
the Somewhat_likely 4
act Critical_impa Health Internal
Resource
Customers 5-Jan-00
Team
Shared
holders
required
/new
any
specificatio
issue/unpla Internal Highly_likely 7
Moderate_imp ct going on ML Frequent
3 members
resource
technical
resources
standardiz
ns
nned Customer Somewhat_likely 3-Jan-00
act
Moderate_imp Absentism
Frequent
3 on
and
skills
not
ed
leave/ leave
client
forms
on Customer Somewhat_likely 3-Jan-00
act Absentism
Critical_impact 8 controls
Complexity
boarded
Resignatio Internal Somewhat_likely 5 Performing PPM
Critical_impact 8 of
nsthe
allocation
Complexity Internal Somewhat_likely 5 Performing
functionality
of the delay
Control inCharts
Critical_impact 6 Sudden Internal Somewhat_likely 4 Team member is
Customer
to be is
functionality
Resignation response
not motivatedfrom
Critical_impact 6 Client Customer Somewhat_likely 6 Delayed
Moderate_imp resources
Complexity
implemente
to
of key
busy be client because
and unplanned
responses or no
3-Jan-00 Customer Somewhat_likely 4-Jan-00
act d the
dependanc
of
Complexity
implemente
resource of not
leaves
Moderate_impa 4 Customer Customer Somewhat_likely 5 delay inincrease
response from
ct yd
functionalit
of the
resources availability
Performing
Client
response from for
Critical_impact 7-Jan-00 Internal Somewhat_likely 4-Jan-00
ydependancy
to be
functionalit CF
PPM project.
Performing
client because
Critical_impact 7-Jan-00 Internal Somewhat_likely 4-Jan-00
yimplement
to be Control
of not Charts
Critical_impact 8 Complexity Internal Somewhat_likely 5 Performing PPM
ed
implement Response
availability not
Critical_impact 8 of the
Approval
Complexity Internal Somewhat_likely 5 Performingfor
Moderate_imp ed
functionality
of the CF project.
received
Control within
Charts
2-Jan-00 dependenc Customer Somewhat_likely 3-Jan-00
act unstable
Health
to the required
Moderate_impa 3 y be
functionality
Approval Customer Somewhat_likely 4 Response not
Moderate_imp
ct feature
issue/unpla
implemente
to be
dependency timeframe
received within
3-Jan-00 Customer Somewhat_likely 3-Jan-00 CR request
act
Moderate_imp d
specificatio
nned
implemente Frequent
the required
2-Jan-00 Internal Somewhat_likely 3-Jan-00
act d
ns
leave/ Absentism
timeframe
Moderate_impa 4 unstable Customer Somewhat_likely 4 CR request
ct Resignatio
feature
Moderate_impa 3 Health Internal Somewhat_likely 4 Frequent
ct ns
specification
issue/unpla Absentism
s
nned leave/
Resignation Key resource
Critical_impact 6 Approval Customer Somewhat_likely 6 User complaints
sOMS
dependency going on on application
Critical_impact 8 Internal Customer Somewhat_likely 4 Follow up for
Critical_impa agreement marriage leave performance
updates
Customers 5-Jan-00
Reports Internal Highly_likely 7
ct unstable
not received and another
Moderate_impa 3 stories
We may to Internal Somewhat_likely 4 To be identified
Moderate_imp
ct feature
lead to resource goin Request
when the from
4 be Customer Somewhat_likely 3-Jan-00
act
unstable
inappropriat on ML client
project
contract is
3 assigned to Customer Somewhat_likely 3-Jan-00
act
Moderate_imp ns
feature
e delivery in milestone
Request from
getting expired
4 BHABHA Customer Somewhat_likely 3-Jan-00
act
case wenot are client
and
N/A accordingly
3 squad
N/A Internal Somewhat_likely 4
act not able to
ns plan.
Moderate_impa 5 yet
Approval
understand Customer Somewhat_likely 6 delay
Schedulein
Moderate_imp
ct Customer
dependency slippage from
3-Jan-00 matured
the Customer Somewhat_likely 4-Jan-00 response
act Response
Moderate_impa 4 Customer
requiremen Customer Somewhat_likely 5 client in
delay
ct
Critical_impact 7 Response
The
t testing Customer Somewhat_likely 6 response fromof
Slow progress
Minimal_impact 1 team is busy
Tool Internal Somewhat_likely 4 client
SIT
experience with
Moderate_impa 5 with some
experience
Approval Customer Somewhat_likely 6 tool lacking with
Response
ct
Minimal_impact 2 other
lacking
dependency
Usage of Internal Not_likely 2 team
missingin within
Brainstorming
priority
new error estimation
the required
sessions during
work
routine timeframe
Team meeting
component and code
not reviews
understood
accurately
Failure
Health
Pressure
Selecting
Moderate_imp issue/unpla
needs to
3 User Internal Somewhat_likely 3-Jan-00 UAT
act
Moderate_imp nned
be put from Frequent
3 stories in Internal Somewhat_likely 3-Jan-00
act leave/
sales end Absentism
Moderate_impa 3 sprints
Customer Customer Somewhat_likely 5 Cannot be
ct Resignatio
on
identifying detected
Critical_impact 8 Complexity Internal Somewhat_likely 5 Performing PPM
ns
Customer
the
of the
Critical_impact 8 Complexity Internal Somewhat_likely 5 Performing
for
of faster
requiremen
functionality
the Control Charts
Critical_impact 5-Jan-00 Customer Highly_likely 6-Jan-00 Detectable
closure
t
to atbelater
functionality or
Critical_impact 6 PST is lost Internal Highly_likely 7 cannnot be
stage
to
to
Client provide
implemente
be
due to crash detect
d
us the
implemente Check the
Critical_impact 6 apporach
Pressure
of mailbox Customer Highly_likely 7 Detectable
d
extended
needs to be approach
Moderate_impa 4 was
Client Customer Highly_likely 7 Check the
Moderate_imp
ct UAT
put
apporach from povided
approachby
4 complex Customer Highly_likely 6-Jan-00
act sales
support
was end on client
povided
Response in bythe
Moderate_impa 3 and
Approval not Customer Somewhat_likely 4 Response
ct Customer
complex
charges
dependency scope
client
missing
missing in the
within
within
Moderate_impa 4 user not
Items Customer Highly_likely 7 Item identified
for
and faster document
ct
Critical_impact 7 initially
friendly
no
closure ofnotor Customer Somewhat_likely 4 scope
the document
not required
required
mapping
Execution
Moderate_imp user
identfified
licenses friendly
not timeframe
with
method traceability
timeframe
5 Approval
to provide Customer Somewhat_likely 6
act during
provided theas matrix
Moderate_impa 5 Approval
us the
dependenc Customer Somewhat_likely 6 Response
ct
Critical_impact 8 proposal
planned
dependency
Resources Internal Highly_likely 8 missing
Check the within
yextended
phase
Critical_impact 6 are not
UAT
Sudden support Internal Somewhat_likely 4 the required
technical
Team member skills is
Critical_impact 6 trained
charges
Resignation
Client isas Customer Somewhat_likely 6 timeframe
of the
not resources
motivated
Delayed
per
of
busy the
key Failure to and unplanned
responses or no
Critical_impact 6 Approval Customer Somewhat_likely 6 Email approval
project
resource identify that Email
leaves
response approval
increase
from
Critical_impact 5-Jan-00 dependenc Customer Somewhat_likely 5-Jan-00 missing
Critical_impa requiremen UAT should missing
Customers y5-Jan-00
t Internal Somewhat_likel Client
4
ct have required y4
Moderate_impa 4 Machine Internal Somewhat_likely Brainstorming
ct failure/ data or
Critical_impact 6 Due to old Customer Highly_likely 7 Detectable
natural
Technology scenarios Frequest
Critical_impact 7 Integration Internal Highly_likely 8 Frequest
calamaities releases of
Critical_impact 6-Jan-00 dependenc Internal Highly_likely 7-Jan-00 releases of
Accounting
Response
Critical_impact 7 y
Scope Customer Highly_likely 8 Accounting
Response
Scope extension
missing within
Critical_impact 6-Jan-00 Customer Highly_likely 7-Jan-00 extension
Critical_impa creep
creep Communicatio missing
the required within
Customers 5-Jan-00 Internal Somewhat_likel 6
the required
ct n Gap y4 timeframe
Critical_impact 6 Communica Internal Somewhat_likely Detectable
timeframe
Moderate_impa 3 tion gap
Visa Internal Somewhat_likely 4 Outcome of Visa
ct
Moderate_impa 3 between
duration
Short onsite for Customer Somewhat_likely 4 processing
Follow-up
Constant with
ct sales team
sanctioned
support
Resource followup
DeLaRue ONPC
on
Critical_impact 6 and Client Customer Somewhat_likely 6 Follow-up with
Critical_impact 5-Jan-00 request
unavailabili Customer Somewhat_likely 5-Jan-00 (which
the inturn
required
DeLaRue on
Moderate_imp can
N/A followup
3 ty
N/A Internal Somewhat_likely 4 set
the of
required
act with customer)
Minimal_impact 2 Data Internal Somewhat_likely 4 hardware
Schedule
set of
migration for Onsite travel
slippage
Moderate_impa 3 Resource Internal Somewhat_likely 4 Schedule
hardware
plan
ct
Moderate_impa 3 activity
unavailabilit
Resource Internal Somewhat_likely 4 slippage
Schedule
ct
Moderate_impa 3 y
unavailabilit
Resource Internal Not_likely 3 slippage
Schedule
ct
Critical_impact 7 yunavailabilit
Resource Customer Somewhat_likely 5 slippage
Schedule
Moderate_imp 5 yResource
unavailabili Customer Somewhat_likely 5 UAT defects
slippage
Critical_impact 7
act ty
unavailabili
Resource Vendor Definitely_likely 9 Schedule
Critical_impact 7 ty
unavailabili
Resource Vendor Somewhat_likely 5 slippage
Schedule
unavailabili
Resource Vendor Highly_likely 8 slippageto add
Unable
unavailabili
No Customer Highly_likely 8 the references
Response
Moderate_imp 4 Resource
ty
feedback
Communic Customer Somewhat_likely 4 of
missing
Response
required within
Schedule
Critical_impact 6-Jan-00
act unavailabili
Resource
from gap
ation Customer Somewhat_likely 4-Jan-00 Webservices
the
missing
Moderate_imp slippagewithinin
required
4-Jan-00 ty
unavailabili
Resource
stakeholde Customer Somewhat_likely 4-Jan-00 UAT defects
timeframe
the
Tellering
required
act Schedule
Unable to add
Critical_impact 6-Jan-00 ty
unavailabili
Resource
rs Vendor Definitely_likely 8-Jan-00 module
timeframe
slippage
Schedule
the references
unavailabili
Resource
No Vendor Somewhat_likely 4-Jan-00
slippage
of
Response
required
unavailabili
feedback Vendor Highly_likely 7-Jan-00
Webservices
missing
Response withinin
from Customer Highly_likely 7-Jan-00
Moderate_imp Communic the
missing
Tellering
required within
3-Jan-00 stakeholde Customer Somewhat_likely 3-Jan-00
act ation gap module
timeframe
the required
Critical_impact 6 rs
Delay in Customer Somewhat_likely 4 Followup with
identifing timeframe
customer on the
Moderate_impa 5 Improper Customer Somewhat_likely 4 Frequent
ct
Critical_impact 6 the
Data list of CR
customer Internal Somewhat_likely 4 CR detection
Customer
Schedule
Moderate_impa 3 by
managemen
migration
Data Internal Somewhat_likely 5 and approval
feedback
slippage
Schedule
ct
Critical_impact 6 Customer
tLack of
activity
migration Internal Somewhat_likely 4 slippage
Involve SP
Critical_impact 6 activity
Sharepoint
Data Customer Somewhat_likely 6 architect to
Schedule
Critical_impact 6 expertise
migration
Data Internal Somewhat_likely 6 review the
slippage
Schedule
Moderate_imp activity
migration defects
slippageand
N/A
3 N/A Internal Somewhat_likely 4
act activity resolution given
by team and
assist them.
Critical_impact 6 Network Customer Somewhat_likely 4 Unable to
Moderate_impa 3 down,
User Customer Somewhat_likely 4 connect the VM
Incremental
ct
Moderate_impa 4 Internet
interrupting
No feedback not Customer Somewhat_likely 4 Machines
report willand
Schedule
ct
Critical_impact 7 working
the
from
Data Sudden
Customer Highly_likely 7 server
provide
slippage
User the
complaints
Critical_impa migration
stakeholder
migration details
on on
application delta
Customers 5-Jan-00 Resignation of Internal Somewhat_likel 4
ct sprocess
activity by y7 update
performance to
Moderate_impa 4 Reports are key resource
Customer Highly_likely Required
ct modifying
not to GST Client
reports
Critical_impact 7 Due
the data at Customer Highly_likely 7 No dataare not
Moderate_impa 3 provided
incorporatio
Different by Internal Highly_likely 8 received
Comparein fromtime
file
source
Client in
ct
Critical_impact 6 n
versions
HDD crash in source on Internal Somewhat_likely 4 client in
version on both
Monitor time
Critical_impact 6 time
systems
staging
Proper data and Customer Somewhat_likely 5 the
performance
Check data of
Critical_impact 6 live
not
Same Internal Somewhat_likely 4 environments
the serverbefore
properly
Continueus
Minimal_impact 1 environmen
provided by
resource
Unavailablit Internal Not_likely 2 execution of
monitoring
Incomplete 3rd
ty of prod
Client
usage resources
party usage
Critical_impact 6 Various Customer Highly_likely 7 Use
Moderate_impa 5 environmen
challenges
Unavailablit Customer Somewhat_likely 4 plackage/templa
Download /Print
Constant
ct
Moderate_impa 1 tUnavailablit
yare of part of Customer Somewhat_likely 4 tes
functionality
Check thewithOR
followup
ct
Moderate_impa 4 this
Scope of change
yrequired Customer Somewhat_likely 4 check for chart
customer
availiability
Closly of
hardware/s
Business responsiveness
business
ct
Moderate_impa 3 Change
Migration Vendor Somewhat_likely 4 monitoring
The
once theuser
migration the
ct
Critical_impact 6 oftwares
user
tools
Customer Customer Somewhat_likely 4 before
requriemnets
tools must
Constant sprint be
development
Moderate_impa 3 limitations
followup on
Unavailablit Customer Somewhat_likely 4 planning
analysed
followup
Check
and thewith
testing
ct
Critical_impact 6 ySign of off/
Unavailabilit Customer Highly_likely 7 properly
Followupby
customer
availiability
completed, with a
of
Moderate_impa 3 Concerned
yBusiness
of proper
Sharepoint Internal Somewhat_likely 4 technical
business
PM on
Frequenty
story the
is readyperson
userdata
ct person
user
data during
resources before
availability
interaction
to mark UATaswith
Moderate_impa 5 Delay from
unavailabilit Customer Highly_likely 7 No feedback is
Moderate_imp
ct UAT
Client starts
team members
received
Done from
5 Stories
y Customer Somewhat_likely 6 Impact on
act
Catastrophic_i personnel
mpact
10 rolled overin
recruitment Internal Highly_likely 8 client
quality
not indelivery
achievingtime
providing 100% billing
Critical_impact 8 in
of next
no skilled
buffer
sign-offs Internal Highly_likely 8
Moderate_imp sprint N/A
3 resources
resource
N/A to Internal Somewhat_likely 4
act
Critical_impact 8 not party
backfill
3rd upto Vendor Highly_likely 7 Build availability
Critical_impact 8 not
the mark
billed
Connectivity Customer Somewhat_likely 6 Not able to
Critical_impact 8 submitting
failure
resource
3rd party Vendor Highly_likely 8 connect to the
Build availability
the
during
not builds CITRIX loginafter
Critical_impact 8 build
for testing Vendor Highly_likely 8 Build failed
submitting
annual
delivered using
Smoke valid
Critical_impact 8 Environmen Customer Somewhat_likely 6 1. ValidTest
credentials user not
the
leaves
for
t not builds
testing
ready able to connect
Moderate_impa 5 Additional
for testing Customer Somewhat_likely 6 additional
by
scope Party
for 3rd
testing, to the
ct
Moderate_impa 5 Request
not stable for Vendor Somewhat_likely 6 due to required
components unstable
ct User
added
running Accessfor environment
added
builds over and
Catastrophic_im 10 Dealy
request in not Customer Highly_likely 8 sign
2. off
Useragreeddelay
account
pact additional
getting above
Catastrophic_im 10 delay
processed inSign Customer Highly_likely 8 sign off delay
not created
inventory for
pact cycles
off
getting
Moderate_impa 4 by Bupasign PM Internal Definitely_likely 10 testing
ct
Moderate_impa 5 offs for test
Governmen Vendor Highly_likely 7 Will be detected
ct cases
t will after GST details
Moderate_impa 4 Internal Definitely_likely 10
ct
Critical_impact 7 anounce
Existing Internal Definitely_likely 10 are announced
GST
resource details by
TeamGovernment
getting
Critical_impact 8 Existing
by Mar/Apr Internal Somewhat_likely 4
Moderate_imp was
act
3 N/A on the
resource Internal Somewhat_likely 4 N/A
disconneted
Moderate_impa 5 project
was
We are on thefor
at a Customer Highly_likely 8 from
Verifythe the
ct
Critical_impact 7 long
project
lower time
We are at a for Customer Highly_likely 8 network
inventory
Verify the for
and
long
version
lower needed
time than versions
frequently
inventory due
for
Critical_impact 6 Long
athechange in Internal Somewhat_likely 4 Ask the team to
and
version needed
leave/resign than versions
to slowness
inform leave
Critical_impact 6 due
athe to
project.
change in Internal Highly_likely 7 by weather
Critical_impact 6 enterprise
the
of key of the
natural
Scope Customer Highly_likely 8 plans
and
condition
Multiple wellable
not in to
the project.
version
enterprise
resource advance
Moderate_impa 3 calamaities
project in
Increase Customer Somewhat_likely 4 complete
changes
By tracking in their
the
the
ct version
no of tickets requirement
work
third I tool
Critical_impact 8 insufficient Customer Somewhat_likely 6
Critical_impact 6 Not using Internal Highly_likely 7 with
not delayed
if theachieving
note pad is
bandwidth feedback
Critical_impact 8 note pad
for buffer
no DGSL- Internal Highly_likely 8 100%
not usebillingin while
Moderate_imp while uploading
N/A
Impact on
5 Bupa
N/A Linkto
resource Internal Somewhat_likely 4
act
Catastrophic_i uploading quality delivery
Schedule
10 Line
backfill
recruitment Internal Highly_likely 8
mpact the folder Slippage
Impact on
Critical_impact 8 billed
of Highly_likely 7
Catastrophic_i on skilled
resources
correct Internal
quality delivery
10 resource
resources
not
recruitment
trained
servers Internal Highly_likely 8
mpact
Moderate_impa 3 Bcoz
during
not
in
of of New
upto
skilled Customer Somewhat_likely 4 While accepting
ct
Critical_impact 6 template
Cause
annual
the mark
Functional
resources of it Customer Somewhat_likely 4 the Request
Detection
Minimal_impact 1 will
Mode
Cause
leaves
Areas
not lead
upto of to Customer Not_likely 1 Detection
TAT
Failure
the mark
Moderate_impa 3 Cause Internal Somewhat_likely 7 Detection
Moderate_imp
ct N/A
3 N/A Internal Somewhat_likely 4
act
Discussed
with the
Detection [D] [D] Risk handling customer Action Plan
Strategy about (Mitigation)this
[how readily it can [Values in drop functional
be detected] down are based hold trainee
Add in China
Easily_Detectable 3on Severity used 126 Marginal 1 Mitigate market
Aras hasbut
backup
for calculating arrange
agreed the
resources to in
Easily_Detectable 3 RPN] 45 Negligible Mitigate Evaluation
call onthose
utilize
team
Maximum 23-06-
this
version
2020
capacity
can
possible bewith ofto VFS
real fix
Easily_Detectable 1 24 Negligible 1 Mitigation
Asked Photoshop/Fla
delivery head
customer long-pending
groomed
scenarios / /
Easily_Detectable 3 126 Marginal 1 Mitigate for sh 16.00
follow
@
Discuss
Create installed/to
up
local with
hrs.
and
Risk mitigation
Resource
proper 3rd issues/chang
trained
data
be installed
Latest
user onwill tobeon
update
Office
Easily_Detectable 3 48 Negligible 2 Customer
Work
agree closely
upon fora
Management
party
Risk control
packages/ - es
perform
taken
Regular
one
–schedulefor
RFP
machine, other
from
machine so
Easily_Detectable 2 48 #REF! 1 Data.
to make sure
with
Templates
mitigation
Risk control / - regions.
support
customer
Project
thus
submitted
that enabling
machine work.so
on
Not_Detectable 8 16 #REF! 1 Infrastructure
Handle
all stake it as
contingency
mitigation
Risk control / - to
Managed
that
Process
Health
UNICEF
1. address
oncethe
06-July-2020
can be used same
BRD to
shall
Easily_Detectable 2 108 Marginal 1 is
Change
such ready
holders. tickets.
contingency
mitigation
Risk control / - Final
maintain
outside
Such
can
be
checkup
team
QA
sign beround
devised
offneeds is as of
to
Easily_Detectable 2 60 Negligible 2 before
Requests
However
Otherwise
discussion
Datamatics SITis in/
give
contingency
mitigation
Risk control / - team
resource
replicated
provide
per
to make
Regression
received, planned sure at
Easily_Detectable 2 90 Negligible 3 UAT
discussion
wait-time
such
going
domain. /onProd
tickets In on48
contingency
mitigation
Risk control / - utilization
deployment
development
feedback
interval
the
Testing
Change data and in
from
Work
in
Easily_Detectable 2 54 Negligible 4 with
any
hrs
case SLAUNICEF
expected
issue time
contingency
mitigation / and
/will
maximum
rigorous
the
order financial
also
testing
internal
Highlighting
requirements help 3
Easily_Detectable 1 54 Negligible 5 response
remains, Team will
contingency flow.
in case
environment.
days
Testing
systems
provided
this
will risk
be of
will
are
to to
Easily_Detectable 2 144 Marginal 6 members
be counted can
Risk mitigation treatedattrition
be
made
Datamatics
takeconducted
customer
Peer asin
Review
their
Easily_Detectable 2 32 Negligible 1 from the 3rd
Team member is Risk Accepted CR. with
available
and
regular
of
officethe clearly
And Test on
Cr
Easily_Detectable 2 32 Negligible 1 working
-
Followup day with
not motivated and 3 defined
time
Schedule
Risk
interval
Scenarios
process
desktops to avoid
control test
–will
to as-
Somewhat_Det 5 120 Marginal of
client/PO to
unplanned leaves cases
any
adjusted
Mitigation
Delay
well
be
Followup
home delay
followed.
asand to
inactive with
Easily_Detectable 3
ectable 48 Negligible 1 submission,
set priority of
increase
Easily_Detectable 3 36 Negligible 1 Risk mitigation work. with the
provide
requirement
involvement
Also
client/PO
leading
user
keep
stories
theto
to
Risk mitigation in release.
new
gathering
of the
resources
provide Release will
Easily_Detectable 2 32 Negligible 1 commercial
advance.
Risk mitigation Also date.
cause
Product
motivated
overall delay
scope to
Easily_Detectable 1 72 Negligible 2 impact discuss
Risk mitigation
Raise in
Owner
reduce
and
Manually
risk with user stories and
priority
Easily_Detectable 1 21 Negligible 2 Datamatics
Risk mitigation
client and development
Client
resignation
of
insertion QAdata
Easily_Detectable 1 16 Negligible 1 in
willdetail
IOM
Anil isto in
provide
follow up and
team.
rate. go-live
Requirement
from drupal
Easily_Detectable 2 1 sprint to
provide
assigned
laptops UAT and
4of
s2.inInadvance.
backend
Risk mitigation Highlight casethe
Easily_Detectable 3 3 Negligible 1 planning
environent
grooming
resources who for
Follow-up
Immediate confusion
risk during in
Somewhat_Detectab 4 96 Negligible Mitigate with the will work
meeting release from
in
le customer PM
escalation to requirement
weekly
Highlight
home of 2 instatus
the
Easily_Detectable 2 48 Negligible 1 case
tasks any
Customer with Highlight
Follow-up understandin
call
risk
each with
customer
during
location the
Easily_Detectable 3 60 Negligible 1 confusion.
Highlight the
with i.e.g, it
customer
higher
weekly
risk will
during
Nasik be
status and
Easily_Detectable 2 32 Negligible 1 customer PM
Follow-up important
Highlight
In case ofand the
to
customer PM
Follow-up discussed
Mumbaiy
during
management
call
weekly
with mandatory with calls
status
Easily_Detectable 2 32 Negligible 1 customer and
important to
customer with
Follow-up
Questions with
customer
call
have Plan
office Client
with
Highlight well
closures, the
in in
and
Easily_Detectable 2 32 Negligible 1 follow-up.
customer and
If
customer
Follow-up
been shared call.
during
customer
risk
advance during
Datamatics
with required calls theand
Easily_Detectable 2 32 Negligible 1 follow-up. If
Easily_Detectable 2 56 Negligible 1 IOM team during
customer
with weekly
More
time
will
highlight
required
calls
status
required
RA
provide to
to get more laptops
call
meeting
from withHOTUStowill 4
Somewhat_Detectab 4 48 Negligible Mitigate management
highlight
resources to
who
le clarity.risk
Raise it with
with We customer
help
staff
IOM to
and and
Easily_Detectable 2 28 Negligible 1 management
IOM
will have
to from
work
Somewhat_Detect client and
Raise risk with 1. during
expedite
coordinate
IOM
provide to calls
4
Marginal 2 provide
plan
home Defineto2 do
able 6 168
up with VMs
follow and
client
Raise risk requirement
accordingly.
provide forin VPN
Easily_Detectable 2 98 Negligible 1 access
call
Share
eachwith
communicati
Team ato
should
location
follow and
client up phase.
If
accounts
SharePoint
the
i.e. plan
Nasik risk andstill
Easily_Detectable 2 98 Negligible 1 Accounts
Marisa
Infrastructure
on
have on
properto &
follow up occurs
soon
development
One
1. once
Mumbaiy dayBRD
Easily_Detectable 2 98 Negligible 1 access that
Monday
Pre-
ensure
understandin
Followup toand with
negotiate
with
workshop
sign required
off is for will
Easily_Detectable 3 108 #REF! Version
will
requisites
the
g be
client/PO
fromproject abletoisto
Risk mitigation set a
intranet
be revised
provided
received,
Easily_Detectable 1 24 Negligible 1 Control
sort
well
on the and
functionality
track
priority RFC
and of
Risk mitigation Change schedule
content
to our team setup
in
Easily_Detectable 3 84 Negligible 1 existing
46
inadvance
and
monitored
and
user technical
storiesto
by the Anand
Risk mitigation requirements
Easily_Detectable 1 16 Negligible 2 source
ensure
with
closely
point
in
In advance.
future ofcode
we
view
3
Mitigate Rathi
will be
Easily_Detectable 1 24 Negligible get the
customer
which
Also
months discusssign
willprior and
Risk mitigation treated Business as
Easily_Detectable 1 12 Negligible 2 offUse
do
2.
help
user
notice
Sales
Informasap
follow
to
stories
to
team
WTO up
be
Mitigate teamAnd
MRF
CR.
Ask to be Cr
Easily_Detectable 1 24 Negligible 2 escalation m
understand
in
given
to
that detail
beteam to in
Mitigate rasie
process
Employees to hire
will to
Easily_Detectable 3 126 Marginal atrix for
the
sprint
client
involved
needs issuesfor
to to be
newfollowed.
be
plan resource
their
Easily_Detectable 1 42 #REF! handling proj
raised
planning
renewal
get
releasedtheand ofand
for Support
Also
leaves keep in
Easily_Detectable 3 36 #REF! ect issues
will
meeting
contract
testing
they be need able
donein toto
Risk mitigation advance resourceson
Easily_Detectable 2 32 Negligible 1 andper
resolve
case
as
complete delays
ofthe the
any the
Risk mitigation monthly motivated to
Easily_Detectable 3 36 Negligible 1 samebefore
confusion.
process
UAT
reduceandto Un Water and foll
basis
Highlight
Easily_Detectable 3 240 Marginal Highlight the team release
Somewhat_Detect resignation
identify
Work closely to make sure Inf
5 245 Marginal delay to
Raise it with date.
able rate.
backup
Highlight the challenges on ve
Easily_Detectable 2 60 Negligible customer
client
Highlight
andthein 2. In casetoof
resources,
Highlight inUn Water and foll
Easily_Detectable 3 75 Negligible statusto
follow-up
delay
Highlightmeting
the confusion
case of long in
Easily_Detectable 3 72 Negligible 1 Avoid to in
customer
delay Created new
requirement
leave.
table structure
status meting
customer in understandin
status meting considering all
g,
theitscenerions
will be
discussed
and showcase
with
it Clientfor
to client in
approvla
call.
Created new
table
Setup
structure
Weekly
Followup with
considering
meeting with
the client and
Delayed Avoidcontrol -
Risk all the
customer to
Easily_Detectable 3 72 Negligible 1 Riskthem
ask control to -
responses or no 4
mitigation
Risk control
/ - scenarios
discuss the
Easily_Detecta 3 108 Marginal mitigation
check the /
response from contingency
mitigation / and and
status
Easily_Detectable 3
ble 108 Marginal 2 contingency
status
Discuss ofwithH/W
Client contingency showcaseany
highlight it
Easily_Detectable 3 75 Negligible 2 delivery
Get
WTO the and with
test
to client
delay
Highlight in for the
Easily_Detectable 3 108 Marginal 2 Risk control - Setup ifWeekly
Vendor
cases
check to
we m
approval
responses.
same in
Easily_Detectable 3 75 Negligible 2 mitigation
Risk control
/ - Followup
plan
reviewed
can the with t
send
Risk control Also highlight
WSR/status
Easily_Detectable 2 84 #REF! contingency
mitigation / - installation
from
some
the
meeting
senior
sameand
Highlight in
this
Easily_Detectable 2 24 #REF! mitigation
contingency / timelines who
resource
contingency WSR
ask
risk to
in
Easily_Detectable 3 126 Marginal 2 accordingly.
knows
onsite to
the
conduct the
WSR/status
Highlight the
Easily_Detectable 3 126 #REF! 2 Risk control - Highlight
system
speed up well.
the
the
Risk control RG
meeting
risk session
to with
mitigation / - UAT
Coding
as per
management
customer
work is in
mitigation
Risk
contingency / -
control and
changed
This sign
has off to
contingency
mitigation / planned
and
WSR/status
Highlight ask this
Easily_Detectable Marginal 1 process.
Highlight
Create
make use this
buffer
3 168
contingency
been
frequency
business
meeting
to customer toof
and
Easily_Detectable 2 80 Negligible 3 to
resources
large
highlighted fonts by
Risk get proper
ask
in them to
Easily_Detectable 3 168 #REF! 1 Risk control
control -- Highlight
Recruitment
providing
with
as risk
clarity on
freeze less
requirements to
the
this
Easily_Detectable 2 80 #REF! 3 mitigation
Risk
mitigation
Risk // --
control
control Highlight
head
training
number
BSP soand ofthe
to
that
contingency
mitigation
Risk control/ - requirements
plan
gathering to
Easily_Detectable Negligible 1 follow-up
some
tickets
they more on
Somewhat_Detect 3 72 contingency
mitigation
contingency
mitigation
/
/ from can
provide
session allon take
and
5 120 Marginal 1 contingency the
resources
one
care screen
in time
able contingency stakeholders
requirements
ask them to
Easily_Detectable 3 168 Marginal 1 onboarding
and
so
to move
that it to
provide
Easily_Detectable 3 72 #REF! 1 of
maintaining
required
Highlight
information
production this
Somewhat_Detect Risk control - standard is
Ask
5 120 #REF! 1 mitigation
Risk control/ - resources.
sufficient
Create
visible
for testing buffer
from
able forms and to
Employees
Ask
Easily_Detectable 3 168 #REF! 1 contingency
mitigation
Risk control/ - documentatio
Highlight
1. onceGo
distance
before BRDthis sign off is receiv
unique
plan
Employees their to
Easily_Detectable 2 32 Negligible 1 Risk mitigation
contingency
mitigation / n.
Also
Live. keep resources motivate
identifiers
leaves
plan their in for
Easily_Detectable
Confirm the leave 3 36 Negligible 1 Risk mitigation Risk
contingency Ask
2. InEmployees
Another control
case of -confusion in requ
2 page in on
advance
leaves
dates with the Easily_Detecta 3 126 Marginal mitigation
option which /
identification.
monthly
Risk mitigation advance on
Not_Detectable
resources 9
ble 108 Marginal 1 contingency
BSP might
basis and
Risk mitigation monthly
Easily_Detectable 3 36 Negligible 1 Monitor
go for and is,the in
identify
basis
Get
Easily_Detectable 3 120 Marginal 3 Mitigation control
Monitor
case of charts
backup
identify
confirmation
Codingwise and
Easily_Detectable 3 120 Marginal 3 Mitigation week
Monitor
delay, to thefor
resources,
backup
from
Monitor
Unit
control client
testing all on
charts in
Somewhat_Detectab 5 120 Marginal 3 Risk control - every
Create
make feature
buffer
use of
le mitigation case
resources,
availability
the
effort
week sub- of
and
wise long forin
of
Easily_Detectable 3 108 Marginal 4 Risk control/ - resources
and
Setup
staging
leave
compare
meeting by
contingency
Risk mitigation
mitigation / case
his
every
providing
with of
required
processes
recalibrate feature
Clientin long byat
Easily_Detectable 2 40 Negligible 1 once
services
contingency leave
performing
resources
50%
and
training
and compare
highlight to11 as
Easily_Detectable 2 40 Negligible 1 Risk mitigation sufficient
Get
production
PPM analysis
sufficient
Risk mitigation completion
per
some
any plan more
delays
confirmation 11
and
Easily_Detectable 3 120 Marginal 2 data
data points
points
resources
send
and
Risk mitigation Follow
from at more
clientupand on
Easily_Detectable 3 120 Marginal 2 with
Schedule
with the
the
maintaining PPB
PPB
reminder
frequent
with
Ask client
availability for
for
of
Easily_Detectable 3 120 Marginal 2 Risk mitigation compare
frequent
Monitor
to calls
all
thecompare
sufficient
intervals
feedbacksamefor
Employees
his required
sub- & to
Easily_Detectable 3 120 Marginal 2 Risk mitigation with
Monitor
the client
siginificant
documentatio thefor
resources
sensitive
handle
plan
processes
Risk mitigation requirement
control their the
chartsas
at
Easily_Detectable 1 12 Negligible 1 difference
siginificant
n.
per plan
phases
Schedule
leaves
50%
week wise inand for
Easily_Detectable 1 12 Negligible 1 Risk mitigation difference
understandin
Follow
send up
reminder with
with
Risk mitigation advance
completion
every
client feature
for on
Easily_Detectable 2 32 Negligible 1 and
g,
for and
the replaceQuery
same
suffecient
and
feedback at more
compare &
Easily_Detectable 3 36 Negligible 1 the trial
resolution
frequent limits
once
slack
basis
handle sufficient
andthe
Easily_Detectable 2 32 Negligible 1 Risk mitigation with
and
Schedule
intervals
11 original
use
data points for
identify
Schedule
frequent with
calls
Easily_Detectable 3 36 Negligible 1 Risk mitigation data
Wireframes
Ask points.
Employees
sensitive
with the PPB
suffecient
backup
with client
to compare
plan the
during
phases
to
Sharing
slack
resources,
theiroffor in
requirement
leaves
discussions
Discuss
the in
siginificant and
required
DLR
case to
understandingof data
long
advance
Sales
difference
agree isupon onand
Somewhat_Detectab 4 144 Marginal 1 Periodic Periodic
temples
involved
,leave
and Query
monthly witha
basis
le
Confirm the leave verification planning
replace
performance
Risk the
control towith
Not_Detectable 10 360 Critical 1 Follow up schedule
re-estimate
sample
correct
resolution
and
Discuss
give identify
thewill set
data.and
User
best of-
dates with the Easily_Detecta 3 126 Marginal 2 trial
testing
and limits
mitigation
all stake
process with
be
/
use
backup
proposal
stories in
Followup
original
performed bywith
data to
resources
Easily_Detectable 2
ble 24 Negligible Mitigate reschedule
contingency
holders.
Wireframes
owners from
resources,
exploring
detail
client
Discuss
points.
identify in
for the in
the
User
Easily_Detectable 2 32 Negligible 1 Risk mitigation and Team
during
case
both
best
re
of
option
plan
will
the
long
performance
Sprint
Risk mitigation stories
user
with stories
team in to
Easily_Detectable 1 12 Negligible 2 discussions
continue
leave
and
branches
bottleneck for
of
Risk mitigation one have
planning
to
detail
be minimal
asigned
in
Easily_Detectable 2 32 Negligible 1 impact week
commercials
BSP for of UAT
theon
meeting
to
Sprint
BHABHA
Easily_Detectable 2 24 Negligible 1 mitigation Resource
project
workshop
project joine
team.
planning
Somewhat_Detectab 4 120 Marginal 1 Status reporting related
Datamatics
timeline. Train
le
Easily_Detectable 1 20 Negligible 1 Risk mitigation meeting
team
activities.
the team will on keep
Easily_Detectable 1 20 Negligible 1 Risk mitigation weekly
the
However
Discusstoolstatus to
and
Easily_Detectable 3 126 Marginal 1 Risk control - meeting
arrive
agree
wait-time
Highlight at with
upon towilla
Somewhat_Detectab 6 24 Negligible 3 mitigation
Raise /
it with third
accurate
schedule
customer
be counted
Highlight partywith and
the
le contingency
client tools
estimations
all stake
followup
challenges and for of
Easily_Detectable 3 90 Negligible 1 Raise it with from
Plan
product the in
well 6th
Easily_Detectable 1 4 Negligible 5 clientcontrol -
Risk holders.
the
delayed
advance
working
Code availability
reviewsTeam
the
day
vendors
will
of the
changescontinue for
testing
in
mitigation / time
of
resolving required any
contingency for
team one
requirement
from UNICEFweek
submission,
integration
on project
during
staff and the
issues.
leading
related
project to
coordinate
commercial
activities.
execution If
accordingly.
However
impact.
phase
the riskwith stillwait-
time will be
client/PO to
Ask
set priority of
Employees to
user stories
plan their
in advance.
leaves in
Also discuss
Risk mitigation advance on
Easily_Detectable 1 12 Negligible 2 user stories
Easily_Detectable 3 36 Negligible 1 in detail in
basis and
Not_Detectable 10 150 Marginal 1 Risk control - sprint that
Ensuring
mitigation identify
Easily_Detectable 3 120 Marginal 2 Mitigation / the
planningall
Monitor
contingency backup
requirements
the sub- the
Easily_Detectable 3 120 Marginal 2 Mitigation meeting
Follow-up
Monitor inon
Mitigate resources,
are
controlformally
processes atin
Easily_Detectable 3 126 Marginal 3 case
Sign ofcharts
off any
with
case
signed-off
more
The
week of long
wise by
frequent
POC for
Not_Detectable 8 336 Critical 1 Mitigate confusion.
Client
Regular
leave
the internal
intervals
every for
weeklyfeature
before actual
back
Easily_Detectable 3 126 Marginal 1 Risk
Mitigatecontrol - client
sensitive
andand compare
execution
Follow-up
up on
Easily_Detectable 3 84 Negligible 1 mitigation
Risk control/ - phases
sufficient
Sign
was
The off
restoration with
created
POC 11to
Easily_Detectable Negligible 1 contingency
mitigation / data
Client
be
for done
beforethispoints onceit
actual
and
3 84 with the PPB
Not_Detectable 3 36 Negligible 1 contingency
Raise it with in months
execution
was
Plan well in
inwas
to compare
align
created with for
Somewhat_Detectab 6 168 Marginal 2 client it with
Raise advance
showcased
Plan
the well the
siginificant in
le client it with config
this
time
advance and audit.
itfor
requiredthe was
Easily_Detectable 1 28 Negligible 2 Raise to Client
Request
difference for
client it with showcased
from
time
additional HOTUS
required to
Easily_Detectable 3 90 Negligible Raise approval.
Discuss
Client for and agree upon a sch
Easily_Detectable 3 90 Negligible 1 Raise staff
from
licenses and
HOTUS in
client it with Discuss
approval.
coordinate
Critical
staff and
and
Easily_Detectable 2 128 Marginal 4 client
Risk control - advance
agree
Commence upon a
accordingly.
coordinate
changes
schedule with
with If
Somewhat_Detectab 5 120 Marginal 3 mitigation
Risk control/ - the
Create
the project
riskhas buffer
still
contingency accordingly.
respect
DGSL
all stake
after training to If
le
Easily_Detectable 3 108 Marginal 4 mitigation
Risk control/ - resources
Setup
occurs
the risk meeting
still by
contingency
mitigation / BSP
proposed
holders.
the
with ToR
resources
providing Clientfor a
Easily_Detectable 3 108 Marginal negotiate
occurs
Critical
contingency However
have
HTML
training
and towait-
been
based
highlight
Easily_Detectable 3 108 Marginal revised
negotiate
changes
time on any for -a
with
Verify the UAT 6 pointed
Risk
receipt
some
any control
more
delays
schedule out
Easily_Detecta 1 24 Negligible revised
DLR
respect
expected to to
data resources
to DeLaRue
Mitigation
printing
schedule (withand
Easily_Detectable 3
ble 48 Negligible 1 Mitigate communicate
In
BSP process
response
maintainingToRwill of
for their
DHC/CPS
constraint
identifying of
the
Easily_Detectable 3 126 Marginal 1 Mitigate BSP
MRF
be
have to
counted
sufficient be
been
Raised review
should
additional
resource and with
Raised the rasie
from to thehire 3 rd
Easily_Detectable 3 168 Marginal 3 the procured
documentatio
pointed
DHC/CPS out
issue decision.
publish
field
the
new mapping
required
resourcefinal
Easily_Detectable 3 168 Marginal 3 issue with
with client
client working
hardware
n.
to DeLaRue
should
release
required
skill set. in
day of
Raised for Support
submission,
Easily_Detectable
Verify that the 3 168 Marginal 3 Raised the the specifications
for
DGSL theirhas
publish
timelines
receipts). final by
issue leading toOct
Easily_Detectable
Nasik Developer 3 168 Marginal 3 issue with
with client
client by 20thand
review
release
proposed
17th control
DLR
Risk
commercial Oct
to ‘17.-
Easily_Detecta 2 72 Negligible 5 17.
decision.
timelines
HTML by
has understood the finalisebased
impact
Mitigation the
Easily_Detectable 1
ble 24 Negligible 1 Mitigate In
17thfuture
receipt Oct3‘17.
requirments approach
months prior by
Easily_Detectable 1 12 Negligible 1 1. Can send Verified
1. Followup
printing the
(with
Mayur as hethe 20th
notice
with Octto beof
Travel 17.
Easily_Detectable 1 12 Negligible 1 1. Manage hardware
Coordination
constraint
having given to client
Easily_Detectable 3 108 Marginal 7 RaisedVisa
Raised
onsite thebut
the
support Desk
with
additional
DLR
DLR
for
ONPC
implementati
to
finalised
renewal
to
of
Easily_Detectable Marginal 7 Travel
by
issueONPCcost need
with client 2.
on Advance
convince
from
3 108 issuebearwith client
to Convince field mapping
communicate
the approach
contract
Ticket booking
Easily_Detectable 2 24 Negligible 1 2. customer
Resourceinjoin
Datamatics to
mitigation
customer to required
BSP
and a training
Integration
club 2/3 task /
Somewhat_Detectab 4 32 Negligible 7 Communicate
2. Advance ticket perspective.
Frequest
receipts).
procured
merge 2/3intasks is scheduled
deliveries
workshop
DLR to for to
le
Easily_Detectable 3 36 Negligible 7 the dates
Knowledge
Booking reminders
the risk
Knowledge
DLR
hardware still
totravel to
so that onsite
Status Report longer
in
be Jan'18
communicate
clientconducted
Easily_Detectable 3 36 Negligible 8 sharing
supportwith
Knowledge period management
exists
Knowledge
finalise
specifications
plan the
team
sharing with from
BSP
regarding
session
management web- isOct the
Easily_Detectable 3 27 Negligible 7 Communicate
increases. because
Frequest
approach
by 20th asbyit
team
the datesthe in DHC/CPS
services
UAT
conducted
session
remindersdates is in
on
to
Somewhat_Detect 4 140 Marginal 4 Raised is
20th
17. notOct
Follow sure
the 17.
Status Report Status
before
release
regular
conducted
client reports
20th
plan on
able
Somewhat_Detect 5 125 Marginal 5 issue with
Raised theclient the same
provided
Follow
interval
Oct
by ‘17.the
17th
regular
regarding Oct the
189 Marginal kind
DLR
Verified of
finalised
Easily_Detectable
able 3
105 Marginal
2 issue with
Raised the technical
provided datesthe
Integration
interval
17.
UAT
hardware in
will
Easily_Detectable 3 Project
issue
Raised with
theclient the approach
documentatio
technical
workshop
Follow-up
Status- reports
Follow
DLR theto
DHC
Easily_Detectable 3 192 Marginal 1 Manager
issue
Raised with
theclient be
and
with
DLR used
aDLR
implementati
n
documentatio
be for training
conducted
required
to for
Raised the provided
Follow
Conducted
As BSP the can
Easily_Detectable 3 192 Marginal 1 issue with
Raised theclient which
is
on scheduled
forfrom
integration
n
from
Accounting
communicate
Email, is
required used
Status
Raised
issue theclient technical
provided
session
not expose on
Somewhat_Detect
Somewhat_Detect 7 112 Marginal 6 issue with
Communicate
with during
in Jan'18
Datamatics
and
integration
DHC/CPS
Extension
BSP
call
Communicat
3rd
the Follow-
Novweb-
documentatio
technical
UAT.
on
able 4 140 Marginal 4 issue
Project with
the dates in client perspective.
development
and
before
release
services
up
e in with
email, 20th
DLR
plan
able
Somewhat_Detect Manager
Raised the n for required
documentatio
Accounting
webservices
5 125 Marginal 5 Status Report Follow-up
Email,
the
release
for
status risk
development
Oct ‘17.
getting Status
still
calls,
plan
able issue with
Raised theclient integration
n
extension
to for required
internet,
Easily_Detectable 3 189 Marginal 2 with
call
exists
by
the
status Follow-
17th DLR reports
Oct for
issue with
Raised theclient and
integration
understandin
Datamatics
Easily_Detectable Marginal Accounting
up with
Communicat
because DLR as
3 105
issue with
Raised
Communicate theclient
DLR
17. follow
responses
with
development
and
g.
will - DHC
DLR on theit
Easily_Detectable 3 192 Marginal 1 Extension
for
e
is in getting
not email,
Conducted
from
queries sure
BSP and on
issue
the dates
within client development
Mock
Easily_Detectable 3 192 Marginal 1 release
the
status
session
As same
concerns
BSP
user plan
calls,
on
can
Somewhat_Detect Status Report During UAT
environment
7 112 Marginal 6 responses
status
kind
3rd
not
stories ofreports
Nov
expose on
able deployment,
on the basis
Easily_Detectable 1 24 Negligible 1 - Get the so far from
with
Customer
hardware
Accounting
the BSPwill
DLR on
on
will
idenfitied CR identified
of
be provided
asked to the
Somewhat_Detectab 4 80 Negligible 1 Regular the
queries
Each
be user
used
extension and
webservices and
le from customer
Timesheet more
documentatio
share
every areas
the
efforts CR
Easily_Detectable 3 72 Negligible 6 Knowledge stories
concerns
Knowledge
which
understandin
to internet, is used
-Knowledge
Get the
updates from
n by
identified
spent BSP
on on
and
tasks
Easily_Detectable 2 30 Negligible 7 sharing with management
Operational
during
g.
Datamatics UAT.
estimation Accounting
Webservices.
Somewhat_Detectab 4 96 Negligible 1 team
sharing withready
Involvement of estimates
will
session
SP
will be
knowledge
architect
follow is the will
is
-SP
Get
team approval Extnsions
Datamatics
be shared
captured
conducted
shared with for
on
le
Easily_Detectable 2 72 Negligible 5 architect
Raise the issue will
Raising
During
Mock be aUAT ticket
accordingly his
which
will approval
regular
tester work
involved are toon not
Easily_Detectable 3 108 Marginal 3 with client
Perform pilot with
Perform Microsoft
deployment,
environment
so that pilot
completely
the
interval
review
to understand the
Easily_Detectable 2 24 Negligible 1 migration
mitigationand fix migration
Resource
identified
on the basis and
ident
the issues
development
known
development
defect
the
fix existing
the to the
and
issues
of
moreapproved
provided
Datamatics
of code
solution areas on
for
user
CR quota
thecan
from
documentatio
same
basis
be
and
carried process
Accounting
n byraising
BSP outof on
for
provided
and thus the
Extnsions
Webservices.
tickets
parameters with
existing
which are
Datamatics
concern team not
Easily_Detectable 1 24 Negligible 2 Raise the issue Datamatics
Easily_Detectable 3 36 Negligible 5 with client
Raise the issue works closely
Provide
Easily_Detectable 1 16 Negligible 4 with
Statusclient
Report to
message
Process makeshall sure
on
Team member is admin
SharePoint
be devised access
Easily_Detectable 1 49 Negligible 1 Raise the issue Mitigate byto
not motivated and 3 client
with Risk
to
2010
provide
setting Sourcecontrol
siteupand a -
and
Somewhat_Det 5 120 Marginal
unplanned leaves Target
Mitigation
email
feedback
replica up sites in
of with is
Somewhat_Detectab 4
ectable 112 Marginal 3 Risk control - Follow
available. Also
increase
le Mitigation communicatio
minimum
Production
BATA PMthe days
to to
Easily_Detectable 3 147 Marginal 2 Risk control - Escalate
optimal
n to the site
Easily_Detectable 3 72 Negligible 2 Mitigation
Code the perform
provide
impact
As confirmedof
internet
users
content
Somewhat_Detectab 4 96 Negligible 1 functionality for
Additional Detailed
unavailability
-with Keep
bandwidth the backup
2 versions migration
Report
of
client, BATA 2asitwell and
le
Easily_Detectable 3 90 Negligible 4 backup
Risk taken-
control of
Highlight
later, SVN
available. perform to
external
Mitigation Requirements
stakeholders
versions
as
Customer Database needs
and
Easily_Detectable 2 48 Negligible 1 Resource Add
increment
and trainee
escalate if
HDD/machine
Management to
on
get
backup their
TeamSenior
be
Not_Detectable 8 16 Negligible 1 Asked customer Maximum
directly
no
Managementpositive from
for proper 3rd programmed
machines
confirmation
resources
possible real in
Easily_Detectable 3 126 Marginal 1 Demo to clients production.
The
response
and POC
get from
buy-in
party packages/ (may
on
team
scenarios
before the be data
those
actual /
Easily_Detectable 2 40 Negligible 1 Customer Any
BATA
for
random) and
revision to in
Templates
followup accuracy
can
data
execution
environment bewill and
be was
Easily_Detectable 1 4 Negligible 1 Advance impacting
Client
Schedule
ensure
action will
that
tofor be key
be
and
intimation toPMPM groomed
taken
created
issue
Project
given from
will
cut /
be
off
Easily_Detectable 1 16 Negligible 1 Intimate the analyze
Client
the
taken
trained backupwill
for the
to be
about theavailablity
scope customer
this
immediately
metrics
dates
cost
informed and for
impact it so
was
prior to
Somewhat_Detectab 4 48 Negligible 1 Migration tools Team
can
rejected
perform
that be will
the same
le of Business
change
features and users
study showcased
escalated
confirmation
be
that
conduct presented a to to
Easily_Detectable 1 24 Negligible 1 Advance restored
Client
records
support
can
Client be will
for in
work.be
case
initiate
intimation the CR
to by the
on
due client
all
requirements
feasilbility
within
informed tothe delay
short PM/
prior
Easily_Detectable 1 12 Negligible 1 UAT planning if
Client Live
replicated
approval.
service will
desk. be
at
cycle
customer
taking about
inputs requirementrs
not
study
time
that
scenarios convered
theto sign-
verify
Easily_Detectable 1 42 Negligible 1 Customer willonbe given
Such
Datamatics
development
.off/Acceptanc
All the
cut
resource off /
in
what SoW type scope
Somewhat_Detectab 4 48 Negligible 1 contract
availablity
asked
Plan for sign
from
tobackup off
provide dates
deployment
will
testing
Anjali
planning
are toof of
for
migrate
out
le and
PM its
dataandin impact
resoureces Business
advance edata
-discuss
A can
spare
certificate
confirmation
will
one also
more
environment. be
help
with
Somewhat_Detectab 6 210 Marginal 1 Risk control - Follow-up
sessions
scope
migrated
machine
need to will
willand
le users
Mitigation on
in
Geosite
Subu all
case
escalate theof
about on
in
Easily_Detectable 3 90 Marginal 5 Mitigate be
once
be planned
used
completed
requirementrstheasdevel
attrition
New
either
case Libra
of Test
Easily_Detectable 3 240 Critical 1 Mitigate much
DB
Train
.within
All/ the
Web
environment.
retaining
in3nothe
resource
feedback.
advance
server
business and to
days will
Easily_Detectable 3 192 Critical 3 Mitigate planning
Introduce
current
Initiate team
next and
maximize
be keep
sessions will
Easily_Detectable 2 24 Negligible 1 mitigation Resource
or
phasereplacing
business and user join
updated
be
with planned
equally so
Easily_Detectable 3 168 Marginal 1 Mitigate Appropriate
clarify
avaialbility.
that at with
any
much
competent
agreement
respective in
Easily_Detectable 2 96 Negligible 1 Accept Team
time
advance willtowait
resources
owners
around
for for
availability
Easily_Detectable 3 192 Marginal 1 Mitigate connections
Project
maximize will
any
change
for
can1be
estimatedoubts
day. inthe If
Somewhat_Detectab 7 448 Critical 1 Transfer business
Build
schedule
during will user
be
/to
le the
switched
impact
avaialbility.
rejected of and of
Easily_Detectable 3 144 Marginal 1 Mitigate Datamatics
efforts
proceedings
unavailabilityneeds
that
schedule
testing
will machine
will
highlight and
Easily_Detectable 3 90 Negligible 1 Mitigate If
to
nextany
bephase
continues
if
thesuch arrived for
continue
any
at schedule
additional
if required. with
Easily_Detectable 3 90 Negligible 1 Mitigate If any
beyond
situation
corresponding
the previous 1 day,
related
work
additional
the sameis riskswill to
Easily_Detectable 3 240 Marginal 1 Accept occurs.
Continuous
costs
build
Bupa and
as soon it
required,
cycle
follow-up
would is
have anbe with it
Easily_Detectable 3 240 Marginal 1 Accept Continuous
as
wouldthe same be is
required,
impact
Customer
considered
follow-up onitwithforas
Somewhat_Detectab 4 160 Marginal 1 Mitigate identified.
Deploy
considered
would
schedule bethe and as
le getting
CR after
Customer
Team
Senior thefor
will
Somewhat_Detectab 6 210 Marginal 1 Risk control - BATA
CR and
considered
commercials
Sign
getting offPM toas
le Mitigation resource
estimate
Datamatics
ensure the in
the
Somewhat_Detectab 4 160 Marginal 1 Mitigate Include
CR and
approval
Sign offand somefrom
le the
impact
will
buffer team
confirmation
provide
Datamatics inthe who
the
Easily_Detectable 2 140 Marginal 1 Mitigate Record
Bupa
can
the KT
to
the
will separate
delivery
sessionsprovide date
so
Somewhat_Detectab 4 128 Marginal 1 Mitigate Rigourous
understand
corresponding
development
estimate for Unit
le
Easily_Detectable 2 24 Negligible 1 the
given
that
and
Need separate
to
they
System client.
can
additiona
mitigation the
costssystem
team
the and
of
same.
estimate for
Easily_Detectable 3 120 Marginal 2 Risk control - be
Test
Team referred
plans
to in
and
faster.
would
change
Upon
the
future.same. indodata
trigger
approval
Easily_Detectable 2 112 Marginal 3 Mitigation
Risk control - multiple
more
aCreate
change
mapping practice
thefor
of the approval
CR from
Upon
rounds of
Somewhat_Detectab 5 120 Marginal 2 Mitigation
Risk control - of the
request.
Bupa,
Create
of the tool
Administration
underlying the
CRbufferfrom
le Mitigation testing.
before
and
source
same
resources theby
shall be
Somewhat_Detectab 4 168 Marginal 1 Mitigate In process
Bupa, the of
le
Somewhat_Detectab 3 144 Marginal 1 Informed client actual
Monitoring
systems
added
providing
identifying
same
In process towith
shall the the
be
of
le about the skills development
Tool
ODS
Scope.
training
resource
added manually
identifying totowith
the the
Easily_Detectable 1 12 Negligible 1 Mitigate In process
phase starts of
set - which is or
some
the reuse
Scope.
resource
identifyingmore
required utility
with theb
Easily_Detectable 3 144 #REF! 4 Mitigate increase
build for other the
required resources
skill set. and
Not_Detectable 8 336 Critical 1 Mitigate for this the
In required
resource
process
projects
withof
Easily_Detectable 3 192 Critical 3 project skill
the set. in and
maintaining
required
identifying
Introduce the
Mitigate past
sufficient
skill set.
Easily_Detectable 2 40 Negligible 2 mitigation resource
Need
documentatio with
additiona
Easily_Detectable 3 240 Critical 1 the
Train
n. required
resource
Mitigate skill set. trainin
Easily_Detectable 2 112 Critical 1 Mitigate Ensure
Easily_Detectable 3 240 Critical 2 Mitigate coordinate with
Easily_Detectable 1 12 Negligible 1 Mitigate In process of
Easily_Detectable 1 24 Critical 1 Mitigate identifying
In process of the
Somewhat_Detectab 4 4 Marginal 1 Mitigate resource
In processwith
identifying the
of
le the required
resource
identifying with the
skill set. with
the required
resource
skill required
the set.
skill set.
Somewhat_Detectab 5 105 Marginal 1 Mitigate In process of
le
Easily_Detectable 2 24 Negligible 1 mitigation identifying the
To induct Buff
resource with
the required
skill set.
Responsibility Date REVISED REVISED Revised REVISED REVISED
Severity [S] [S] Occurrence [O] Detection [D]

[Range 1 to 10, [O] highest detection is 2, least
PM 23-Jun-20 with 10
Moderate_imp 1[Values in drop Somewhat_lik 4 [Values in likely to detect is 10
Easily_Detectable
actas highest down are ely drop down
PM 23-Jun-20 severity]
Minimal_impa 1 based on Somewhat_lik 4are based on Easily_Detectable
ct Severity used ely Severity used
DGSL & Client 43927 Minimal_impa 1for calculating Not_likely 1 for Somewhat_Detectable
PM / IT On going ct
Moderate_imp 5 RPN] Somewhat_lik 6 calculating Easily_Detectable
PM/TL 43888 act
Minimal_impa 3 ely
Somewhat_li 5 RPN] Easily_Detectable
PM On going ct
Minimal_impa 1 kely
Somewhat_li 4 Easily_Detectable
Developers On going ct
Moderate_imp 4 kely
Somewhat_li 4 Not_Detectable
Unicef 43802 act
Moderate_imp 4 kely
Unicef, act kely
Datamatics
Unicef
Datamatics
Unicef
Unicef
Client 43803 Minimal_impa 1 Not_likely 1 Easily_Detectable
PM 43195 ct
Minimal_impa 1 Not_likely 1 Easily_Detectable
Hire freshers in PM ct
43428 Critical_impac 6 Somewhat_lik4
the
DGLS Team, train
& Client 43810 t
them
Testingand create
team 43784 Moderate_imp 3 Somewhat_li 4 Easily_Detectable
aPMknowledge 43195 act
Minimal_impa 1 1
base Not_likely
kely Easily_Detectable
PM/PO 43780 ct
Moderate_imp 5 Somewhat_li 6 Easily_Detectable
PM 43780 act
Moderate_imp 5 kely
PM/TL 43226 act
Minimal_impa 2 kely
Project Manager 43696 ct
Moderate_imp 4 Highly_likely
kely 7 Easily_Detectable
PM 43697 act
PM 8/5/2019 ct
Minimal_impa 1 Somewhat_lik 4 Easily_Detectable
PM On going ct
Moderate_imp 4 ely
Highly_likely 7 Easily_Detectable
PM On going act
Critical_impact 4 Somewhat_li 7 Easily_Detectable
PM On going Moderate_imp 4 kely
PM On going act
Moderate_imp 4 Highly_likely 7 Easily_Detectable
PM On going act
PM On going act
Moderate_imp 4 kely
PM On going act
Moderate_imp 4 kely
PM 8/5/2019 act
Moderate_imp 4 Somewhat_lik 4 Somewhat_Detectable
PM act
Moderate_imp 3 ely
Project Manager act
Moderate_imp 4 kely
Project Manager 43605 act
Moderate_imp 4 kely
Moderately_s 4 Easily_Detectable
Moderate_imp 4 omewhat_likl
Moderate_imp 4 ey
omewhat_likl
PM/Sales act
Moderate_imp 5 ey
omewhat_likl
PM/TL 43196 act
Minimal_impa 2 ey
kely
PM 43205 ct
Minimal_impa 1 Not_likely
PM 43195 ct
Minimal_impa 2 Somewhat_li 4 Easily_Detectable
PM ct
Critical_impact 6 Somewhat_li
PM 43517 Minimal_impa 1 kely
Not_likely 1 Easily_Detectable
PM ct
PM act
Minimal_impa 1 kely
PM/Sales ct
Critical_impact 6 Somewhat_li
PM/Sales Critical_impact 6 kely
PM 43195 Minimal_impa 1 Not_likely
PM 43181 ct
Project act kely
Manager
Project
Project
Manager
Project
Manager
DGSL
Manager 43418 Minimal_impa 1 Not_likely 1 Easily_Detectable
ct
DGSL 43418 Minimal_impa 1 Not_likely 1 Easily_Detectable
Setup meeting PM ct
with
PM Client and 43434 t
highlight
PM any 43419
delays
PM 30-Nov-18
PM 15-Nov-18
PM Moderate_imp 3 Somewhat_li 4 Easily_Detectable
PM/Sales act
Moderate_imp 3 kely
PM 43434 act kely
PM 30-Nov-18
Project 03-Nov-18
Manager
Project 19-Nov-18
PM
Manager 43414
PM 43414
PM 10-Nov-18
PM 10-Nov-18
PM 43434
PM 43434
PM 43434
PM 30-Nov-18
PM 30-Nov-18
PM 30-Nov-18
PM 05-Apr-18 Minimal_impa 1 Not_likely 1 Easily_Detectable
PM 22-Mar-18 ct
Moderate_imp 3 Somewhat_lik 4 Easily_Detectable
Got the PM act
43405 Critical_impac ely
6 Somewhat_lik4
approval
PM of new 43332 Moderate_imp t3 Somewhat_li 4 Easily_Detectable
position(MRF)
PM 43332 act
Moderate_imp 3 kely
from
PM LOS Head 11-Jul-18 act
Critical_impact 8 Somewhat_lik 4 Easily_Detectable
kely
PM 11-Jul-18 Critical_impact 8 ely
Somewhat_lik 4 Easily_Detectable
Somewhat_lik 4 Somewhat_Detectable
PM 43252 Moderate_imp 3 ely
PM 1-Jun-18 act
Moderate_imp 3 Not_likely 1 Easily_Detectable
PM 43266 act
Critical_impact 8 Somewhat_li 4 Easily_Detectable
PM 43266 Critical_impact 8 Somewhat_li
PM 15-Jun-18 Critical_impact 8 Somewhat_lik
PM 15-Jun-18 Critical_impact 8 ely
Project Manager 43262 Minimal_impa 1 ely
Project Manager 11-Jun-18 ct
PM 43245 ct
PM 43242 ct
PM 25-May-18 act
Minimal_impa 1 Not_likely
PM 22-May-18 ct
Project 30 –May-18 act ely
Project
Manager 25-Apr-18
Technical
Manager 27-Apr-17 Moderate_imp 3
Architect/QA
Project Manager 11-Jan-17 act
Minimal_impa 1 Not_likely 1 Not_Detectable
Create buffer PM ct
resources
PM by 1-Apr-18 Critical_impact t6 Somewhat_lik 6 Easily_Detectable
providing
PM 43195 Minimal_impa 1 ely
training
PM to some 43186 ct
Minimal_impa 1 1
more resources Not_likely Easily_Detectable
PM 43332 ct
and maintaining ct
Service
sufficient 15-Apr-08 Minimal_impa 1 Somewhat_lik 4 Somewhat_Detectable
Project
Manager Manager
-
documentation. 17-Mar-17 ct
Moderate_imp 3 ely
PM Nikam
Vilas 43252 act
PM resource
One 1-Jun-18 act
Moderate_imp 4 Somewhat_lik
from
PM Nasik 23-Mar-18 act
Critical_impact 3 ely
Team
Projectwas
Manager 27-Apr-17 Minimal_impa 1 ely
brought in to
Project Manager 11-Jan-17 ct
Moderate_imp 3 ely
Mumbai
PM 9-Mar-18 act
location in May ct
PM 43179 Minimal_impa 1 Not_likely 1 Easily_Detectable
PM 43181 ct
PM 9-Mar-18 act
Minimal_impa 1 Highly_likely
kely 8 Somewhat_Detectable
PM 1-Jun-18 ct
Critical_impact 8 Somewhat_lik 4 Easily_Detectable
PM/Sales Moderate_imp 3 ely
PM 27-Apr-17 act
Critical_impact 7 Highly_likely 8 Not_Detectable
PM/Sales 17-Mar-17 Moderate_imp 3 Highly_likely 7 Easily_Detectable
DGSL 2/9/2018 act
Minimal_impa 3
DGSL 43140 ct
Minimal_impa 1 Not_likely 1 Somewhat_Detectable
Project Manager 27-Apr-17 ct
Project Manager 11-Jan-17 ct
Project Manager 17-Mar-17 act
Minimal_impa 1 ely
Project ct
Project Manager
Manager 27-Apr-17 Moderate_imp 3
PM 20-Jan-18 act
Critical_impact 8 Not_likely 2 Easily_Detectable
PM 3-Mar-18 Critical_impact 6 Somewhat_lik 4 Somewhat_Detectable
PM 14-Feb-18 Critical_impact 6 ely
Project 12-Jan-18 ely
Project Manager
Manager 43112
The LIVE data PM 43012 Moderate_im 4 Not_likely 1
could
Client be 17-Mar-17 Minimal_impa pact
1 Somewhat_lik 4 Somewhat_Detectable
restored
PM in the 17-Mar-17 ct
Minimal_impa 1 ely
UAT ct ely
Project
environment for 17-Oct-17
Project Manager
Manager 43025
proper testing
Project
by the internal 20-Oct-17 Moderate_imp 3 Highly_likely 7 Easily_Detectable
Project
client toManager
Manager verify 43028 act
Moderate_imp 3 Highly_likely 7 Easily_Detectable
The
all the scenarios PM act
42990 Moderate_im 4 Not_likely 2
requirements
PM 11-Jan-17 Moderate_imp pact
3 Somewhat_lik 4 Easily_Detectable
would
PM be On going act
Moderate_imp 4 ely
gathered
PM , On going act
Moderate_imp 4 ely
analysed , act
Moderate_imp 5 ely
Project
freezed by the 20-Oct-17
Project act ely 4
MumbaiManager
Manager Team 43028 Moderate_imp 5 Somewhat_li Easily_Detectable
Service
and then would 18-Aug-17 act
Minimal_impa 1 Somewhat_lik
Project Manager
be
Manager - 22-Jul-17 ct
Moderate_imp 7 ely
ProjectNikam
Manager
communicated
Vilas 20-Jul-17 act
to the Nasik
Project Manager 20-Jul-17 act
developer.
Project ManagerCode 21-Jul-17 act
reviews.
Project 14-Jul-17 act
Manager
Technical 14-Jul-17 ct
Architect /
Project 20-Oct-17 ct
Moderate_imp 4 Highly_likely 7 Somewhat_Detectable
Technical Lead
Manager
Project 01-Sep-17 act
Manager
Project 17-Oct-17 act
Moderate_imp 5 ely
Manager
Project 01-Sep-17 act
Manager
Project 10-Jul-17 act
Moderate_imp 4 ely
Project Manager
Manager 42930 act
Minimal_impa 1 ely
Not_likely 1 Somewhat_Detectable
Technical 42930 ct
Architect /
Project Manager 43028 ct
Moderate_imp 4 Highly_likely 7 Somewhat_Detectable
Technical Lead
Moderate_imp 5 Somewhat_li 4 Somewhat_Detectable
Moderate_imp 5 kely
Moderate_imp 4 kely
PM 31-Jul-17 act
Moderate_imp 3 Somewhat_lik
PM On going act
Moderate_imp 5 ely
Project Manager 12-Jul-17 act
Project Manager 30-Jun-17 Moderate_imp 3 ely
PM 30-Jun-17 act
Project Manager 02-Jun-17 act
Technical 14-Jun-17 Critical_impact 6 Not_likely 1 Easily_Detectable
Lead/Architect
Service 19-Jun-17 Minimal_impa 1 Somewhat_lik 4 Somewhat_Detectable
Manager - ct ely
Vilas Nikam
Project Manager 05-May-17 Critical_impact 6 Not_likely 1 Easily_Detectable
Technical 05-May-17 Moderate_imp 3 Not_likely 3 Easily_Detectable
Lead/Architect
Project Manager 05-May-17 act
Project Manager 05-May-17 act
Create buffer PM 23-May-2017 Critical_impac 6 Somewhat_lik4
resources
PM by 31-Mar-17 Moderate_imp t4 Somewhat_lik 5 Somewhat_Detectable
providing
PM 31-Mar-17 4-Sept-2018
act
training
DGSL to some 17-Mar-17 Minimal_impa 1 Somewhat_lik 4 Somewhat_Detectable
more resources
and maintaining ely
PM
sufficient 20-Feb-17 Critical_impact 6 Somewhat_lik 4 Easily_Detectable
PM
documentation. 31-Mar-17 Minimal_impa 1 ely
Moderate_imp 4 ely
Somewhat_lik 4 Not_Detectable
DGSLresource
One 11-Jan-17 act
Minimal_impa 1 ely
Not_likely 1 Not_Detectable
from
PM HR App On going ct
development
PM On going ct
Moderate_imp 4 ely
Team
PM was On going act
Moderate_imp 3 ely
alloacted
TEAM to CEO On going act
Moderate_imp 3 ely
App Team in act ely
PM
Sept 10-Dec-16 Critical_impact 6 Not_likely 2 Easily_Detectable
PM 15-Mar-17 Moderate_imp 3 Somewhat_lik 4 Easily_Detectable
PM 1-Mar-17 act
Moderate_imp 3 ely
PM On going act
Minimal_impa 1 Somewhat_lik 4 Somewhat_Detectable
PM 15-Feb-17 ct
Moderate_imp 5 ely
Highly_likely 7 Somewhat_Detectable
PM act
PM 18-Jan-19 ct
PM 06-Feb-19 Critical_impact 6 Highly_likely 7 Easily_Detectable
Service 01-Dec-16 Minimal_impa 1 Somewhat_lik 4 Somewhat_Detectable
PM
Manager - 12-Jun-17 ct
PM Nikam
Vilas 12-Jun-17 Critical_impact 8 ely
PM 12-Jun-17 Critical_impact 8 Somewhat_lik 5 Easily_Detectable
PM 12-Jun-17 Moderate_imp 5 Somewhat_lik 4 Easily_Detectable
PM 12-Jun-17 act
Moderate_imp 5 ely
PM 12-Jun-17 act
Minimal_impa 1 ely
PM 12-Jun-17 ct
PM 20-Oct-16 act
Moderate_imp 3 ely
PM 28-Feb-17 act
Moderate_imp 5 ely
Highly_likely 7 Somewhat_Detectable
PM 20-Oct-16 act
Team 20-Oct-16 act
Moderate_imp 3 ely
PM 20-Oct-16 act
Moderate_imp 3 ely
Service 31-Dec-16 act
Minimal_impa 1 ely
PM
Manager - 01-Dec-16 ct
Moderate_imp 4 ely
PM Nikam
Vilas 25-Feb-17 act
Critical_impact 6 Highly_likely 7 Easily_Detectable
PM 31-Dec-16 Critical_impact 6 Somewhat_lik 4 Somewhat_Detectable
Client 11-Jan-17 Minimal_impa 1 ely
Client 27-Apr-17 ct
Minimal_impa 1 ely
Client 27-Apr-17 ct
Minimal_impa 1 ely
PM 31-Aug-17 ctMinimal_impa 1 ely
Client 17-Mar-17 ct
Minimal_impa 1 ely
PM 31-Oct-15 ct
Minimal_impa 1 ely
Service ct
30.Jun.2015 Minimal_impa 2 ely
PM
Manager - 31-Mar-15 ct
Minimal_impa 7 ely
Prasad
PM Gajul 30-Sep-15 ctMinimal_impa 1 ely
PM 30-Apr-15 ct
Minimal_impa 1 ely
Client 11-Jan-17 ct
Minimal_impa 1 ely
Client 27-Apr-17 ct
Minimal_impa 1 ely
Client 17-Mar-17 ct
Minimal_impa 1 ely
ct ely
Client 11-Jan-17 Minimal_impa 1 Somewhat_lik 4 Somewhat_Detectable
Service ct
31.Aug.2014 Minimal_impa 1 ely
Manager - ct ely
Premal Desai
Detection Revised RPN If Revised RPN >= Initial RPN, revisit the risk. Contingenc Contingenc Contingenc
= S*O*D Using this risk reference, add another line of y REVISED y y
[D] action tracking REVISED Revised
Severity [S]
1 [Values in 4 Note: If Risk
10-Jun-20 leads toCustomer
: Informed Opportunity, aboutusethe
the [Range 1 [S] Occurrenc
drop down same Risk reference number in Opportunity to 10, with e
1are based on 4 10-Jun-20
23-Jun-20 : Informed Customer
Aras has arrange theabout
call onthe
23- 10 [Values in [O]
Severity used 06-2020 with VFS delivery head @ 16.00 hrs. as highest
same drop down
for calculating
03-Jan-00 4 23-Jun-20
06-July-20:: Client
06-Apr-20: Aras has
Latest arrange
agreed
update to thesubmitted
utilize
– RFP call
this severity]
on 23-. Minimal_i 1are based Not_likely
2 RPN] 60 06-2020
capacity
01-Aug-20:
25-Mar-20: with
to fixVFS
RPN delivery
long-pending
Final round
before of head @ plan
16.00
issues/changes
discussion
mitigation ishrs. mpact
is going on Severity
01-Jan-00 30 06-July-20:
for
on other
126.
ImpactAfter
has Latestdown,
regions.
taking
gone update
Managed
action the
due – RFP
to
RPN submitted
no. came . Minimal_i
to maintain
mitigation 2 used for Somewhat
01-Jan-00 8 01Aug-20
team
Since the 60:Final round
action.utilization
down toProbability
project and
isof of discussion
financial
occurrence
continuation flow.RPNis going
has2019
of no. is Moderate_
mpact 4calculating Moderatel
_likely
on
revised
Risk not
Ongoing
reduced to 4
occurred
Risk.
and
support, this Risk
risk isand
is is
gettinggetting
controlled. monitored
monitored
has been already taken impact RPN] y_somewh
07-Jan-00 128
20-May-20-No
closely
care. Change in RPN no at_likley
01-Jan-00 32 Risk not occurred and is getting monitored
0 closely
0
0
0
0
1 1 Impact has gone down, due to mitigation Minimal_i 1 Not_likely
31-Dec-99 1 action. Probability
Impact has gone down, of occurrence has
due to mitigation mpact
Minimal_i 1 Not_likely
Somewhat_ 4 reduced
action.
96 and risk isof
Probability controlled.
occurrence has mpact has
Impact Critical_im 7
Detectable 0 reduced and risk is controlled. gone pact
1 12 Impact has gone down, because of internal down, due
1 Peer
Impactreviews of the
has gone down,Testing
due team and active
to mitigation to
mpact
31-Dec-99 mitigation
1 30 involvement
action.
Impact of theofproduct
Probability
has reduced Owner.
asoccurrence
client/ has
Product mpact
1 30 reducedhas
Owner
Impact and risk down,
agreed
gone is that
controlled.
commitment
because client/to PO
75% mpact
31-Dec-99 8 of
hasScope
agreed
Impact is not
has gone possible
to provide due to
down,priority
due toof
unavailablility
use stories
mitigation mpact
Minimal_i 1 Somewhat
of Complete
for 2 Sprints
action. Scope.
in
Probability ofBusiness
in advance. Requirements
occurrence has mpact
Moderate_ 4 _likely
Somewhat
1 are
Impact has reduced as action has beenEffort
gathered
reduced and in
riskdue
is course. The
controlled. total impact
Minimal_i 1 _likely
Not_likely
31-Dec-99 and Story points are to be met as measure
1 4 taken.
05-Aug-19- The RPN number is reduced to 4 mpact
of Success criteria.
01-Jan-00 56 from 96 after identification of mitigation Moderate_ 5 Somewhat
01-Jan-00 56 plan impact
Minimal_i 2 _likely
Somewhat
56 Risk is monitored closely. Risk not occurred mpact
Moderate_ 5 _likely
Somewhat
01-Jan-00 and Closed
01-Jan-00 56 impact
Moderate_ 5 _likely
Somewhat
01-Jan-00 40 impact
Minimal_i 4 _likely
Somewhat
01-Jan-00 40 mpact
Minimal_i 4 _likely
Somewhat
01-Jan-00 56 mpact
Moderate_ 5 _likely
Somewhat
1 16 05-Jun-19: Reviewed, risk not occurred impact _likely
31-Dec-99 12 04-Jul-19: Reviewed, risk not occured
31-Dec-99 16 05-Aug-19- The RPN number is reduced to 4
16 from 96 after identification of mitigation Moderate_ 4 Moderatel
31-Dec-99 plan
31-Dec-99 16 impact
Moderate_ 4 y_somewh
Moderatel
Risk is ongoing is monitored closely impact at_likley
y_somewh
31-Dec-99 16 Moderate_ 4 Moderatel
02-Jan-00 60 Revised RPN 60 is less than initial RPN 108 impact at_likley
y_somewh
31-Dec-99 8 therefore
Impact hascontigency
gone down, plan
duenot
to to be
mitigation Minimal_i 1 at_likley
Somewhat
31-Dec-99 1 deployed
action.
Impact Probability
has gone down, of occurrence has
due to mitigation mpact
Moderate_ 3 _likely
Not_likely
31-Dec-99 8 reduced
Impact andgone
has risk down,
action. Probability isof
controlled.
occurrence has
due to mitigation impact
Moderate_ 3 Somewhat
31-Dec-99 24 reduced
action.
If Revised and
RPN risk
>=isInitial
Probability controlled.
of occurrence has the risk Minimal_i
RPN, revisit impact 1 _likely
Somewhat
31-Dec-99 1 reduced
and
Impact andgone
identify
has risk down,
is controlled.
Contingency Plan (use
because nextPO
client/ set mpact
Minimal_i 1 _likely
Not_likely
31-Dec-99 12 of columns)
has agreed
Revised RPNtorisk.
provide
12 is less priority of use
than initial RPNstories
24 mpact
4 Note:
RevisedIf Risk
in advance.
therefore RPN leads
contigency to Opportunity,
4 is less plan initial
than beuse126
not toRPN the mpact
Moderate_ 3 _likely
Somewhat
31-Dec-99 Risk reference
therefore
Revised RPN 24number
contigency in Opportunity
is lessplan
than not to be
initial RPN 42 impact _likely
therefore
Revised contigency
RPN 24 is lessplan
thannot to be
initial RPN 36
therefore
Impact hascontigency
gone down, plan
duenot
to to be
mitigation Minimal_i 1 Not_likely
action.
Impact Probability
has gone down, of occurrence has is
because team mpact
0 reduced and
planning riskinisadvance
leaves controlled.
hence RPN value mpact
reduced.
1/2/1900 3 Created new table structure considering all

the scenerions and showcase it to client for
approvla
02-Jan-00 3 Created new table structure considering all
Easily_Detec 3 the
72 scenerions and showcase it to client for Impact has Moderate_ 5
table 0 approvla gone impact
0 down, due
0 to
0 mitigation,
probability
31-Dec-99 12 Revised RPN 12 is less than initial RPN 84 of
31-Dec-99 12 therefore
Revised contigency
RPN 12 is lessplan
thannot to be
initial RPN 24 occurrence
0 deployed
therefore contigency plan not to be has
0 deployed reduced
1 1 Impact has gone down, due to mitigation Minimal_i 1 Not_likely

1 12 action. Probability
Impact has gone down, of occurrence
because teamhas is mpact
Easily_Detec 3 reduced
planning
72 and
leavesriskinisadvance
controlled.hence RPN value mpact
Impact has Critical_im 6
31-Dec-99
table 12 reduced.
Impact has gone down, because team is gone down
Minimal_i pact
1 Not_likely
31-Dec-99 12 planninghas
Impact leaves
goneindown,
advance and sprint
because team is since the
mpact
1 32 capacityhas
planning
Impact isleaves
decided
goneindown based
advance onand
since thesprint
holiday
project is recruitmen
mpact
Critical_im 8 Somewhat
1 32 plans
capacity
monitored
Impact is decided
has using
reduced PPMbased on the
asisaction
bieng holiday
performed
has been takenon tCritical_im
process
pact 8 _likely
Somewhat
plans
regular
to intervals
identify the complex was
4 96 Impact has gone down, functions and
due to mitigation, as pact
Critical_im
initiated 7 _likely
Somewhat
3 72 analyse them
documentation
Impact has in and
gone detail.
cross
down, duetraining has
to mitigation, pact
Moderate_ 5 _likely
Somewhat
31-Dec-99 3 motivated
Impact hasothers
probability of
gone to increase
occurrence
down, has their
because reduced impact
Minimal_i 1 _likely
Not_likely
1 3 knowledge
confirmation
Impact has gone has down,
given from
becauseclient for his mpact
31-Dec-99 32 resource
confirmation
Impact has availability
has down
gone given since
from client
projectfor
is his mpact
Critical_im 8 Somewhat
31-Dec-99 32 resource
monitored
Impact has availability
using
reduced PPM asisaction
bienghasperformed
been takenon pact
Critical_im 8 _likely
Somewhat
1 32 regular
to intervals
identify the complex functions
Impact has gone down since project is and pact
Somewhat
1 32 analysehas
monitored
Impact them in detail.
using
reduced PPM asisaction
bienghasperformed
been takenon pact
Somewhat
31-Dec-99 1 regular
to
Impact intervals
identify
has the
gonecomplex
down, functions
because ofand regular pact
Minimal_i 1 _likely
Not_likely
1 1 analyse
followup
Impact them
has with in
gone detail.
client
down, because of regular mpact
31-Dec-99 1 followup
Impact has with
goneclient
down, due to mitigation mpact
31-Dec-99 12 action.
Impact Probability
has gone down, of occurrence
1 1 reducedhas
planning
Impact and
leavesriskindown,
gone isadvance
controlled toas
duehence SRS
RPNis value
mitigationnow mpact
1 12 signed-off.
reduced.
action.
Impact Probability
has gone down, of occurrence
reduced
planning and
leavesriskinisadvance
controlled as SRS
hence RPNis value
now mpact
signed-off.
reduced.
0
10 10
Easily_Detec 3 72 Impact has Critical_im 6
1
table 36 01-Apr-18 : RPN No is revised to 24 from 36 gone pact
31-Dec-99 1 Impact has gone down, due to mitigation down, due
1 01-Apr-18
action. hastill
gone29-May-19:Risk
Impact Probability down, becauseNotclient/
of occurrence occurred-
has PO to
mpact
31-Dec-99 mitigation,
1 Closed
reduced
has and
agreed torisk is
provide controlled.
matured user
Impact has gone down, due to mitigation stories mpact
31-Dec-99 as
4 16 on priority
action.
Only very for BHABHA
Probability
Demanding team. has
of occurrence
Applications Are mpact
reduced documenta
0 Affected and risk is controlled. impact
tion and _likely
31-Dec-99 16 Impact has gone down, because of regular Minimal_i
cross 1 Not_likely
1 16 followup
Impact haswith
gone client
down, because of regular mpact
Minimal_i
training 1 Not_likely
3 36 followup with
Impact has gone client
down, but due to mpact
has
1 4 mitigation, probability of occurrence has motivated
0 reduced others to
1 2 Impact has gone down due to proper code increase
reviews their
mpact
knowledge
31-Dec-99 1 Impact has gone down, because client/ PO Minimal_i 1 Not_likely
31-Dec-99 12 has agreed
Impact to provide
has gone down,priority
becauseof team
use stories
is mpact
6 48 in advance.
planning
Impact leaves
has goneindownadvance
due hence RPNPOC
to proper value
is mpact
1 32 reduced.
made has gone down since project is
Impact impact
Somewhat
1 32 monitored
Impact has using
reducedPPM asisaction
bienghas
performed
been takenon pact
Somewhat
02-Jan-00 63 regular
to
Revised intervals
identify
RPNthe63complex functions
is less than initial and
RPN 126 pact _likely
9 504 analyse them
therefore
Revised RPN in detail.
contigency
504 plan not
is greater thantoinitial
be RPN Critical_im 8 Highly_like
deployed
336 therefore contigency plan has to be pact ly
3 63 Revised
deployedRPN 63 is less than initial RPN 126
therefore contigency plan not to be
03-Jan-00 4 deployed
The POC before actual execution was
1 1 created for this and it was showcased to
1 16 Client for approval.
1 1
0
0
1 16 Starting the project after ensuring training is Moderate_ 6 Somewhat
4 96 given inhas
Impact Hibernate transaction
gone down, due to management
mitigation, as impact
Somewhat
3 72 and negotiation
documentation
Impact the
has goneand schedule
cross
down, due towith
training the client
has
mitigation, pact
Moderate_ 5 _likely
Somewhat
to train theothers
motivated
probability resource
of who has
have
to increase
occurrence domain
their
reduced impact _likely
knowledge than to hire new resources which
may take more time
Easily_Detec 1 4 Impact has Moderate_ 5
4
table 15-Jan-00 gone down impact
1 4 Revised RPN 4 is less than initial RPN 126 since the 3
Moderate_ Somewhat
0 therefore contigency plan not to be LIVE data
impact _likely
0 deployed has been
restored
3 63 on UAT
02-Jan-00 63
Easily_Detec 1 8 Impact has Critical_im 6
1
table 12 Revised RPN 12 is less than initial RPN 24 done down pact
4 64 therefore contigency plan not to be since
mpact _likely
4 64 deployed communic
3 60 ation,
monitoring
02-Jan-00 60 & review
4 16 Only very Demanding Applications Are Moderate_
has 4 Somewhat
1 0 Affected impact
increased _likely
1 0
1 0
1 0
4 4
4 4
4 112
4 80
3 105
3 90
3 60
03-Jan-00 4
03-Jan-00 4
03-Jan-00 112
03-Jan-00 80
02-Jan-00 105
02-Jan-00 90
02-Jan-00 60
4 60
4 80
1 24
1 3
4 48
1 12
3 18 Tool tested and identified the defects. Fixed
4 16 the defects and
Degradation notstarted the migration.
noticeable Moderate_ 4 Somewhat
impact _likely
1 6 Developers are monitoring on day to day
1 9 basis during each batch migration
1 12
1 6
Somewhat_ 4 96 Impact has Critical_im 7
4
Detectable 80 Impact has gone down gone pact
3 147 Impact is same down, due
4 16 The approval from client was taken to code to
4 96 in both the functionality. mitigation,
as
2 48 Impact has gone down documenta
2 8 Since the project is continuation of 2016 tion and
8 128 support, this risk has been already taken cross
8 8 care.
The POC before actual execution was training
2 8 created for this and it was showcased to has
1 16 Client for approval. motivated
2 24 others to
4 48 increase
their
1 12 knowledge
1 12
1 3
4 16
6 210 Impact is same
1 4
2 112 Appropriate Trainings have been provided
1 42 and monitor
Training the work
provided closely
to the by sr.
new join team
resources.
4 16 members.
Degradation not noticeable Moderate_ 3 Somewhat
3 120 impact _likely
1 16
3 120
2 80
2 32
3 60
3 60
1 1
2 40
4 60
5 175 Impact has gone down
4 60
4 48
1 12
4 16 Degradation not noticeable Moderate_ 4 Somewhat
2 56 Impact has gone down, due to mitigation, impact _likely
2 84 severity andgone
Impact has probability of occurrence
down, due has
to mitigation,
4 96 reduced
severity andgone
and
Impact has the down,
detection
probability istomore
of occurrence
due nowhas
mitigation,
4 16 since teamishas
reduced.
detection done
more nowmore
sinceRND and
team practice
updates
4 16 on
thecommunity
leave plans version.
in advance.
The project got closed from client side.
4 16
1 4 bandwidth of DGSL-Bupa Link Line has been
4 16 increased now
1 4 2+ years experience .Net developers /
4 40 Trainees taken
Degradation notonnoticeable
board now Critical_im 4 Somewhat
1 28 Appropriate Trainings have been provided pact _likely
1 4 and overall
Velocity quality
of team has
has been
been improved
improved now
now
1 4 and consistently monitored
4 16
4 16
4 16
4 16
4 16 Quality Reduction Unacceptable to the Client Moderate_ 4 Somewhat
impact _likely
Contingenc Contingenc Contingenc Contingenc If Status
y y y y Contingenc
REVISED REVISED Detection Revised y Revised
RPN RPN >=
[O] Detection [D] = S*O*D Initial RPN
[D] (may need
[Values in highest [Values in to do RCA)
drop down detection drop down Using this
1are based Somewhat
is 2, least 4are based 4 Converted risk
on Severity _Detectabl
likely to on Severity to reference,
Issue
5 used for Easily_Det
e detect is 2 used for 20 None add Identified ICRA - POC
calculating
4 10
ectable
Easily_Det 2 calculating 32 another
Impact has
RPN] ectable RPN] gone line of
0 action
0 down, but
tracking
due to
0
0 mitigation,
Note: If
probability
0 of leads
Risk
0 occurrence to
0 hasOpportunit
1 Easily_Det 1 1 Noney, use the
reduced Identified
ectable Risk
andprocess the
1 Easily_Det 1 1 CR reference Identified Anand
Somewhat ectable
4 Somewhat 4 detection
will
112 be Pull Rathi
Not-Occur
_likely _Detectabl 0 isnumber
more in
followed. another
nowOpportunit
1 Easily_Det e1 1 Clientsince y resource
Identified
ectable we
/Product are with the
1 Easily_Det 1 1 None
installing Occurred All projects
1 ectable
Easily_Det 1 1 Ownerishas
Client same skills
Identified
environme
been from ISG
1 ectable
Easily_Det 1 1 already
Client
nt in 1has Identified
reviewing
informed Team
4 ectable
Easily_Det 1 4 been
Project
machine Identified Anand
ectable and
about risk
providing
estimation Rathi
4 Easily_Det 2 providing
1 ectable
Easily_Det 1 1 and
the
will
- be Closed
feedback
agreed.Acti
requireme
revised
ectable to
ntsthe
on
and plan
for Test
shared2
4 Easily_Det 2 40 Scenarios
alreadyin
Sprints
ectable with
4 Easily_Det 2 16 during
implement
advance,
stakeholde the
4 ectable
Easily_Det 2 40 Sprint
ed
hence
rs. risk
4 ectable
Easily_Det 2 40 successfull
is closed.
(Standard
4 ectable
Easily_Det 2 32 y , hence
Customer
estimation
4 ectable
Easily_Det 2 32 risk
will
methedelo
Customer is
be
4 ectable
Easily_Det 2 40 closed.
asked
gy
proviednot
Customer to
ectable provide
usedbefor
alternate
will
0 the
this
setup as
asked to
signature
project.)
UAT
discuss andthe
0 of
SITthe
approach thoughAPI
4 Easily_Det 2 32 to the
not beasusedper
ectable of API
4 Easily_Det 2 32 so
the that
implement
4 ectable
Easily_Det 2 32 dev.
ationteam
configurati and
ectable 0 will
on needed
requireme not
4 Easily_Det 1 4 wait
but
Project
nt thus atforleast
will
can Identified All
1 ectable
Easily_Det 1 3 final
can
be
reduce
None setup
put on
the Identified projects.
Anand
4 ectable
Easily_Det 1 12 release.
the
hold
impact and of Identified Rathi
All
ectable Thus
environme
Team
this
Involveme the
riskwill projects.
4 Easily_Det 1 4 If
developme
ectable nt
nt where
reconvene
of top
Contingenc
1 Easily_Det 1 1 Client
nt
testingwill isnot can Identified
ectable once
ymanageme
Revised
already
4 Easily_Det 1 4 Contigency
hamper.
be carried
required
4 ectable
Easily_Det 1 12 nt
RPN would
informed
revised
Contigency >=
out.
setup
be
Initial is
ectable 0 about
RPN
revised
available. isRPN
risk
less
required
(may
and
than
RPN need
Initial
is less
0 for
to doand RCA)
agrred.Acti
RPN
than Initial
monthly
Using
on plani this Occurred All projects
ectable contigency
RPN and
1 Easily_Det 1 1 in case
steering
risk
already
action isof Occurred All projects
ectable contigency
risk
0 committee
reference,
implement
found
action to
is
occurance,
review
add
ed
address of
found
additional to
the
another project
successfull
the
address risk
resources
status.
yline of
, hence
the
will risk
be
0 action
risk is
allocated
tracking
closed.
from
desk/resou
Note: If
rce
Riskpool.leads
to
Opportunit
0
Somewhat 6 Easily_Det 3 90 Highlight Not-Occur
_likely ectable 0 the delays
0 to the
0 Client and
0 escalate if
required to
0 the Clietnt
0 Senior
0 Manageme
0 nt
1 Easily_Det 1 1 None Identified

1 ectable
Easily_Det 1 1 in case of Occurred
Somewhat ectable
5 Easily_Det 3 risk
90 A new Not-
_likely
1 Easily_Det ectable
1 1 occurance,
None resource
Occurred occurred
1 ectable
Easily_Det 1 1 additional
None BA cum
Occurred Closed
4 ectable
Easily_Det 2 64 resources
Replaning Tester was
Not-Occur
ectable will
the be hired
5 Easily_Det 2 80 Replaning
allocated Not-Occur
4 ectable
Somewhat 4 112 remaining
the
Pull Not-Occur
from
work
6 _Detectabl
Easily_Det 3 90 remaining
another
Highlight
desk/resou Not-Occur
1 e
ectable
Easily_Det 1 1 work
resource
the
None
rce delays
pool. Identified
1 ectable
Easily_Det 1 1 with
to
Nonethethe Identified
4 ectable
Easily_Det 2 64 same
Client
Replaningskills
and Vaishali Shirshat:
Occurred
ectable from
escalate
the ISGif Change from As agile
Team Identified
ectable required
remaining
the to methodology is takes care
the Clietnt Occurred
5 ectable
Easily_Det 2 80 work
remaining
the
Replaning of mitigation in sprint
Identified
Senior
work
1 ectable
Easily_Det 1 1 remaining
the
None
Manageme planning while risk arrives
Identified
1 ectable
Easily_Det 1 1 work
remaining
None
nt from release planning , so
Identified
1 ectable
Easily_Det 1 1 work
None status should not be closed
Occurred
1 ectable
Easily_Det 1 1 in case of Identified
1 ectable
Easily_Det 1 1 risk
None Occurred
1 ectable
Easily_Det 1 1 occurance,
in case of Identified
ectable additional
risk
resources
occurance,
will be
additional
0 allocated
0 resources
from
will be
Somewhat 5 Easily_Det 3 90
desk/resou
allocated Pull Not-
_likely ectable rce
frompool. another occurred
desk/resou resource
Identified Closed
Vaishali Shirshat:
1 ectable
Easily_Det 1 1 Client
rce pool.is with the
Closed
1 ectable
None same skills Due to frqueent changes in
Identified
from ISG requirement life cycle is
4 ectable
Easily_Det 1 16 informed
PoojaThak chosen as Agile for the
about Team
ectable 0 kar hasrisk project instead of waterfall.
1 Easily_Det 1 1 and
joined
None and Closed
agrred.Acti This kind of risk is typically
1 ectable
Easily_Det 1 1 started
None Closed for waterfall and cant not
on plani
executing
ectable already be justified for Agile
LMS
0 implement
activities.
0 ed
3 Somewhat 6 36 successfull
Pull Senior Not-Occur
_Detectabl y , hence
skilled
e risk is
resource /
closed.
Tech Lead
from ISG
Team
for waterfall and cant not
be justified for Agile
1 Easily_Det 1 1 Client is Closed

1 ectable
in case of Occurred
6 ectable
Easily_Det 3 90 informed
risk
Take Not-Occur
4 ectable
Easily_Det 2 64 about
Replaningrisk
occurance,
additional Not-Occur
5 ectable
Easily_Det 2 80 and
additional
requireme
the
Replaning Not-Occur
ectable agrred.Acti
resources
nts
the into a
remaining
0 on plani
will
new
work be
phase
remaining
7 Easily_Det 1 56 Contigency
already
allocated
ectable or
workbacklog
revised
implement
from
points.
0 RPN
ed is less
desk/resou
than Initial
successfull
rce pool.
0 RPN and
y , hence
0 contigency
risk is
0 action
closed.is
found to
0 address
0 the risk
0
5 Easily_Det 2 60 Pull Closed
4 ectable
Somewhat 4 112 another
Pull Not-Occur
6 _Detectabl 3
Easily_Det 90 resource
another
Highlight Not-Occur
eectable with the
resource
the delays
same
with
to skills
thethe
from
same
Client ISG
skills
and
Somewhat 6 Easily_Det 1 30
TeamISGif LIVE data Not-Occur
_likely ectable from
escalate can be
Team
required to restored in
4 Easily_Det 1 12 the Clietnt
ectable UAT
Senior
Manageme
nt
Somewhat 2 Easily_Det 1 12 Impact has Not-

_likely
4 Easily_Det ectable
1 4 Contigency gone down occurred
ectable revised due to Closed
RPN is less regular
than Initial communic
RPN and ation,
contigency monitoring
4 Easily_Det 1 16 Shraddha
action is and
ectable Kulkarni
found to reviews
has joined
address
and
the risk
started
executing
LMS
activities.
4 Easily_Det 1 16 Shraddha
ectable Kulkarni
has joined
and having
KT from
LMS
Somewhat 4 Somewhat 4 112 Pull Not-Occur
_likely _Detectabl another
e resource
with the
same skills
from ISG
Team
4 Easily_Det 1 12 Rekha
ectable Navle to
continue in
LMS
Support
who will
replace
Shonali
4 Easily_Det 1 16
ectable
4 Easily_Det 3 48 Dhiraj to
ectable coninue in
LMS
Support till
Richa is
back
4 Easily_Det 1 16 Make
ectable existing
resources
work extra
Hours to
cover loss
of
resources
when team
size
reduces to
2
Risk Management - Guidelines
1 Risk Risk No. Risk Reference number - Use serial numbering [optionally, concatenate Project Name/Code with
2 Identification Date of Risk Identification Date of Risk Identification
3 Process Area / Phase / Functional A Category can be used in Validation sheet
Note: Use areas like - Domain,Technology, Integration, Delivery,
Disposal, Processes used (any new processes, procedures,
methods, etc), Products used (any new free-ware/open source, etc),
Contract Risks, Business (Budget/Costs , Schedule), Resource /
Infrasturcture, Performance Risks, Skills, Deployment and Support,
Environment
e.g. Phases of Software development - Design , Process Area of
BPO - Transition, Pilot, Execution, etc.
4 Process Requirement E.g. Design should meet the customer requirement - technology requirement
5 Mode of Failure Give only 2 or 3 words to state this. E.g. Non-identical Environment
[what may go wrong with the what may go wrong with the Requirement -E.g. Technology not met
6 Requirement]
Risk Description Give detailed description of the mode of failure, from perspective of affected party
[detailed description of the mode
of failure, from perspective of
affected party]
7 Impact Impact description Give detailed description of the impact
8 Impact On [what Parameter- For each Parameter like Schedule, Efforts (cost), Quality, etc. a separate line of Risk Analysi
9 Schedule
Impacted /Party
Effort (Cost) / Quality, etc.] List L0003 of dCORUM to be referred. Also available in Validation sheet here
10 Severity [S] Refer table below
11 [S] Range is even numbers - Validation based on the values in previous cell
12 Cause Cause of Mode of Failure The cause is to be documented which will lead to further analysis
13 Risk Source [Internal, Vendor, Customer]
[Internal, Vendor, Customer]
14 Occurrence Refer table below
[O]
[Probability of the occurrence of the
cause]
15 [O] Refer table below

16 Detection Detection Mechanism Computed field
17 [how to detect
Detection [D] this cause] Sort on RPN and one with highest score is the top most. Analyse the top 3.If there are more than
18 [how
[D] readily it can be detected] 1. Risk avoidance (very high so avoid the project / activity)
19 Risk Priority Number [RPN] = Severity * Probability * 2. Risk control
Computed field- mitigation / contingency
20 Risk Assessment [based on Risk Assessment Risk assessment based on Risk assessment matrix and organization threshol
Matrix]
21 Risk Ranking Need to Rank by the project / department
22 [Highest RPN. If more
Risk Treatment Riskthan 1 in same
handling range, then order Exploit
Strategy on Severity, then
– Taking Occurrence
advantage of theand then Detection]
situation (P)
N means Risk is negative
P means Risk is Positive Share – Sharing with other unit (P)
(opportunity Accept – acknowledge the risk and not take any action till it actually
occurs (P / N)
Avoid – eliminate the threat or protect the project from its impact (N)
Transfer – Shift the impact to a 3rd party (N)
Mitigate – Reduce the probability of risk or its impact (N)
23 Action Plan (Mitigation) Action to reduce the risk

24 Responsibility Responsible person to ensure completion of the action
25 Date Date by which action is to be completed
26 Monitoring and REVISED Severity [S] Choose the value
27 Review [Range
REVISED 1 to
[S]10, with 10 Choose the value
28 Revised Occurrence [O] Choose the value
29 REVISED [O] Choose the value
30 [Values inDetection
REVISED drop down [D]are based on Severity
Choose used for calculating RPN]
the value
31 highest
Detectiondetection
[D] is 2, least likely to detect
Chooseisthe
10 value
32 [Values
Revisedin drop down are based on Severity
RPN Revisedused
Scorefor calculating
RPN = SeverityRPN]
* Probability * Detection
33 Remarks = S*O*D
If Revised RPN >= Initial RPN, revisit Give
the risk.
the link to the Risk number and track as new line item
Using this risk reference, add another line of action tracking
Back to top Risk Source - Internal /External
Internal
Vendor
Customer
Back to top Impacted Party

Example
Source of risk Description
Customer Dependencies with the client for clarification of issues.
DL We do not have personnel with experience in web application development.
Customer Setting up of Test database on-site prior to UAT is client’s responsibility.
DL Delay in procuring Hard disk for HP 9000.
DL The communication with the customer is in Japanese Language. Moreover the documents are a
Vendor The vendor might not deliver the desired product
Customer Requirements are not defined clearly in the contract.
Back to top
BackTables
to top Severity Meaning
Rating Severity
1,2 Minimal impact
3,4,5 Moderate impact
6,7,8 Critical impact
9,10 Catastrophic impact
BackRisk
to topAnalysis • In all cases, irrespective of the final
RPN, all Severity scores greater than
8 has to be treated as a high priority
risk.
• In case of a tie between RPNs,
preference will go to the higher
severity, followed by Occurrence and
then detection
e.g: If the RPN score is low but the
severity may be high and therefore,
you need to prioritize it higher.
Risk_Assessme RPN
nt
Catastrophic >500
Critical 300 - 500
Marginal 100 - 299
Negligible <100
Step 1: Sort on RPN and analyse the top 3

Step 2: If there are more than 1 in the same RPN, then analyse on the following order
1 Severity
2 Occurrence
3 Detection
Risk Category based on Risk Score --> Severity --> Occur For values, refer tables above
Risk Assessment Matrix
RPN Severity Occurrence
1000 10 10
729 9 9
512 8 8
343 7 7
216 6 6
125 5 5
64 4 4
27 3 3
8 2 2
1 1 1
Pr
oje
ct
De
tail
s
lly, concatenate Project Name/Code with Serial number]
chnology requirement
rspective of affected party
ty, etc. a separate line of Risk Analysis is required

e in Validation sheet here
s in previous cell
. Analyse the top 3.If there are more than 1, then evaluate on the highest Severity, then Occurrence, then Detection
matrix and organization threshold used as validaion

cation development.
t’s responsibility.
anguage. Moreover the documents are also in Japanese.
Back to top
Occurrence Meaning probability
Description 1,2,3 Not very likely < 20%
No impact on reliability, safety, schedule, 4,5,6 Moderately / 20-50%

cost etc. somewhat likely
frequent
-Slight hiccups; 7,8 Highly frequent 50-80%

-Systems not impacted significantly;
-Some annoyance for Customer;
Loss of one or more primary functionalities, 9,10 Almost always > 80%
Significant erosion of Project Margin
-Product inoperative;
-Customer may pull out;
-Loss / Bleeding;
Detection
10
9
8
7
6
5
4
3
2
1
Risk Identification
Back to top
Detection Meaning Description
1,2,3 Easily Detectable Can be easily caught during review / test
4,5,6,7 Moderately Some iterations / multiple reviews/tests can

Detectable detect
8,9,10 Almost Undetectable Almost impossible to detect

Impact
Cause Detection
Risk Monitoring
Treatment and
Review
Remarks

Risks, Opportunities, Issues - Management and Analysis Form

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Risks, Opportunities, Issues - Management and Analysis Form

Uploaded by

Copyright:

Available Formats

Risks, Opportunities, Issues -Management and

Project Manager: Gopal Ranaj

Delivery Head: Gopal Ranjan

28-Feb-20 3.0 1. Added Risks of AK AD

26-Aug-20 4.0 New Risks updated VS MK

Note:Risks are discussed during SMR, which is typically on monthly basis.

the SMR ppt Risk status as well.

VFS24X7 VFS24X7_ RiskRegister Jitendra Patkar Gautam Makkar

The Conference Board TCB_CFD_Risk Amit Chauhan Sandeep Arora

Severity [S] [S] Occurrence [O] Detection [D]

1/2/1900 3 Created new table structure considering all

1 1 Impact has gone down, due to mitigation Minimal_i 1 Not_likely

1 Easily_Det 1 1 None Identified

1 Easily_Det 1 1 Client is Closed

Somewhat 2 Easily_Det 1 12 Impact has Not-

15 [O] Refer table below

23 Action Plan (Mitigation) Action to reduce the risk

Back to top Impacted Party

1,2 Minimal impact

3,4,5 Moderate impact

6,7,8 Critical impact

9,10 Catastrophic impact

Step 1: Sort on RPN and analyse the top 3

rspective of affected party

ty, etc. a separate line of Risk Analysis is required

matrix and organization threshold used as validaion

anguage. Moreover the documents are also in Japanese.

No impact on reliability, safety, schedule, 4,5,6 Moderately / 20-50%

-Slight hiccups; 7,8 Highly frequent 50-80%

4,5,6,7 Moderately Some iterations / multiple reviews/tests can

8,9,10 Almost Undetectable Almost impossible to detect

You might also like