Example Risk RegisterExample Risk Register.xlsx WBS 1 20

Example Risk Register
Example Risk Register.xlsx | WBS 1 2014-04-29, 17:19
WBS_ID Task Task Level Risk
Risk Category
(Type)
Risk
Probability
Risk
Consequenc
es (Impact)
Initial Risk
Score
(Probabil. *
Impact)
Risk
Handling
Category Risk Handling/Control Plan
Risk
Owner
(Risk
Manager)

0
SERVER AND SYSTEM UPGRADE
PROJECT
0 Project funding not obtained
External,
Financial
25% $500,000 $125,000 Accept Cancel the project PM
0
PROJECT
0 Project funds cut
External,
Financial
50% $250,000 $125,000 Mitigate
Re-plan the project with reduced
scope
PM
0
PROJECT
0 Lack of client or sponsor support External 33% $250,000
$82,500 Accept
If it happens, it happens. Deal
with it.
PM
:

:
1 INITIATE PROJECT (phase 1)
1.1 Analyze requirements
1.1.1
Contact customer - Start project
initiation
3
Customer non-responsive or schedule
conflicts
External 10% $10,000 $1,000 Mitigate
Keep trying to arrange acceptable
schedule.
PM
1.1.2 Manage project initiation
1.1.3 Engage customer 3
conflicts
schedule.
PM
1.1.3.1 Conduct initial requirements analysis 4 Requirements
scope exceeds budget
External,
Financial

10% $50,000 $5,000 Mitigate
Re-plan project for reduced
scope.
PM
1.1.3.2 Review concept of operations (if any)
1.1.4
Establish integrated cost estimating
team
3
Participants non-responsive or
schedule conflicts or unable to obtain
expertise
schedule.
PM
1.1.5 Conduct joint analysis (a'la JAD) 3
schedule conflicts
schedule.
PM
1.1.5.1 Generate cost estimate 4 Cost estimate exceeds project
budget Financial 10% $50,000 $5,000 Mitigate
Re-plan project for reduced

scope.
PM
:
:
4.3.2 Develop system
4.3.2.1 Precure servers 4 Servers delayed in shipment External
10% $10,000 $1,000 Transfer Insure the shipment
Chief
engineer
4.3.2.2 Procure/build network 4 Technical difficulties building
network Technical 10% $25,000 $2,500 Mitigate
Bring in technical experts to
assist; delay project if necessary
Chief
engineer
4.3.2.3 Procure/build databases 4 Technical difficulties buildind
databse Technical 10% $10,000 $1,000 Mitigate
Bring in technical experts to
assist; delay project if necessary
DBA
:
:
Example Risk Register (Partial)

0
PROJECT
0 Project funding not obtained
0
PROJECT
0 Project funds cut
0
PROJECT
0 Lack of client or sponsor support
:
:
1 INITIATE PROJECT (phase 1)
1.1 Analyze requirements
1.1.1
Contact customer - Start project
initiation
3

conflicts
1.1.2 Manage project initiation
1.1.3 Engage customer 3
conflicts
1.1.3.1 Conduct initial requirements analysis 4 Requirements
scope exceeds budget
1.1.3.2 Review concept of operations (if any)
1.1.4
Establish integrated cost estimating
team
3
schedule conflicts or unable to obtain
expertise
1.1.5 Conduct joint analysis (a'la JAD) 3
schedule conflicts
1.1.5.1 Generate cost estimate 4 Cost estimate exceeds project
budget
:
:
4.3.2 Develop system
4.3.2.1 Precure servers 4 Servers delayed in shipment

4.3.2.2 Procure/build network 4 Technical difficulties building
network
4.3.2.3 Procure/build databases 4 Technical difficulties buildind
databse
:
:
Est. Cost of
Mitigation
Remaining
Probability
after
Mitigation
Remaining
Consequences
(Impact) after
Handling
Final Risk
Score
Current Risk
Status Notes and discussion
13% $250,000 $31,250
$31,250 25% $125,000 $31,250

17% $125,000 $20,625
$250 5% $5,000 $250
$375 8% $5,000 $375
$1,250 5% $25,000 $1,250
$3,125 13% $25,000 $3,125
$1,250 25% $5,000 $1,250
$1,250 5% $25,000 $1,250
$100 5% $5,000 $250
$625 5% $12,500 $625
$250 5% $5,000 $250
Risk Category
(Type)
Risk
Probability
Risk
Consequenc

es (Impact)
Initial Risk
Score
(Probabil. *
Impact)
Risk
Handling
Risk
Owner
(Risk
Manager)
4.4.2.7
Prepare developomental testing
report
4 Report preparation delayed PM 5% $5,000 $250 Mitigate
Bring in additional tech writers to
assist
Tech
writing
:
:
5.1.6
Obtain initial operational testing

approval (user acceptance)
3 Client does not accept system External 5% $500,000 $25,000
Mitigate or
Accept
Depending on severity, either
send back to developers for
correction or cancel project
Chief
engineer
or PM
:
:
5.2 Software Development 2 Development schedule delays 25%
$41,667 $10,417 Mitigate Add additional programmers
Chief
engineer
or PM
5.2 Software Development 2 Development cost overrun 25%
$50,000 $12,500 Mitigate Renegotiate scope
Chief
engineer
or PM
5.2 Software Development 2
Quality issues due to inexperienced
programmers

12% $30,000 $3,600 Mitigate :
Chief
engineer
Unclear or incomplete requirements
result in need to scrap and re-start
devleopment of selected modules
10% $50,000 $5,000 Accept etc :
Incorrect requirements result in need
to scrap and re-start devleopment of
selected modules
10% $150,000 $15,000 Accept : :
:
:
6
System Initiation, Implementation &
Fielding
6.1 Initital Training 2
Scheduling issues with customer
personnel
40% $30,000 $12,000 Accept
6.2 System Integration, Site Test/Accept 2
Customer does not accept product,
requires rework

10% $500,000 $50,000 Accept
:
:
… etc, etc …
Total at risk:
Likely loss
due to risk:
4.4.2.7
Prepare developomental testing
report
4 Report preparation delayed
:
:
5.1.6
Obtain initial operational testing

approval (user acceptance)
3 Client does not accept system
:
:
5.2 Software Development 2 Development schedule delays
5.2 Software Development 2 Development cost overrun
Quality issues due to inexperienced
programmers
Unclear or incomplete requirements
result in need to scrap and re-start
devleopment of selected modules
Incorrect requirements result in need
to scrap and re-start devleopment of
selected modules
:
:
6
System Initiation, Implementation &
Fielding
6.1 Initital Training 2
Scheduling issues with customer
personnel

6.2 System Integration, Site Test/Accept 2
Customer does not accept product,
requires rework
:
:
… etc, etc …
Est. Cost of
Mitigation
Remaining
Probability
after
Mitigation
Remaining
Consequences
(Impact) after
Handling
Final Risk
Score
Current Risk
$63 3% $2,500 $63
$6,250 3% $250,000 $6,250
$2,604 13% $20,833

$3,125 13% $25,000
$900 6% $15,000
5% $25,000
5% $75,000
20% $15,000
5% $250,000
Total cost of
mitigation:
Likely
remaining
loss after
mitigation: Savings due to risk management:
Risk Category
(Type)
Risk
Probability
Risk

Consequenc
es (Impact)
Initial Risk
Score
(Probabil. *
Impact)
Risk
Handling
Risk
Owner
(Risk
Manager)
$1,730,000 $392,250
23%
of cost at risk

Est. Cost of
Mitigation
Remaining
Probability
after
Mitigation
Remaining
Consequences
(Impact) after
Handling
Final Risk
Score
Current Risk
$46,038 $865,000 $98,063 $248,150
3% 50% 6% 14%
of cost at risk of cost at risk of cost at risk
of cost at risk
WBS
Project Charter
Mamma’s Bakery and Sandwich Shoppe - Project Plan to Install

IT System
IFSM 438: Project Management
ITP-1 Project Charter
A.
General Information
Project Title:
Mamma’s Bakery and Sandwich Shoppe
Install IT Project
Brief Project Description:
Prepared By:
Date:
March 2, 2021
Version:
1.0
Customer and Stakeholders:
Mamma Mia – As the business owner, she has the largest
interest and influence over how the IT system is designed and
implemented.
Mamma Mia's employees – The employees will directly be
interacting with and using the new IT system. Their job
performance can be influenced positively or negatively by the
implemented systems. They will be very interested in a system
that will meet their needs.
Customers – The IT system will influence the customers'
experience. The efficiency of getting goods to customers can be
affected.
Suppliers – The IT system can make ordering inventory timely
and more cost-effective. Suppliers and Mamma will be
interested in integration between their systems and the IT

system at Mamma's.
Health Department/Government Regulators – The IT system will
have to meet all regulators standards. Therefore, regulars will
influence the IT system's design and implementation.
B. Project Objective:
Explain the specific objectives of the project. For example:
What value does this project add to the organization? How does
this project align with the strategic priorities of the
organization? What problem will this project solve? What
results are expected? What are the deliverables? What benefits
will be realized? What problems will be resolved?
The project will design and implement a modern IT
infrastructure at Mamma Mia bakery. The bakery is expanding
its operations and the IT systems it will allow it to expand and
scale with demand. . Resource planning, supply chain/inventory
management, transaction ease, employee efficiency, and
customer experience should all see improvements.
C. Assumptions
List and describe the assumptions made in the decision to
charter this project. Please note that all assumptions must be
validated to ensure that the project stays on schedule and on
budget.
Mamma Mia’s is a small business looking to grow into new
areas of food service, and to better leverage technology for
expansion. Currently the business is run using antiquated,
offline systems with little integration that do not scale well.
Eight Week Warriors LLC (EWW) will be providing these
services, starting with the following assumptions.
Assumption
Explanation of Assumption

1.Contiguous Space
The new storefront space is next to the existing bakery
2.Blank Slate
There is no existing IT infrastructure
3.Existing relationships
The customer has existing relationships with food service
vendors and the health department
4.Limited IT Experience
The customer has no experience with IT systems, and will
require training and mentorship
5. All systems will need to be procured
EWW will be responsible for procuring and installing any and
all hardware and software, from cabling and computing
resources to POS registers and cloud-based systems
D. Project Scope
Describe the scope of the project. The project scope establishes
the boundaries of the project. It identifies the limits of the
project and defines the deliverables.
This project is for the Mamma’s bakery shop to install an IT
system and modernize their current business process. Currently,
the bakery shop is operating by telephone and hand paper
documents. There is no IT system, IT staff, networking, LAN,
productivity software/applications or Internet installed. This
project scope developed by the Eight Week Warriors, will
implement an IT system installed for point-of-sale, inventory
and bookkeeping purposes. This project will incorporate the use
of technology in its operation. The Eight Week Warriors team
will plan, design, train the staff and provide project deliverable
services to help Mamma’s bakery shop become more efficient.
Project Deliverable
· Hire and train staff based on the new business processes.
· Install a business internet connection using Wi-Fi and/or

network equipment.
· The SaaS Business-to-Business will be implemented for the
bakery business model
A website would be developed for customers to be able to view
the different products offered by the business and pl ace advance
orders.
· Enterprise Resource Planning will be developed for the bakery
so that information would be about the customers, suppliers,
and employees would be easily managed by the IT system.
· The IT system will connect to her suppliers, the heal th
department for food services, and other business relationships
as one of their major marketing campaign strategies.
· The IT system will be user friendly and be able to process
debit/credit transactions.
· The IT staff will create training materials.
List any requirements that are specifically excluded from the
scope.
· The bakery management system will ensure all the systems are
integrated under one platform and to help centralize the data.
E. Project Milestones
What is the estimated schedule for the project (start to finish?)
List the major milestones and deliverables of the project.
.
Milestones
Deliverables
Date
Initiation Phase
· Identify project members and roles
· Gather requirements
· Meet and speak with stakeholders/clients about business goals
· Develop a clear scope of work/time frame

2/17 – 3/2
Planning Phase
· Develop a detailed schedule with milestones and deliverables
· Develop a detailed scope of work including budget for all
resources and materials
· Assign tasks to members
· Research ISPs in the area and compatible hardware and
software that fulfill requirements
· Research and determine the network and system configurations
that fulfill requirements
3/3 – 3/16
Execution Phase
· Set up network infrastructure
· Image and build IT systems and servers
· Build an IT inventory system
· Develop a website
· Build an IT finance system
· Ensure IT security
· Test all systems with sample data
· Revise, improve, or fix any found issues
3/17 – 3/30
Closeout Phase
· Perform training for client staff
· Ensure all requirements have been met and client is satisfied
3/31 – 4/6
F. Impact Statement

.
This project will be assessed to determine the impact it will
have on current business processes, current operations,
technology and all stakeholders (Hayes, 2000). As a small
business the following impacts have been identified.
1. Implementing an IT system to accommodate business
expansion will give Mamma Mia a competitive advantage in the
bakery and café market.
2. Implementing an IT system will streamline business
processes and vendor relationships.
a. Can result in a costs reduction over time.
b. Can speed up productivity.
3. Implementing an IT system will allow give data efficiencies.
a. Mamma Mia will have the ability to track peak customer
sales.
i. Identify opportunities.
b. Steam line inventory management, process improvement,
employee management.
4. Identifying key stakeholders and continuous communication
is essential. This will need to remain throughout the life of the
project.
G. Roles and Responsibilities
Describe the roles and responsibilities of project team members
followed by the names and contact information for those filling
the roles. The table below gives some generic descriptions.
Modify, overwrite, and add to these examples to accurately
describe the roles and responsibilities for this project.
Sponsor: Provides overall direction on the project.
Responsibilities include: approve the project charter and plan;
secure resources for the project; confirm the project’s goals and
objectives; keep abreast of major project activities; make

decisions on escalated issues; and assist in the resolution of
roadblocks.
Name
Email / Phone
Mamma Mia
[email protected]
Project Manager/Assistant Project Manager: Leads in the
planning and development of the project; manages the project to
scope. Responsibilities include: develop the project plan;
identify project deliverables; identify risks and develop risk
management plan; direct the project resources (team members);
scope control and change management; oversee quality
assurance of the project management process; maintain all
documentation including the project plan; report and forecast
project status; resolve conflicts within the project or between
cross-functional teams; ensure that the project’s product meets
the business objectives; and communicate project status to
stakeholders.
Name
Email / Phone
Deanna Best
[email protected]
Ahmed Abdulhadi
[email protected]
Team Member: Works toward the deliverables of the project.
Responsibilities include: understand the work to be completed;
complete research, data gathering, analysis, and documentation
as outlined in the project plan; inform the project manager of
issues, scope changes, and risk and quality concerns;
proactively communicate status; and manage expectations.
Name
Email / Phone
Julicel Crisostomo
[email protected]

Mireille Batubenge
[email protected]
Tasian Berryman
[email protected]
Tupper Cole
[email protected]
Customer: The person or department requesting the deliverable.
Responsibilities include: partner with the sponsor or project
manager to create the Project Charter; partner with the project
manager to manage the project including the timeline, work
plan, testing, resources, training, and documentation of
procedures; work with the project team to identify the technical
approach to be used and the deliverables to be furnished at the
completion of the project; provide a clear definition of the
business objective; sign-off on project deliverables; take
ownership of the developed process and software.
Name
Email / Phone
Mamma Mia
[email protected]
Subject Matter Expert: Provides expertise on a specific subject.
Responsibilities include: maintain up-to-date experience and
knowledge on the subject matter; and provide advice on what is
critical to the performance of a project task and what is nice-to-
know.
Name
Email / Phone
Professor Samuel Magambo
[email protected]
H. Resources
Identify the initial funding, personnel, and other resources

committed to this project by the project sponsor.
Resource
Constraints
Project Budget
$
I. Project Risks
Identify the high-level project risks and the strategies to
mitigate or avoid them.
Risk
Mitigation Strategy
J. Success Measurements
What are the high level benefits of this project?
Identify metric and target you are trying to achieve as a result
of this project. For example, overall cost savings of $50K or

reduce processing time by 25 percent.
K. Signatures
The signatures of the people below document agreement and
approval of the formal Project Charter. The project manager is
empowered by this charter to proceed with the project as
outlined in the charter. This charter will be
Customer:
Name
Signature
Date
Project Sponsors:

Name
Signature
Date
Project Manager:
Name
Signature
Date
References
Hayes, D. S. (2000). Evaluation and application of a project
charter template to improve the project planning process.
Project Management Journal,31(1), 14-23.
Project_Charter March 2021
Page 8 of 8
Case Scenario – Mamma’s Bakery and Sandwich Shoppe
Your team has been asked to prepare a project plan to install an
IT system in a local bakery.

Mamma Mia has been the primary baker and bakery owner since
its opening 15 years ago. The bakery is one of a dozen shops in
a strip mall in an up-and-coming part of town. The bakery is a
walk-up-and-order configuration with no seating space. Because
the bakery has become more successful over the years,
Mamma Mia has decided that the time is right to expand the
bakery into the next store, which is now vacant, and she has
signed a contract for the two stores to be connected and
remodeled.
· This space will more than double the size of the current
bakery. With this added-on/extra space,
Mamma Mia would like to offer her customers sandwiches and
bakery items, as well as café-type seating.
At the moment, the bakery employs
· 1 other baker and
· 2 persons who wait on the customers at the counter.
· All paperwork, bookkeeping, ordering supplies, hiring and
firing, and keeping track of inventory is done by Mamma.
When the expansion construction is complete,
Mamma Mia anticipates hiring
· 4 additional people full time –
· 2 food-service certified sandwich makers,
· 1 more baker, and
· 1 more counter server. She also intends to hire
· 1 person to track inventory and order supplies, and
· 1 person to manage the bookkeeping, bill paying, and finance
parts of the business.
Because the bakery is now a small operation, all business is
· done by telephone and with paper documents.
· There is one cash register and
· all bakery goods are purchased with cash or check.
To coincide with the construction/expansion effort, Mamma
would like to have an IT system installed
· for point-of-sale,

· inventory,
· bookkeeping, purposes.
Mamma would like the system to “connect”
· to her suppliers,
· the health department for food services, and
· other business relationships.
She would also like a website so that she has an Internet
presence and
· so her customers can make advance orders for pick-up.
· Related to that, she would like the system to be able to
process debit and credit cards.
Mamma Mia has identified $100,000 to provide an IT system
that will be
· modern,
· easy to use/employee and
· customer friendly, and
· will make her bakery and sandwich shop more efficient.
The cost estimate is just that – an estimate.
· Mamma has very little experience working with computers and
IT systems.
· She feels a bit “old fashioned” but she is willing to learn and
wants to be sure that her employees learn, too, how to work
with the IT system.
Mamma is your point of contact and the person you will be
working with as you “fill-in” and finalize the requirements for
the IT system, and then move to the design and implementation
of the IT system.
This means you will have a need to define and explain terms as
you work with her.
As you begin to plan the ITP project, keep in mind that until
now the client
· has had little or no IT system and
· has had no IT staff. In addition,
· there is no networking, LAN, or Internet installed, and
· no productivity software or other applications.

You may assume that Internet connectivity is available in the
area, however (whether via ISP or satellite or whatever).
Mamma Mia is the major stakeholder and your point of contact
for this proposal.
Your instructor will fill the role of Mamma and the major
stakeholder.
So all questions for the client should be directed to your class
instructor.
Your team may consider
· clarifying the requirements,
· including the available funding,
· through Private Message email interviews with Mamma Mia.
ITP-3 - Project Risk Assessment (Individual project)
(PMBOK 11)Addresses Course Outcomes #4c and 6e
Please be sure to read the Team Contribution Assessment and
Grading of Team Assignments and the Project Documentation
Requirements sections of this ITP Master Document.
Assignment for the ITP-3 Project Deliverable
This assignment is an INDIVIDUAL assignment. Review your
previous deliverable assignments and the assignments that other
teams have posted in the Shared Learning Environment
Discussions.
This assignment has two parts.
Risk Register in Excel – Part 1
Using your team's ITP WBS, develop and submit a project risk
register in MS Excel:
· A project risk register, from the textbook, from the classroom
material, from www.pmi.org, or from other valid research, that
meets the following requirements.
· In MS Excel, the risk register should be populated w ith the
risks for at least 3 tasks of different types and categories at
EACH level of the decomposition in the WBS (no fewer than 12
tasks must have risks identified -- 3 major tasks, 3 sub-tasks, 3
lowest level leaf node tasks or sub-sub tasks, and also at least 3

risks at the overall project level (Level 0)). (Note that this is
minimum required, along with the other things below, to earn a
satisfactory score. To earn a better score, you would want to
include more risks at each level, and some of the additional
things mentioned below.)
· Risks may include, for example, technical IT risks, external
risks that impact the project but which are outside the PM's
control, project management risks, risks of project changes, and
so forth.
· Please note that a task could have more than one risk! The
risk register must include MITIGATION strategies to
avoid/eliminate or minimize the risk and contingency plans
(what you will do if the risk happens). If the format you are
using does not include these columns, please add them, then be
clear on the difference between mitigation and contingency.
Address what aspect of the project will be affected by each
mitigation action - cost, schedule, or scope. Provide a
recommendation for whether or not the mitigation action should
be implemented, remembering that EACH mitigation will
impact the project's scope, cost or schedule.
The risk register should also include:
· Title or description of item or TASK at risk. (This is the WBS
task in which the risk occurs, not the risk itself.)
· Also include the WBS ID and a designation of which WBS
level the task is at. Each risk in the Risk Register should show
the WBS level of the task that it refers to. I urge you to let the
computer do this for you, since doing it by hand seems error
prone for some reason. Either import the field from MS Project
or use an Excel formula to calculate the level for you.
· Description of the RISK (What is the risk? What is at risk of
happening?) (This identifies the nature of the risk itself, not the
task.)
· Risk category or type (e.g., technical risks, quality risks,
financial risks, external risks, organization risks, project risks,
quality risks, other risks, etc.)
· Consequences, impact, or cost at risk (adjectival or numeric)

· Likelihood or probability (adjectival or numeric)
· Initial risk score (or "risk product", consequence times
likelihood)
· Risk handling category (avoidance, mitigation, transfer,
acceptance, etc.)
· The mitigation action that, if taken, would avoid the risk or
the impact of the risk.
· Cost and time required for the mitigation action.
· Contingency plan - what the team will do if the risk actually
happens
· Designation of risk "owner" or risk manager (best designated
by title or role rather than by individual's name)
For additional points, you may include such things as:
· Additional risks
· Risks for additional tasks
· Results of handling each risk after controls are implemented:
· Consequences or cost at risk
· Likelihood or probability
· Final risk score or product (consequence times likelihood)
· Quantitative numerical consequences, probabilities, and risk
scores (rather than subjective, qualitative, or adjectival
assessments)
· Additional narrative discussion of each risk, handling method,
etc.
· Total of all the risk scores (risk products) for the entire
project after risk controls are implemented, in dollars.
· Also include some risks associated with the general ability to
complete the project successfully. (You might consider these
risks at Level 0, the root level, of the WBS, affecting the entire
project.)
· Finally, if you quantitatively calculated the risk product in
those terms, then what is the total of all the initial risk scores
(risk products) for the entire project, in dollars.Text Document
– Part 2
Please include the Executive Summary with appropriate changes
Questions: In an accompanying Word doc or text submission,

answer the following questions:
1. Which risks (and associated tasks) would be the most
threatening to the success of the project and why? This
discussion should be very specific to tasks and their associated
risks.
2. Which top THREE mitigations (and associated tasks) and risk
handling plans should be implemented, and why? Remember
that mitigation actions will affect cost, schedule and/or scope –
so discuss what can you AFFORD to do based on the likelihood
and impact of the risk?
3. What are the TOTAL impacts on cost, schedule and scope for
the project if the recommended risk controls and mitigation
actions are taken? If you use costs, how did you calculate the
cost? Will the risk handling improve things or make them
worse? That is, will the project cost more and/or be less
successful because of risk handling, or will it cost less and/or
be more successful because of risk handling? How
so? Explain.
4. How did you determine those costs and impacts? Please
describe. What is the benefit of mitigating risks that are
identified for mitigation?
5. If your project could only afford $20,000 for mitigation
actions, which risks (identify associated tasks) would be
implemented?
6. If your project could only tolerate a 5 day delay related to
mitigation actions, which risks and mitigations (identify
associated tasks) would be implemented?
7. What would be the most expensive (time and or schedule)
contingency action/plan? Identify the associated task and
explain why this contingency would be the most expensive in

terms of time or schedule.
8. How did you determine those costs and impacts? Please
describe.
Submit the Excel and the Word document(s) to the Assignment
Area.
Approximate breakdown by areas include:
· General: Structure, Format, Mechanics, Style (~5%)
· Risk register (~84%)
· Questions (~10%)
Rubrics and Grading for the ITP-3 Project Deliverable
To earn 90-100% of the points available for this assignment –
The risk register meets the basic requirements. Identify at least
10 risks at each level of the WBS, including risks that affect the
general ability to complete the project successfully, major tasks
of different types and categories, sub-tasks of different types
and categories, risks of several different risk types and
categories, including external risks, financial risks,
organization risks, PM risks, quality risks, technical risks,
and other risk categories. In addition, include such things as:
· Multiple risks for single tasks
· Quantitative numerical consequences, probabilities, and risk
scores (rather than subjective, qualitative, or adjectival
assessments)
· Show risk assessment (probability, impact, and score)
numerically (e.g., percentages, dollars, etc.) rather than
qualitatively.
· Additional narrative discussion of each risk, handling method,
etc.
· Designation of risk "owner" or risk manager and why that
person or functional position is the “owner”
· Total of all the risk scores (risk products) for the entire
project after risk controls are implemented, in dollars.
· Also include some risks associated with the general ability to
complete the project successfully. (You might consider these
risks at Level 0, the root level, of the WBS, affecting the entire

project.)
· Answer all the initial risk scores (risk products) for the entire
project, in dollars.
Include the following risk info for ea. risk: Title or description
of item or TASK at risk; Description of the RISK; Risk category
or type; Initial assessment of Consequences, impact, or cost at
risk; initial likelihood or probability; Initial risk score
(consequence x likelihood); Risk handling CATEGORY; Risk
handling / control / mitigation / action PLAN; Designation of
risk "owner"; Risk results with/after controls / handling plans
implemented (Consequences or cost with controls; Likelihood
or probability with controls; Final risk score (consequence x
likelihood)). Answer all questions, and include reference
sources are used in the text and included in a Reference page.
Show risk assessment (probability, impact, and score)
numerically (e.g., percentages, dollars, etc.) rather than
qualitatively.
Identify at least 6 risks at each level, including risks such as:
the general ability to complete the project successfully; major
tasks of different types and categories; sub-tasks of different
types and categories; lowest level leaf node tasks or sub-sub
tasks of different types and categories. Include risks of several
different risk types and categories, including risks such as:
external risks, financial risks, organization risks, PM risks,
quality risks, technical risks, and other risk categories.
Include several different risk handling categories (avoidance,
mitigation, transfer, acceptance).
Include most of the following risk info for ea. risk: Title or
description of item or TASK at risk; Description of the RISK;
Risk category or type; Initial assessment of Consequences,
impact, or cost at risk; initial likelihood or probability; Initial
risk score (consequence x likelihood); Risk handling
CATEGORY; Risk handling / control / mitigation / action
PLAN; Designation of risk "owner. Answer all questions.

Identify at least 3 risks at each level, including risks such as:
the general ability to complete the project successfully; major
tasks of different types and categories; sub-tasks of different
types and categories; lowest level leaf node tasks or sub-sub
tasks of different types and categories. Include risks of several
different risk types and categories, including risks such as:
external risks, financial risks, organization risks, PM risks,
quality risks, technical risks, and other risk categories.
Include different risk handling categories (avoidance,
mitigation, transfer, and acceptance).
Include most of the following risk info for ea. risk: Title or
CATEGORY; Risk handling / control / mitigation / action
PLAN; Designation of risk "owner. Answer the majority of the
questions.
Identify at least 6 risks, including risks such as: the general
ability to complete the project successfully; major tasks of
different types and categories; sub-tasks of different types and
categories; lowest level leaf node tasks or sub-sub tasks of
different types and categories. Include risks such as: external
risks, financial risks, organization risks, PM risks, quality
risks, technical risks, and other risk categories. Includes only
one of the risk handling categories (avoidance, mitigation,
transfer, acceptance).
Include much of the following risk info for ea. risk: Title or
CATEGORY; Designation of risk "owner. Answer the majority
of the questions.

Less than 60% -
Risk Registers that do not meet the requirements will earn a
zero. WBSs that are not original work will earn a zero.

Example Risk RegisterExample Risk Register.xlsx WBS 1 20

Recommended

Recommended

More Related Content

Similar to Example Risk RegisterExample Risk Register.xlsx WBS 1 20

Similar to Example Risk RegisterExample Risk Register.xlsx WBS 1 20 (20)

More from BetseyCalderon89

More from BetseyCalderon89 (20)

Recently uploaded

Recently uploaded (20)

Example Risk RegisterExample Risk Register.xlsx WBS 1 20