IT 328 Module Five Project Milestone Three
docx
keyboard_arrow_up
School
Southern New Hampshire University *
*We aren’t endorsed by this school
Course
328-Q2207
Subject
Information Systems
Date
Dec 6, 2023
Type
docx
Pages
3
Uploaded by MajorTitanium846
1
Milestone Three Project Risk and Mitigation
Maleka Monono
Southern New Hampshire University
IT 328 Project Mgmt in Info Tech
Professor William Collard
Saturday, November 25th, 2023
2
Project Risk
When working on a project of this magnitude, it is not abnormal for there to be risks. In
this project, there are a few risks that have a high likelihood of occurring. However, there is one
risk that I feel requires immediate attention. 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. The success of the entire project is reliant on the code. If the code is not correct the
program will not be able to function as it should. The code is the brain of the program, it is what
tells the program how to operate. A delay in code causes negative effects to the triple constraint
(scope, time, cost), potentially causing it to increase the triple constraint. We can understand this
more by referring to either the RACI chart or Gantt chart. There are steps that come after the
code, that will not be able to be completed if the code is not correct.
There are multiple dependencies that will be affected by this risk, specifically steps 12
through 15. Any steps that come after where the risk is going to occur will be affected. There are
a couple things that will happen if the code is not written correctly. First, the test plan will have
to be redone along with scenarios to test. Secondly, the integration testing will have to be redone
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. We can only assume that if the code
was inaccurate the integration testing did not have the desired outcome. Thirdly, the transition
web application into production environment (go-live) will not occur. As stated before, if this
risk was to occur it would cause a domino effect within the triple constraint.
The triple constraint is made up of the cost, scope, and time. When one is affected so are
the rest. In the case that this risk is not addressed, the main constraint to be affected would be
time. The software developers on the team would have to either re-write the entire code or take
3
the time to go through the code and find out which part of it isn’t working/incorrect. This would
cause a major delay in the schedule because they are essentially re-doing steps 10 through 14.
Additionally, this would put a strain on costs because double the resources would be used to re-
do or alter steps 10 through 14. Ultimately, the project would be at risk of incompletion due to
the push in schedule, as well as increased costs due to additional resources.
Risk Mitigation
The risk above is mainly caused by a conflict in the schedule. The best way to mitigate
this risk is to add additional time to the coding and testing phases. Coding days, steps 10 and 11,
should each be extended by at least two days. Testing days, steps 12 through 14, should each be
extended by 2 days. This adds an extra 10 days to the project overall. Even though this pushes
the project finish date, it is the best outcome. The project will be late, but the quality of the
product will be at its best. This still affects the triple constraint (cost, time, scope). We are
increasing time which will directly increase cost. However, it is better to plan for an increase in
cost or time than to have it happen abruptly. If this risk were to occur without a mitigation plan in
place, it is a possibility that the project could be delayed more than 10 days. This is the best way
to mitigate this risk because it does not affect the scope of the project. No steps will have to be
repeated and no excessive resources will be spent.
It is important when working on a project of this scale that you have safety measures in place. It
is never a bad idea to have more than one plan. In the long run, we are prepared for the risk
which saves cost and time without addition to scope. The team will be able to work confidently
without being under pressure and produce a high-quality product that the clients will be able to
enjoy.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
- Access to all documents
- Unlimited textbook solutions
- 24/7 expert homework help