IT Final Project
6
Milestone 3
Student name
Institution affiliation
Course name
Date submitted
Milestone 3
Project risk
Risks in the project include any uncertain occurrence that may or may not happen during the project management process. The risks can offer negative or positive impacts on the progress towards the project’s objectives (Qazi et al., 2018). Depending on the project, many risks may arise, and one can outweigh the other. In this project, the risk of rollout issues can be a more significant issue than others. The risk arises during deployment to assembly due to the convolution of amalgamation code with the 'go-live' of a new project in the same structure. The project involves creating a fresh user interface; numerous things can occur throughout the launching phase. The risk needs more attention than other risks, as any wrong line of code can lead to the project's complete stop. This will lead to increased costs and more time, forcing the team to go through the entire code to find the issues. This process will make the group associates spend much stretch on the venture, impacting the calendar. The entity will also need to use more cash to ensure the workers are motivated to complete the project hence the need for more resources.
The realization of this risk can make the entire project's schedule incontrollable because of the various dependencies that depend on having the right code and it is delivered on schedule. One of the dependent tasks that will be impacted involves the development of a user interface mockup for review. This task can be put on grasp or pressed back in the venture life cycle. The issue is attributed to having a wrong code, hence the need to go back and identify where the problem lies, wasting more time in this task completion. Another dependent task that will be impacted is the creation of the website’s front end. The identified threat will make the group affiliated to go back and recreate the tasks of the UI that the wrong code will have negatively impacted. This wastes time as a need to rewrite the front end and ensure it is effectively functional, adding costs for the stakeholder. A bad code impacts the front and back end and hence needs to correct with a new interface. If this risk is attended to, it can lead to clarity among the learners using the interface hence troubles finding the needed information. The issue can also make GUI develop issues, hence impacting its effectiveness. It is crucial to ensure the database is easily accessible for the learners and staff members.
The triple constraint looks at the three most substantial restrictions on any project. This includes the scope, schedule and costs. It is essential as it helps the team adapt to the changing conditions that the project faces daily and in its development process (Kerzner, 2022). The identified risk will affect the three categories. First, the risk will make the investors to use more cash on the venture. The project has its set budget limits; hence additional costs inconvenience the stakeholders and can negatively lead to a possible shutdown of the project. Secondly, the risk will impact the project's timeline or schedule. Any issue that affects the project will bring about various problems with the Gantt chart compelling the manager to engage in various steps aiming to recover the chart. This aims to ensure the project is completed on time or to engage the stakeholders and ask for a time extension. Lastly, the risk will impact the project's scope. This arises from more tasks added to the schedule hence more tasks that need timely completion. This creates scope creep hence affecting the scope and time.
Risk mitigation
A risk mitigation strategy aims at lessening the impacts of potential risks. It involves the development of a plan to manage, eliminate or limit the setbacks as much as possible. There is also a need to monitor progress and evaluate the needed modifications if necessary (Beecham et al., 2021). The proposed mitigation steps are aimed at keeping the project on track. The leading step involves taking a small amount of time and double-checking the project's entire code. This step will help ensure that the created code is effective by checking if there is any issue with the algorithm itself. This includes analyzing the code with every novel line of code to ensure nothing is tossing the venture in a loop. The step can involve a small quantity of extra time in the development stage but will save much time that could be used when trying to find the incorrect line of code. The code testing takes little time and will not impact the project's scope. Another step is allowing every team to test the code and software they create. The step will guarantee the algorithm and the software has no concerns with functioning together with other constituents utilized in the venture.
The proposed mitigation steps aim to ensure the project does not face any delay towards its completion by preventing the risk occurrence. However, they can add unwarranted stretch to the venture timeline, generating scope creep, which can impact the venture's completion stage. This arises from checking the code or software in individual steps to prevent any issues. The constant testing can add unsolicited stretch to the venture hence slowing down other responsibilities that must be completed as per the schedule. The steps are improbable to impact the venture in the end; hence it is a tradeoff as only a little stretch is taken away from the venture itself. The steps also help avoid going back to check the code to identify the underlying issue, either small or big. It is a better tradeoff in the long run as testing the code or the software with the other teams ensures that when the project 'goes live', everything is working well, contributing to the project's success. However, the step can slow things down, affecting the teams as they take too much time to test their code and software with the other teams. If everything is done correctly, then the steps can prevent the risk from occurring.
The proposed risk mitigation strategy is the best action to address the rollout risk. The strategy can help cut down the money used to fix issues that may arise, although it can add time to the project. Testing the algorithm or software can lessen the threats of developing problems in other portions of the venture. The issues can be further prevented by assessing with further portions of the venture to ensure the creation rolls out in time. The coding functionality can be impacted by minor issues, messing up the entire project and creating more time. When the proposed steps are enacted, the issue may not arise, ensuring the stakeholders are happy with the project. If the steps need a little time, they can help cut back spending more money on the project hence helping the project in the long term.
Beecham, S., Clear, T., Lal, R., & Noll, J. (2021). Do scaling agile frameworks address global software development risks? An empirical study. Journal of Systems and Software, p. 171, 110823.
Kerzner, H. (2022). Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons.
Qazi, A., Quigley, J., Dickson, A., & Kirytopoulos, K. (2018). Project Complexity and Risk Management (ProCRiM): Towards modelling project complexity-driven risk paths in construction projects. International journal of project management, 34(7), 1183–1198.