IT 328 SNHU Severe Weather On Project Development In Sailcloth Paper In Milestones One and Two, you dug into the scenario involving the student degree prog

IT 328 SNHU Severe Weather On Project Development In Sailcloth Paper In Milestones One and Two, you dug into the scenario involving the student degree progress project at Regatta University. In Milestone One, you examined project roles then described the project in concise form. In Milestone Two, you analyzed the work assigned to a technical role in relation to an integrated project schedule then envisioned a new project element and its implications for the project timeline. Now, in Milestone Three, you will draft two key sections of your final project. In this milestone, you will identify and describe a project risk from the list of risks included in the Project Management Document Excel workbook, then you will recommend risk mitigation strategies. Specifically, in this milestone, you will compose Sections II and III of the final project. Section II includes selecting a specific risk, explaining why that risk needs attention, and explaining why it should be addressed. You will also explain the implications for the project if this risk is not addressed. Section III is a recommendation for a risk mitigation strategy. Here, you will explain the steps to be taken to mitigate the risk and how these actions may affect the project. You will then explain why your proposed strategy is the best course of action. PLEASE SEE RUBRIC ATTACHED. IT 328 Milestone Three Guidelines and Rubric
Project Risk and Mitigation
Overview: In Milestones One and Two, you specifically focused on Section I of your final project. In Milestone Three, you will advance toward successful
completion of your final project, the risk analysis and mitigation memo, by drafting key components of the project. Specifically, you will draft Sections II and III of
the project—the project risk description (Section II) and the risk mitigation recommendation (Section III). At this point in your learning experience, these items
have not been further broken down.
In the final project, and here in Milestone Three, you will analyze and recommend mitigation strategies for one project risk. Refer to the risk matrix in the Project
Management Documents Excel workbook to select a project risk to focus on before you proceed. You may pick any one of these risks depending on which area
you mean to speak to. You do not need to pick the most likely or significant risk. The risk you choose to focus on must come from this list.
Prompt: Specifically, Milestone Three must address the following critical elements:
I.
Project Risk: Select a risk from the list in the Project Management Documents workbook. Using this Excel workbook as a guide, provide detailed
information about the specific project risk.
A. Explain why this risk requires attention. Support your response with examples from the Project Management Documentsworkbook.
B. Describe any dependencies within the project that may be affected by this risk. Provide specific examples from the project management
documentation to support your response.
C. Explain the implications for the project within the context of the triple constraint if this risk is not addressed.
II.
Risk Mitigation: Using all available project documents as guides, recommend a risk mitigation strategy.
A. Explain the steps that need to be taken in order to mitigate the identified risk.
B. Explain in detail how the proposed mitigation strategy will affect the project. Include any tradeoffs that must be made to accommodate the
mitigation strategy, and consider the triple constraint and any other variables that you deem important.
C. Defend why your proposed mitigation strategy is the best course of action for the project team.
Remember that your writing throughout the memo should be clear and professional. Use language appropriate for the audience of stakeholders. This will help
you prepare to fulfill part of the final project critical element on communication (Section V, Part A).
Rubric
Guidelines for Submission: Your Milestone Three submission should be approximately 2 pages in length with double spacing, one-inch margins, 12-point Times
New Roman font, and adherence to the latest edition of APA formatting.
Critical
Elements
Attempted With Minimal or No Functional
Issues (100%)
Requires
Attention
Identifies risk and explains why the risk
requires attention with minimal or no errors,
supporting response with examples from
project management documents
Dependencies
Attempted With Significant Functional Issues
(75%)
Not Evident in Submission (0%)
Value
Identifies risk and explains why the risk
requires attention, supporting response with
examples from project management
documents, but with major errors related to
logic, accuracy, or completion
Does not identify risk and explain why the risk
requires attention
15
Describes with minimal or no errors any
dependencies within the project that may be
affected by the risk, including support from
project management documentation
Describes any dependencies within the project
that may be affected by the risk, including
support from project management
documentation, but with major errors related
to logic, accuracy, or completion
Describes any dependencies within the project
that may be affected by the risk
15
Implications
Using the triple constraint as a guide, explains
with minimal or no errors the implications for
the project if the risk is not addressed
Explains within the context of the triple
constraint the implications for the project if
the risk is not addressed but with major errors
related to logic, accuracy, or completion
Does not explain the implications for the
project if the risk is not addressed
15
Mitigate
Explains with minimal or no errors the steps
that need to be taken in order to mitigate the
identified risk
Explains the steps that need to be taken in
order to mitigate the identified risk but with
major errors related to logic, accuracy, or
completion
Does not explain the steps that need to be
taken in order to mitigate the identified risk
15
Affect
Explains in detail with minimal or no errors
how the proposed mitigation strategy will
affect the project, considering the triple
constraint and any other variables deemed
important including any tradeoffs that must be
made to accommodate the mitigation strategy
Explains in detail how the proposed mitigation
strategy will affect the project, considering the
triple constraint and any other variables
deemed important including any tradeoffs
that must be made to accommodate the
mitigation strategy, but with major errors
related to logic, accuracy, or completion
Does not explain how the proposed mitigation
strategy will affect the project
15
Best Course of
Action
Defends with minimal or no errors why the
proposed mitigation strategy is the best
course of action for the project team
Defends why the proposed mitigation strategy
is the best course of action for the project
team but with major errors related to logic,
accuracy, or completion
Does not defend why the proposed mitigation
strategy is the best course of action for the
project team
15
Articulation of
Response
Submission has no major errors related to
citations, grammar, spelling, syntax, or
organization
Submission has major errors related to
citations, grammar, spelling, syntax, or
organization that negatively impact readability
and articulation of main ideas
Submission has critical errors related to
citations, grammar, spelling, syntax, or
organization that prevent understanding of
ideas
10
Total
100%
Project Scenario
Regatta University is a leader in both traditional education and career-path development,
itself on staying on the leading edge of curriculum and degree programs, learning method
services, and demonstrated student success. “The future is here and now,” the university’
Regatta serves approximately 8,000 students at locations including the original campus in
California; Dayton, Ohio; and Hilo, Hawaii. In a typical term, approximately 40% of Regat
university’s online education hub. Enrollment growth has been strong, increasing by 4 to 8
You are a key member of the information technology team at Regatta, with a core special
providing user-friendly interfaces connecting to a flexible, powerful information structure.
colleagues to create a student degree progress tool that students will use for accurate, ins
and degree completion. As you may imagine, this tool is eagerly awaited by a variety of st
and the Office of Enrollment Management, as tracking and communicating student progre
“We need a tool that will be easy to use but also accurate. No misinformation!” your team
th development, including in emerging fields. The university prides
learning methodologies and instructional technologies, student
w,” the university’s president, Martha Yoon, likes to say.
riginal campus in Augusta, Maine, and satellite campuses in Ventura,
ly 40% of Regatta’s students take courses at a distance through the
creasing by 4 to 8% each year for the last decade.
ith a core specialization in student services. You are responsible for
mation structure. Now you have a new project—working with
e for accurate, instant information on their progress toward program
by a variety of stakeholders, including Regatta academic advisors
g student progress toward degree completion is vital for retention.
ation!” your team manager says.
Steps will be highlighted if A and R are not assigned.
RACI Chart
R:
Does the step
A:
Accountable for the step
C:
Consulted with before the step
I:
Informed when the step is completed
Project: Student Degree Progress
DEPARTMENT
STEP
Information Technology
DESCRIPTION
1
2
3
4
5
6
7
8
9
10
11
12
13
Create the project charter
Develop the project management plan
Define the project scope
Create a formal budget and budget plan
Fill in a Gantt chart with the project schedule and milestones
Develop a user interface mockup for review
Create the architectural design for the front end of the
application (user-facing)
Create the architectural design for the back end of the
application (for data processing)
Jane Smith
John Doe
I
C/I
I
A/R
A/R
A/R
A/R
A/R
Arthur Bowman Shila Cole
C
I
I
Ana Fischer
John Jones
C/I
I
I
C/I
I
A/R
I
A/R
A/R
Develop the graphic user interface (GUI) for the degree tracker
A/R
Develop the web code to receive data from the back end and
place data within the GUI
Develop the back-end code to process data and send it to the
web application
Create a defined test plan for all system components
Test the scenarios defined in the test plan for proper application
behavior
A/R
A/R
14
Perform integration testing to ensure that the front-end
components and back-end components speak to each other as
well as integrate seamlessly with the rest of the web application
I
15
Transition web application into production environment (go-live)
C/I
16
17
18
19
20
Monitor project progress throughout its life cycle
Manage project deliverables for records and hand-off
Assess and manage risks throughout the project life cycle
Develop the final project report
Perform project reflections
I
Page 3 of 9
A/R
A/R
A/R
A/R
A/R
A/R
C/I
C/I
A/R
R
R
A/R
R
R
A/R
A/R
R
R
R
C
C
C
I
I
I
1.0 Student Degree
Progress Project
1.1 Initiation
1.2 Planning
1.3 Execution
1.1.1 Project Charter
1.2.1 Scope
Definition
1.1.2 Project
Management Plan
1.2.2 Budget Plan
1.3.1.1 User
Interface Mockup
1.3.2.1 Graphical
Component Unit
1.2.3 Scheduling
(Gantt Chart)
1.3.1.2 Architectural
Design – Main
Application
1.3.2.2 Web View
Unit
1.3.1.3 Architectural
Design – Backend
1.3.2.3 Backend Unit
1.3.1 Design
1.3.2 Implementation
dent Degree
ess Project
1.3 Execution
ckend Unit
1.4 Controlling
1.4.1 Monitor Project
Progress
1.4.1 Final Project
Report
1.3.3.1 Test Plan
1.4.2 Manage
Deliverables
1.4.2 Project
Reflections (Lessons
Learned)
1.3.3.2 Test
Scenarios
1.4.3 Assess and
Manage Risks
1.3.3 Testing
1.3.3.3 Integration
Testing
1.3.4 Transition to
Production
1.5 Project Closeout
Project Risk
There is a risk that severe weather in Sailcloth, Maine (the main campus that houses
the development team), will close the campus and impact progress.
There is a risk that the ambiguity in the project scope (it only defines “graphical
element” but not what type) will lead to requirement changes by the stakeholder
during development, affecting both the budget and schedule.
There is a risk that sign-off on project deliverables (charter, Gantt chart, product
approval, etc.) from project sponsors and stakeholders exceeds the allotted time.
This decision delay will impact the progress schedule.
There is a risk for rollout issues when deploying to production due to complexity of
merging code with the “go-live” of another project on the same system.
Two projects are currently being developed at the same time in the same code base.
Delays to the secondary project will cause delays to the Student Progress go-live.
The student portal where the project will be deployed is a high-availability system and
is expected to be accessible for students 24/7. There is a risk that the large number
of changes occurring during go-live could take the system offline, temporarily
impacting system availability.
There is a risk that an interpersonal conflict will arise within the team, impacting the
human resources assigned to the project and potentially impacting the allotted
schedule.
Likelihood
Medium
High
Low
High
High
Low
Low
Implications
Role
Name
Jane Smith
John Doe
Arthur Bowman
Shila Cole
Ana Fischer
John Jones
Role Description

Purchase answer to see full
attachment