Arizona State University

Risk Response Plan

Andrew Hittinger

OGL 421

Professor Matthew Rodgers

April 15, 2022

 Project Risks: Solution: Category Risk Rating Threats and Opportunities
Lack of  Prioritize Communication 6.7 Threats: The lack of communication
Communication communication and the within the project team could cause
importance for it. Set up major delays in the production of our
direct lines of website. We need to put emphasize
communication with communication and hold scheduled
mandatory meetings meetings that all participants are
that all stakeholders required to attend. This will mitigate
must attend. the risk.
 This risk is coming
from Rachel, content Escalate
experts, and web
developers not attending
or avoiding important
meetings.
Minimal  Set communications Communication 2.3 Threats: Our stakeholders and their
support from expectations before the Stakeholder engagement are critical to the success
stakeholders project begins. Assign of this project. Our web design is built
and project tasks and utilize a around their knowledge and expertise.
team calendar for We need their approval on all content
daily/weekly follow being distributed and have to make
ups. Have a plan with sure this information is relayed at the
deadlines and dates to early stages of our project so our web
hold people design team can proceed with the
accountable. Involve construction of the website without the
Tyrell Corp executive delay of “lack of information”.
team if necessary
 Lack of interest or care Avoid
 is driving this, team is
distracted by another
task
Budget  Due to the lack of Communication 5.3 Threats: Our budget is stable as of
interest and engagement Cost management now, however the affect of “lack of
with stakeholders the communication” could cause extensive
project will be delayed. rework and delays to our project. This
This will cause our will affect our budget greatly, and will
budget to be utilized need to be monitored.
quickly and may cause
cost overrun depending
on the engagement we
receive from the Mitigate
stakeholders and project
team
 This risk is caused by
lack of engagement
from stakeholders
Executive  PM and executive sponsor Communication 1.0 Threats: It is important that our
Sponsor will will identify a defined time Resources project sponsor stay engaged
have limited to meet weekly to discuss Project Team throughout the 3-month project. With
availability to project status. other projects going on, this should be
the project  Communication between a priority as we have a strict deadline
the PM and Executive to launch the site. Since there is so
sponsor will include the much information needed by the
executive assistant. executive sponsor, their engagement is
 Project documents, status vital to the success of this project.
reports and project risks
will be updated to reflect Mitigate
the project status.
 To many other projects
going on, lack of interest in
this project in particular
  This is caused by not
prioritizing this project and
the executive sponsor
having to many other tasks
Current system  To mitigate the risk an  Resources 0.4
is out of date evaluation and system  Marketing Opportunities: Creating this new
and will require assessment must be  Project Team design will show our project sponsor
a current-state completed to identify that we are an innovative company
evaluation baseline of system prior to with incredible design. We will take
creating the new system their old/current system, utilize
design. End-to-end system information, however revamp it with
design cannot begin until new resources and information
current state architecture provided to us by the stakeholders.
has been approved. This will only be successful if we have
 Executive sponsor will full engine from our project sponsors.
approve critical system
changes to be implemented Accept
prior to starting new
development.
 Caused by lack of market
research

Extensive  The executive sponsor will  Communicatio 4.8 Threats: If rework is necessary our
rework to bring address the findings of the n budget and timeline may be
system up to assessment.  Resources compromised. Maintaining customer
code for new  The executive sponsor will engagement and utilizing our
product approve the issues resources will be an affective way to
standards identified as critical and reduce rework and maximize
high upgrades. With productivity.
approval, the updates will
be implemented prior to the
new code development. Mitigate
 The project timeline will be
 evaluated at the completion
of the evaluation and
adjustments made to time,
scope, and cost with the
direction of the executive
sponsor.
 System stability sign off by
the executive sponsor is
required before new code
can be implemented.
 Caused by lack of market
research, and web
development testing

The project  The identified project roles  Project Team 7.0 Threats: Utilizing our whole team for
requires full will be filled by internal and  Resources this project will take away resources
capacity of external resources to from other projects, however we will
team resources support the project. need to do this in order to have the
for roles  Resources on the project best possible chance to complete this
identified and must have full capacity and project on time and within budget.
their required availability on the project
availability to for the duration of the Opportunities: Utilizing are whole
work on the project, as defined by the team to work on this project will allow
project. project manager. us to complete this project on or
 Project manager and the before schedule. It will also ensure
functional manager will that our design is to plan and that we
assess the resources and are efficient and accurate in our
manage role replacements project deliverables.
on an individual basis.
 Project manager will Mitigate
escalate any issues with
resources directly to the
functional manager.
  We need to identify key
roles and detail important
responsibilities so the
project team is sure of their
duties

Cross project  Roadmap and high-level Project Team 2.9 Threats: Not having a proper road
initiatives and project evaluation will be Stakeholders map or idea on this project could cause
dependencies conducted by the project project delays. Engaging with our
have not been team to evaluate project stakeholders and identifying a map,
identified or dependencies and initiatives that will help our project team see
defined that could impact the what the finished product is that they
project. are looking for will greatly improve
 The Project Manager will the health of this project.
schedule the working
session with the project Escalate
team.
 The output of the meeting
will be identified project
dependencies.
 Brainstorm in the beginning
of the project to identify
and define all stake holder
initiatives and interest
within this project
Product designs  The product team will be  Project Team 3.9 Threats: Identifying project
and product responsible for the new  Marketing expectations at the start of the project
specifications product specifications and will allow us and our team to identify
approved prior requirements key areas of this project that will
to development documentation. require additional details and work.
starting  The product owner must Identifying this early will help us
approve the requirements manager our resources and capacities
prior to the development allowing us to maintain a schedule that
 team coding the website. will complete this project within the 3-
 Product requirement month timeline.
changes, updates or re-
writes must be assessed for Mitigate
impacts to the project
timeline.
 Changes to the project must
be documented in the
project change log and
approved before work can
begin.

Reflection

The most common response action I used was mitigation. At this stage in the project, we have the chance to correct some of

our negative risk that is on the verge for this project. Establishing a clear action plan to engage our stakeholders will be critical to our

success and mitigating this is the most affective way. As the project manager I need to emphasize the importance of communication

and work directly with our stakeholders and project team to develop an action plan that offers clear and efficient communication

between each of them. As the project manager I do not feel the need to escalate this communication issue or utilize a third party. I

think I have the ability to schedule, and create a meetings schedule that will hold both sides accountable for attendance. If we correct

our communication issue, we will be able to reduce a lot of the risk on our risk registrar. I believe this choice to focus strictly on
communication and creating a meeting agenda will have a positive outcome on our project and reduce all negative risk. Our risk

management strategy is simple, stay efficient, stay communicative and work together as a team to complete this project on time.