Hey having a bit of trouble with the structure needed for this assignment and would appreciate some help with an outline for the assignment. This assignment centers around analyzing and recommending a mitigation strategy for one of the project risks. And for this assignment, I am choosing the following risk:

"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."

I would really appreciate help with an outline for analyzing and recommending mitigation strategies for this particular risk!

----------------------------------------------------------------------------------------------------------

IT 328 Milestone Three Guidelines and Rubric

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:

1. 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.
   1. Explain why this risk requires attention. Support your response with examples from the Project Management Documents workbook.
   2. 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.
   3. Explain the implications for the project within the context of the triple constraint if this risk is not addressed.
2. Risk Mitigation: Using all available project documents as guides, recommend a risk mitigationstrategy.
   1. Explain the steps that need to be taken in order to mitigate the identifiedrisk.
   2. 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 deemimportant.
   3. Defend why your proposed mitigation strategy is the best course of action for the projectteam.

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).

What to Submit

Your Milestone Three submission should be in the form of a Word document, should include double spacing, and have one-inch margins.

Week 5 Week 6 Week 7 Task Duration Start Day End Day Predecessors Resource Week 2 Week 8 Week 9 Week 10 Task Name M | T W | T | F | 5 5 M | T W | T | F | S S M | T W T | F | 5 5 M | T W | T | F | 5 5 M | T W | T | F | S S M | T | W | T | F | S S M | T W | T | F | S S M | T W | T | F | S S M | T W T F S S M T W T F | S Mode Names Create the project charter 1 day Day Day 2 John Doe John Doe Develop the project management 2 days Day 2 Day 4 John Doe John Doe plan Define the project scope 4 days Day 2 Day 6 John Doe John Doe W Create a formal budget and budget days Day 6 Day 8 John Doe John Doe plan Fill in a Gantt chart with the project 1 day Day o Day 9 John Doe John Doe schedule and milestones Develop a user interface mockup for 2 days Day S Day 11 5 Ana Fischer Ana Fischer review Create the architectural design for 2 days Day 9 Day 11 5 Ana Fischer Ana Fischer the front end of the application (user-facing) Create the architectal design for the 2 days Day 9 Day 11 John Jones John Jones back end of the application (for data processing) Ana Fischer Develop the graphic user interface 8 days Day 11 Day 19 Ana Fischer (GUI) for the degree tracker Ana Fischer Animated graphical elements to 8 days Day 11 Day 19 Ana Fischer mprove presentation and user experience Day 11 Day 19 Ana Fischer Develop the web code to receive data 8 days Ana Fischer from the back end and place data within the GUI Day 11 Day 16 John Jones I John Jones 12 Develop the back-end code to process 5 days data and send it to the web application 13 Create a defined test plan for all 2 days Day 11 Day 13 7.8 Shila Cole Shila Cole system components Test the scenarios defined in the test 7 days Day 19 Day 26 9,11,12,10 Ana Fischer, Ana Fischer, John Jones, Shila Cole plan for proper application behavior Ana Fischer, John Jones, Shila Cole Perform integration testing to ensure 7 days Day 26 Day 33 14 Ana Fischer, 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 Ana Fischer, John Jones 16 Transition web application into 1 day Day 33 Day 34 15 Ana Fischer, production environment (go-live) John Doe Monitor project progress throughout 36 days Day 1 Day 37 John Doe its life cycle John Doe 18 Manage project deliverables for 36 days Day 1 Day 37 John Doe records and hand-off Ana Fischer, John Doe, John Jones, Shila Cole 19 Assess and manage risks throughout 36 days Day 1 Day 37 Ana Fischer, the project life cycle John Doe 20 Develop the final project report 3 days Day 34 Day 37 16 John Doe John Doe 21 Perform project reflections 1 day Day 34 Day 35 16 John DoeIT 328 Milestone Three Guidelines and Rubric Overview In Milestones One and Two, you specifically focused on Section | 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 Il and Ill of the projectthe project risk description (Section Il) and the risk mitigation recommendation (Section IlI). 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: |. 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 Documents workbook. 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. IIl. Risk Mitigation: Using all available project documents as guides, recommend a risk mitigationstrategy. A. Explain the steps that need to be taken in order to mitigate the identifiedrisk. 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 deemimportant. C. Defend why your proposed mitigation strategy is the best course of action for the projectteam. 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). What to Submit 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. 18 D E F G H I K M N 0 P Q Project Risk Likelihood Implications There is a risk that severe weather in Sailcloth, Maine (the main campus that houses 2 the development team), will close the campus and impact progress. Medium 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. High 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. Low There is a risk for rollout issues when deploying to production due to complexity of 5 merging code with the "go-live" of another project on the same system. High 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. High 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. Low 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 3 schedule. Low > Project Scenario RACI Chart Work Breakdown Structure (WBS) Risk Matrix Team Member Info +Siotm i min s bifkoWw N OU 8w e Project Scenario Regatta University is a leader in both traditional education and career-path development, including in emerging fields. The university prides itself on staying on the leading edge of curriculum and degree programs, learning methodologies and instructional technologies, student services, and demonstrated student success. \"The future is here and now,\" the university's president, Martha Yoon, likes to say. Regatta serves approximately 8,000 students at locations including the original campus in Augusta, Maine, and satellite campuses in Ventura, California; Dayton, Ohio; and Hilo, Hawaii. In a typical term, approximately 40% of Regatta's students take courses at a distance through the university's online education hub. Enrollment growth has been strong, increasing by 4 to 8% each year for the last decade. You are a key member of the information technology team at Regatta, with a core specialization in student services. You are responsible for providing user-friendly interfaces connecting to a flexible, powerful information structure. Now you have a new projectworking with colleagues to create a student degree progress tool that students will use for accurate, instant information on their progress toward program and degree completion. As you may imagine, this tool is eagerly awaited by a variety of stakeholders, including Regatta academic advisors and the Office of Enrollment Management, as tracking and communicating student progress toward degree completion is vital for retention. \"We need a tool that will be easy to use but also accurate. No misinformation!\" your team manager says. Project Scenario [T | Work Breakdown Structure (WBS) | [RiSkMatiix| [ Team Member Info + Raadw 7. A B C D E F G H K L M N O STEP Y DESCRIPTION Jane Smith John Doe Arthur Bowman Shila Cole Ana Fischer John Jones Y 1 Create the project charter A/R Develop the project management plan A/R Define the project scope A/R C/I I I OUT AWN Create a formal budget and budget plan C/I A/R Fill in a Gantt chart with the project schedule and milestones A/R C/I I Develop a user interface mockup for review A/R 7 Create the architectural design for the front end of the application (user-facing) A/R 8 Create the architectural design for the back end of the application A/R (for data processing) 9 Develop the graphic user interface (GUI) for the degree tracker A/R 10 Develop the web code to receive data from the back end and place data within the GUI A/R 11 Develop the back-end code to process data and send it to the web A/R application 12 Create a defined test plan for all system components A/R C/I C/I 13 Test the scenarios defined in the test plan for proper application A/R R R behavior Perform integration testing to ensure that the front-end 14 components and back-end components speak to each other as H A/R R R well as integrate seamlessly with the rest of the web application 15 Transition web application into production environment (go-live) C/I A/R A/R 16 Monitor project progress throughout its life cycle A/R 17 Manage project deliverables for records and hand-off A/R 18 Assess and manage risks throughout the project life cycle A/R R R R 19 Develop the final project report I A/R I 20 Perform project reflections A/R C C C Project Scenario RACI Chart Work Breakdown Structure (WBS) Risk Matrix Team Member Info1.0 Student Degree Progress Project 1.1 Initiation 1.2 Planning 1.3 Execution 1.4 Controlling 1.5 Project Closeout 1.1.1 Project 1.2.1 Scope 1.3.2 1.3.4 Transition to 1.4.1 Monitor 1.4.1 Final Project 1.3.1 Design Implementation 1.3.3 Testing Production Project Progress Report Charter Definition 1.4.2 Project 1.1.2 Project 1.2.2 Budget Plan 1.3.1.1 User 1.3.2.1 Graphical 1.3.3.1 Test Plan 1.4.2 Manage Deliverables Reflections Management Plan Interface Mockup Component Unit (Lessons Learned) 1.2.3 Scheduling 1.3.1.2 1.3.3.2 Test 1.4.3 Assess and Architectural Design 1.3.2.2 Web View (Gantt Chart) Unit Scenarios Manage Risks - Main Application 1.3.1.3 1.3.3.3 Integration Architectural Design 1.3.2.3 Backend Unit Testing Backend Project Scenario RACI Chart Work Breakdown Structure (WBS) Risk Matrix Team Member Info +