Risk Management Matrix (Risk Register)

Project Devops
Project Manager Sumit Ankush
Neha Kadam
Ansh Poojari

ID Risk Probability Impact Refinement Mitigation / Trigger / Status Owner Date Date to
Description / Content Monitoring Contingency Entered review
plan
<# <Descriptio <risk <low / <associate <enter the <if risk <running <who <Date at <include
> n of risk probability medium information mitigation / mitigation fails status the monitors which the date
identified> > / high> for risk monitoring steps then plan for provides a the risk> risk is status
refinement taken> handling the history of identified entry
> risk> what is > was
being done made>
for the risk
and
changes in
the risk.>
1 Code 20% high The further Checking if the Having backup Closed Ansh
repository process of repository has copies of code Poojari
doesn’t debugging enough space and with the the
accept the and is accepting files developer in
code from integration with all extensions case of such a
developers. would not of code. situation.
take place if Clearing
the repository unwanted
doesn’t code files from
contain the the repository
code. time to time
and
maintaining its
state.
2 Error in 40% medium If errors in Taking regular Having a Open Sumit
debugging code are not checks of the prototype Ankush
detected, it debuggers and which has
will cause an updating them been already
issue in the time-to-time. created to
final product compare with
which is to be the final
delivered. outcome.
This impacts Reworking on
the output. the things
which don’t
come out to be
as expected
from the client.
3 Error in 55% high Failure in Updating Pausing the Open Neha
Code integration versioning tools on deployment Kadam
Integration leads to regular basis and for a while
incomplete trying to until the
modules accommodate unintegrated
being changes in modules have
deployed. minimum files at been
This would the developer side. integrated.
affect the
final product
 as well as the
flow of
project.
4 Bugs are not 45% medium Wrong Adding correct Readdressing Open Neha
being sent addressing of paths in the the bugs. Kadam
to the debugging debugging Changing the
respective process can process. Updating addressing
developers. affect the them with change pipeline of
work flow of in assignment of Sonarcloud.
respective the tasks.
developer as
they will have
to deal with
the bugs out
of the module
assigned to
them
5 Deployment 66% high The cost When working Making Closed Neha
crash associated on the product multiple Kadam
with an or backup copies
deployment documentation, of the
crash the members software in
resulting in should always be development
a loss of aware of the and all
data is stability of the documentatio
crucial. The computing n associated
main purpose environment with it, in
of the system they’re working multiple
won’t be in. Any changes locations. So
achieved with in the stability of that, if
this. Local the environment deployment
system crash should be crashes, then
can also lead recognized, data will not
to recorded and be lost.
deployment proper
crash countermeasure
s should be
prepared in
advance.