While working in IT at Regatta University, you are assigned a second project: updating the look and feel of the of the student services portal. This project runs concurrently with the student degree progress project. Further, because of the interwoven nature of the two codes, the graphical user interface (GUI) update must be deployed at the same time as the student degree progress project. As the GUI project progresses, you realize that its schedule is starting to slip and the GUI project is falling behind. This is causing a major risk to the scheduled delivery of the student degree progress project as well. In your discussion post, do the following: Using the triple constraints, discuss at least one factor (schedule, cost, scope) that could be changed as a solution for ensuring that both projects are delivered at the same time. Review the list of project risks in the Project Management Documents spreadsheet. Will the solution proposed in Step increase the likelihood or potential severity of any of these risks? Identify and describe any new risks raised by the proposed solution. In your responses to classmates, be sure to note areas of similarities and differences in their analyses and your own. Consider the best course of action for keeping both projects on track. As you can see, managing projects can be complex and often requires careful analysis of problems and solutions.

Project Risk	Likelihood	Implications
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.	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 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 schedule.	Low