You are on page 1of 5

Table of Contents

3.0 Introduction…………………………………………………………1
3.1 Risk Mitigation for Risk m…………….……………….…1
3.1.1 Employee Risk……………………………..………..1
3.1.2 Technological Risk…………………………………..1
3.1.3 Strategic Risk………………………………………...1
3.1.4 Financial Risk………………………………………..2
3.1.5 Time Risk……………………………………………..2
3.2 Risk Monitoring for Risk m……………………………….2
3.2.1 Employee Risk……………………………………….2
3.2.2 Technological Risk……………………….………….2
3.2.3 Strategic Risk…………………………….…………..3
3.2.4 Financial Risk………………………………………..3
3.2.5 Time Risk……………………………………………..3
3.3 Risk Management for Risk m…………………………….3
3.3.1 Employee Risk……………………………………….3
3.3.2 Technological Risk…………………………………..3
3.3.3 Strategic Risk………………………………………...4
3.3.4 Financial Risk………………………………………..4
3.3.5 Time Risk……………………………………………..4
4.0 Special Conditions…………………………………………………4









WMITS Software Configuration Management Plan Page 1

3.0 Introduction
Short introduction.
3.1 Risk Mitigation for Risk m
3.1.1 Employee Risk
If the member of the team fails to participate
during the stage of creating the propose system, It
is possible that the propose system will fail to meet
the goal of the proponents. To avoid this problem,
as mitigation phase, each member must have
proper communication and understanding in their
obligations in the team.
3.1.2 Technological Risk
If the group members are not prepared in
unexpected electric interruption on the process of
making the system they are going to propose,
there is a possibility tolose the files that
proponents are creating and miss the deadlines of
their goals. To avoid this problem,as mitigation
phase, the proponents must always save their files
each and every time they are encoding. And they
must have alternative laptops or computers to use
and back up their files.
3.1.3 Strategic Risk
If the necessary tools are not provided to
the team, their work will lack uniqueness and
quality. As mitigation phase, the proponents will
make sure that they always research on what was
new or latest changes that can easily adapt to their
system to produce a unique one. And they make
sure to secure their system.

WMITS Software Configuration Management Plan Page 2

3.1.4 Financial Risk
If the member of the team fails to meet their
budget in creating their propose system, there is a
possibility not to provide the necessary tools or
needs to complete the creation of the system. As
mitigation phase, the proponents must have their
contribution to sustain the financial needs while
creating and finishing the system.
3.1.5 Time Risk
If the member of the team does not follow
and meet their assign time schedules, this will
cause them to delay their creation of the system
and this will be the reason why the proponents will
not finish their goals on time. As mitigation phase,
the proponents must plan and budget their time
wisely to accomplish certain goals on time, and the
tasks and schedules.
3.2 Risk Monitoring for Risk m
3.2.1 Employee Risk
Managing and monitoring this risk will
include helping other co-members which having
difficulties in their tasks by giving some ideas and
techniqueson them. This is giving and taking ideas
from each members of the team when they have a
little time to spend throwing back ideas.
3.2.2 Technological Risk
In monitoring,the proponentswillkeep an eye
on new technology and how to make sure that they
can have their back up files when any electric
interruptions will occur.

WMITS Software Configuration Management Plan Page 3

3.2.3 Strategic Risk
To monitor this risk, the proponents will
keep their eye to the new system and tools they
can use and their effectiveness. This can give
them new ideas and will help them develop their
system to a unique one.
3.2.4 Financial Risk
To monitor the financial risk the proponents
will keep their eye on their financial budgetand the
effectiveness on how they use it. This will help
them sustain the needs on creating their propose
system.
3.2.5 Time Risk
To monitor this risk, the proponents will
keep an eye on their time plan and its
effectiveness. This will help them budget their time
wisely.
3.3 Risk Management for Risk m
3.3.1 Employee Risk
If it turn out that the team is having trouble
on performing their task, the other co-member will
take some time off to teach the particular member
on the basics they need to know to fulfil their tasks.
3.3.2 Technological Risk
The proponents will try to spot new
techniques and look out for the major shifts of the
technology and how it will affects the system that
they are working on. If there is a need to change in
the technology they are using, they will discuss it
on the group to know if they will all agree on the
changes they made on their existing system.
WMITS Software Configuration Management Plan Page 4

3.3.3 Strategic Risk
If it happens that the system strategy is not
effective, the proponents will re-plan their strategy
and choose the one that is most appropriate in
system and appropriate tools they can use to
make it effective.
3.3.4 Financial Risk
If it happens that the budget of the
proponents is not effective to achieve their goal,
the proponents will plan it againto budget
iteffectively. This will help them sustain the needs
of their propose system.

3.3.5 Time Risk
If it turn out that the plan schedule does not
meet the expected duration, the proponents will
have to draw another plan on how to meet their
goals effectively.
4.0 Special Conditions