Professional Documents
Culture Documents
This Template For Study Purpose Only Risk Plan For You're Working in Google Corp at APAC and Prepare To Improve The Voice Recognition Project
This Template For Study Purpose Only Risk Plan For You're Working in Google Corp at APAC and Prepare To Improve The Voice Recognition Project
This Template For Study Purpose Only Risk Plan For You're Working in Google Corp at APAC and Prepare To Improve The Voice Recognition Project
Risk Plan
For You’re working in Google Corp at APAC and prepare to improve the voice
recognition project.
Document Information
© Information
Document History
Document Approvals
Project Sponsor
Project Manager©
Quality Manager
(if applicable)
Procurement Manager
(if applicable)
Communications Manager
(if applicable)
A Risk Plan outlines the foreseeable project risks and provides a set of actions to be taken
to both prevent the risk from occurring and reduce the impact of the risk should it eventuate.
More specifically, the plan includes:
A Risk Plan should be documented early in the project, during the Planning phase. The plan
is undertaken prior to the Execution phase to ensure that any risks identified are addressed
during the Execution phase itself. Immediately after the plan has been documented, the Risk
Management Process will be engaged to monitor and control the likelihood and impact of
risks on the project.
The Risk Management Process is terminated only when the Execution phase of the project
is completed (i.e. just prior to Project Closure). ©
This document provides a guide on the topics usually included in a Risk Plan. Sections may
be added, removed or redefined at your leisure to meet your particular business
circumstance. Example tables, diagrams and charts have been added (where suitable) to
provide further guidance on how to complete each relevant section.
The first step in creating a Risk Plan is to identify the likely risks which may affect the project.
A series of risk categories is identified and for each category a suite of potential risks is
listed. This may take place during a ‘Risk Planning’ workshop, involving each of the key
project stakeholders who are involved in / affected by the project. This may include the
project sponsor, manager, team, suppliers, and in some cases, even the customer. Each of
the risks identified is described in detail and documented within the Risk Plan.
1.1 Definition
Provide a formal definition for the term ‘risk’ for this project. For example:
“A risk is defined as any event which is likely to adversely affect the ability of the project to
achieve the defined objectives”.
Risk identification is the process of continuously and systematically identifying the risks that
may occur in the business activities of the enterprise.
1.2 Classify
Risks can be classified into 5 categories as follows:
Delay or failure to deliver on time: This is the risk of a complete and possibly permanent
failure of the goods or services, or the risk of delay in the delivery of the goods or the
provision of a service. specific.
Brand Damage: These are risks that can damage a business's brand due to conflicts with
business principles, customer and stakeholder expectations.
Loss of competitive advantage: The risks of competitive advantage are often not well
defined, including intellectual property theft, counterfeiting, and gray market goods.
Price and cost risk: The risk that input costs are higher than anticipated or planned (with or
without a contract).
Quality Risks: Risks associated with poor quality, poor product or service quality, and
potential defects.
1.3 Categories
Types of possible risks for this project. Each risk category is a particular aspect of the project
which is likely to experience a risk during the lifecycle of the project. Examples of typical
risk categories include:
People
Technology
Business process
Reputational
Technical
Applicability
Design
Data security
Financial
Health
Sound source is not guaranteed
Connection
Late scheduling
Lack of physical facilities
1.4 Risks
Identify the likely risks for each category provided above by completing the following table.
Each risk identified should be allocated a unique identifier (id) number.
1 Risk Identification
Category Description Id
People · The risk that good employees will leave the project midway 1.1
because of the difference in income
1.2
· The user may not want to use or opt out of the speech
recognition system. 1.3
· The user may not know how to use the voice recognition
system. 1.4
· Lack of technically trained manpower, The staff assigned to 1.5
the project do not have the right skills
· Multi-regional voices are hard to recognize 1.6
· Leadership may not support voice recognition systems
2.4
Business process · Business processes may change during speech recognition 3.1
project implementation
3.2
· Project issues not resolved within an appropriate amount of
time 3.3
· The same problems kept reappearing throughout the project
· Unresolved issues become new risks to the project 3.4
· Scope and requirements may increase, resulting in 3.5
underfunding.
· The system may not meet the user's needs or expectations 3.6
· The criteria for accepting project deliverables are not clearly
3.7
defined
· There are special business requirements that the project 3.8
cannot meet.
Sound source is · Poor sound quality can affect speech recognition 7.1
not guaranteed · May contain obscene sounds
7.2
Late scheduling · Jobs that are not scheduled on time leading to unscheduled 9.1
work
2 Risk Quantification
1.3 40 80 60 Medium
1.6 20 80 50 Medium
2.1 40 60 50 Medium
2.2 60 60 60 Medium
2.3 60 60 60 Medium
2.4 60 60 60 Medium
3.1 40 80 50 Medium
3.3 60 80 70 High
3.4 80 80 80 High
3.6 80 80 80 High
3.7 60 80 70 High
3.8 60 80 70 High
4.1 20 60 40 Low
4.2 40 80 60 Medium
4.3 20 40 30 Low
4.4 20 80 50 Medium
5.1 20 80 50 Medium
5.2 40 60 50 Medium
6.1 20 80 50 Medium
6.2 40 20 30 Low
7.2 20 80 50 Medium
8.1 40 60 50 Medium
8.2 20 40 30 Low
10.1 40 60 50 Medium
Survey of
voice
problems
Very 3.5 Any changes Project xx/yy/ Call for Project xx/yy/
High in scope will Manager zz investment Manager zz
go through the capital from
change sponsors
approval
process and Cost savings
must be Simplify
aligned with requirements
previously
approved Please add
funding. funds for the
project
Set priorities
for business
and technical
requirements
into the
decision-
making
process.
Before starting
the project,
there must be
a contract with
the customer
with full terms
Very 11. Apply HR, Project xx/yy/ Perform regular Project xx/yy/
High 2 corrective monitoring Manager,
measures Manager zz HR zz
right from the
time they arise
to avoid
common risks
for the project
Rearrange the
work
accordingly, to
ensure the work
is not stalled
High 1.4 Spend a part Project xx/yy/ Hire personnel Project xx/yy/
of the cost to Manager zz from HR service Manager zz
train providers
personnel
right from the You can choose
start to hire
employees to
Set aside a work from home
buffer for
additional Encourage
personnel employees to
work overtime
Create a to earn extra
separate income and
training finish projects
program for early
the project
Organize
cross-training
sessions
between
skilled
members and
newbies
Plan extended
work and
assign tasks
to yourself and
your
subordinates
Reduce
pressure at
work
Increased joy
at work - Can
plan a lot for
the future and
solve long-
term problems
Enhance
creativity
Mobilize users
to test and test
High 3.8 Make some Quality xx/yy/ Negotiate and Project xx/yy/
hypothetical Manager zz explain to Manager zz
cases to give customers
customers about business
reference, problems that
then follow the cannot be
available completed
samples, try to
convince
customers.
Develop test
software
samples,
request
detailed
description
and send to
customers
High 9.1 Make a clear Project xx/yy/ Choose the Project xx/yy/
schedule to Manager zz most optimal Manager zz
ensure the schedule for
completion of work
the project on
time
Compilation
and
compilation of
training
materials.
Regularly
monitor and
monitor the
understanding
and
acceptance of
the new
system
(through
support
applications,
conduct
surveys), and
adjust training
based on the
results of
these
assessments.
Clearly
communicate
the new
system to
employees,
emphasizing
that
employees will
participate in
the pilot
implementatio
n to ensure
the new
system meets
their
requirements
Medium 2.1 Buyers should Project xx/yy/ Replace old Project xx/yy/
ask for the Manager zz version Manager zz
latest version
or all-inclusive
solution
Medium 2.2 Prepare, test Quality xx/yy/ Learn from Quality xx/yy/
and follow the Manager zz experience and Manager zz
detailed test complete the
plan, identify project
the important
parts and Optimize
essential performance
business that
must be
tested.
Accept the
fact that the
pilot rollout
won't be
perfect and
figure out what
needs to be
fixed before
large-scale
rollout and
what needs to
be adjusted
afterwards.
Medium 2.3 Indicate clear Quality xx/yy/ Thanks to the Quality xx/yy/
and specific Manager zz intervention of Manager zz
requirements the disaster
for disaster prevention
prevention department
system
testing.
Medium 2.4 Start early, Project xx/yy/ Negotiate with Project xx/yy/
specify Manager zz partners to Manager zz
connection shorten time
standards
Work
immediately
with external
systems to
unify
standards
Medium 3.1 The project Project xx/yy/ Build the Project xx/yy/
manager must Manager zz necessary Manager zz
be involved in changes into
the policy the system
development through an
process to approved
ensure that change
the impact of management
any significant process
changes is
clearly
understood.
Based on
each specific
file, an
appropriate
treatment and
recall plan will
be proposed.
Medium 5.1 Ensure that Project xx/yy/ Looking for Project xx/yy/
funding is Sponsor zz backup Manager zz
maintained sponsors
evenly.
Low 6.2 Ensure social Project xx/yy/ Let employees Project xx/yy/
distancing to Manager zz work from home Manager zz
prevent to prevent
infectious disease
diseases
Low 8.2 Make sure the Project xx/yy/ Add servers to Project xx/yy/
server works Manager zz load balance Manager zz
well, can bear overloaded
the load of servers
many people
at the same
time
4 Risk Process
What is a Risk Process?
A Risk Process, or Risk Management Process, describes the steps you need to take to
identify, monitor and control risk. Within the Risk Process, a risk is defined as any future
event that may prevent you to meet your team goals. A Risk Process allows you to identify
each risk, quantify the impact and take action now to prevent it from occurring and reduce
the impact should it eventuate.
4.1 Purpose
Risk mitigation is the prudent response to the reality that life is uncertain and sometimes bad
things happen to good organizations. The alternative to risk management is going through
life with your fingers crossed, hoping that bad luck only ever happens to other people.
Risk management introduces rationality into the irrational world of bad luck. It’s a way of
evaluating potential negative events and their likely impacts, then taking steps to protect
ourselves against those events that would cause the severest damage if they occurred, or
that are more likely to occur.
Risk mitigation and management can help us understand where we should invest to protect
ourselves, and also where we don’t need to do so (if the risk is too small).
The Risk Management Process
The risk management process is the set of steps you should be taking routinely, habitually,
to assess and mitigate the hazards present in your organization and lines of business.
This should become part of your organization’s culture. It should become as habitual for your
company as it is for a person to look both ways before they cross the street.
It needs to be a cycle because it can take several iterations to get where you need to be and
also because things change over time. Risk management and mitigation is not a project, but
an ongoing aspect of resiliency.
Most organizations should assess their risks at least once a year, depending on the rate of
change in their organization, field, and environment.
4.2 Procedures
The 6 Steps of the Risk Management Process
· Along with the Sponsor,Stakeholders and Business Analyst, helps create the Project
Charter during the Identification phase of the project
· Develops the Project Plan with the team and manages the team's performance of
project tasks
· Secures acceptance and approval of deliverables from the Project Sponsor and
Stakeholders
· Responsible for communication, including status reporting, risk management,
escalation of issues that cannot be resolved in the team
· Responsible for ongoing status reporting, including project health and tracking the
financials of the project
· Responsible for overall management of the vendor relationships
· Responsible for closing the project in a controlled manner, and obtaining customer
sign-off for the project closure document to formally close the project
Project Sponsor Roles and responsibilities
Usually a senior member from the business area in which the project is requested, with a
deep understanding of that area's operations and strategic aims. The Project Sponsor has
the authority to approve budgets and resource requests within their business area.
· Assist the project manager in planning work packages, creating schedules and cost
estimates
· Responsible for completing assigned work on the project during the execute phase.
This may include design, build, testing against requirements, operational assessment
and implementation activities
· Identify risks and opportunities throughout the project, and may help in formulating
the appropriate responses to these
· Actively participate in project team meetings and promptly communicate issues to the
project manager
4.4 Register
4.5 Templates
Risk ID
Risk Description
Likelihood
Relative Impact
(Cost/Schedule/Scope/Quality)
Mitigation Strategy/ Action
Relative Cost
Probability of Successful
Mitigation
Status/ Comments
5. Appendix
https://en.wikipedia.org/wiki/Risk_management_plan
http://www.phe.gov/about/amcg/contracts/documents/risk-management.pdf
https://plan.io/blog/risk-management/
http://ptgmedia.pearsoncmg.com/images/9780789750105/samplepages/0789750104.pdf