University Project Management: Request Tracker Risk Management Report

This report examines the Request Tracker project, initiated to replace the problematic Remedy ticketing system. It details the project's background, highlighting the shift to an open-source solution to reduce costs. The core of the report centers on a comprehensive risk management plan, identifying potential issues such as lack of team coordination, unsuitable leadership, time management deficiencies, and security breaches. Each identified risk is analyzed, and corresponding mitigation strategies are proposed, including improved communication, stricter deadlines, and the implementation of a ticketing system. The report stresses the importance of an agile project management plan and the need for clear roles and responsibilities, advocating for regular meetings and proactive monitoring by supervisors to ensure the project's success. The conclusion underscores the necessity of a structured project management approach and the individual responsibility required for successful project outcomes.

Running head: BSC PROJECT MANAGEMENT
BSC Project Management
Name of the Student
Name of the University
Author’s note

1BSC PROJECT MANAGEMENT
Executive Summary
Ron Bashley, an OIT employee along with Harry Bonnett, the Director of Information
Systems Department work on Request Tracker project to fix ticketing system issues. The
previous initiative Remedy failed in some instances very badly with utter disappointments
besides for Remedy requires $20,000 per year for the licensing so Ron's supervisor Backen
called a meeting and there all the members of the meeting decided to move to open-source
and hence initiated the project Request Tracker. Request Tracker will work similar to
Remedy and will cut down the heavy budget and expenses. The project should be done
according to a project management plan to get the desired result. This report also showcased
that Ron should be more responsible for his job. The report highlighted all the risks
associated with the Request Tracker project and also the procedures to mitigate those risks.

2BSC PROJECT MANAGEMENT
Table of Contents
1. Introduction............................................................................................................................2
2. Background of the case study................................................................................................2
3. Risk management Plan...........................................................................................................2
4. Identify risks associated with this project..............................................................................3
5. Risk analysis for identified risks............................................................................................4
6. Risk responses plan for identified risks.................................................................................4
7. Plan for monitoring and controlling identified risks..............................................................4
8. Justification of your proposed risk management Plan...........................................................5
9. Conclusion..............................................................................................................................5
10. References............................................................................................................................6

3BSC PROJECT MANAGEMENT
1. Introduction
Ron Bashley, an OIT employee along with Harry Bonnett, the Director of Information
Systems Department work on Request Tracker project to fix ticketing system issues. The
report will highlight all the risks associated and will provide probable solutions to mitigate
those risks.
2. Background of the case study
Ron and Harry started working on the Request Tracker project to improve the
ticketing system, the previous initiative Remedy failed in some instances very badly with
utter disappointments besides for Remedy requires $20,000 per year for the licensing, so
Ron’s supervisor Backen called a meeting and there all the members of the meeting decided
to move to open-source and hence initiated the project Request Tracker. Request Tracker will
work similar to Remedy and will cut down the heavy budget and expenses [2].
3. Risk management Plan
Each and every organisation should have a project management plan and the
employees of the organisation from managers to the employees should follow the project
management plan. They should adopt the agile project management plan which is widely
used worldwide. The project management procedure ensures that all the employees work in a
particular organisation work as an integrated unit sequentially. At first, a plan is made, and
then based on the plan, a design is made, then according to the design the plan is executed
accordingly, after partial completion the project is working properly or not is checked, after
accomplishing the task properly, the employee's further progress [3]. Each employee has his
duty and has to perform it with full responsibility that is how any organisation can mitigate
the risks within the organisation.

4BSC PROJECT MANAGEMENT
4. Identify risks associated with this project
There are a whole lot of risks associated with the project. At first, there is no
coordination among the departments, Ron is working his way and Harry on his own way,
there is an obvious risk that the project will fail. Secondly, as a team leader Ron is not
suitable, he does not have the leadership skills at all [1]. He is taking the project lightly
simply stating the project as informal. The members of Ron remain absent and they do not
work with full responsibility, Ron entrusted whichever member he gets and give the
responsibility. Thirdly, there is no time management plan for Ron, no deadline, no target at
all. The project is continuing and they do not know whether it will be completed within the
six months or not. Fourthly there are security breaches in the project. He uses email to
connect with the subordinates, the subordinates in terms do not reply back, it is obvious that
there is a lack of responsibility, there is another issue lying over there, the intruders and the
hackers can attack and hack the computer system and exploit the whole system vulnerable to
work [7]. The code Harry shared will get compromised; the whole Request Tracker project
will fail miserably.
Fifthly, since Ron is not working properly, the whole Request Tracker project will
probably go live without testing and it will malfunction for sure, the intruders again come
into play and will take advantage of the underdeveloped software. Ron should have tested the
bug report properly and should have made a query to Harry with full responsibility instead he
just sends an email and report the bugs to Harry. This casualty is not expected. Lastly, there is
no coordination between the between Ron's supervisor and Harry's supervisor, so it is the big
risk for them [8].

5BSC PROJECT MANAGEMENT
5. Risk analysis for identified risks
Due to above risks, the project will complete from Harry's end but from The Ron's
end, the project is likely going to fail [6]. Ron has totally failed to control his team and team
members, he has no proper time management, he will not able to finish the task within
deadline, the security breaches will be the big issue for them, again since Ron is not working
as per responsibility, the application software will go live without properly patched, the app
may malfunction [2]. There is no coordination between Ron's supervisor and Harry's
supervisor, so it is looking obvious the project will fail.
6. Risk responses plan for identified risks
At first, Ron's supervisor and Harry's supervisor will have to communicate with each
other and will have to solve the risks. Ron should be serious about the whole project, he will
have to be strict with the deadline, and he will have to act with his subordinates as an
authoritarian so that the subordinates do not take the project lightly. Ron will have to
communicate with Harry and should conduct a meeting on daily basis to solve the risks and
the bugs within the project besides sending emails [4]. The emails contain the project code
and sensitive information, Ron should take Harry’s ticketing system approach alongside
sending emails. All these mentioned approaches will definitely help to mitigate the risks.
7. Plan for monitoring and controlling identified risks
At first, Ron should communicate with Harry properly, He should conduct meeting
with Harry daily, should discuss the bug and the productivity. Ron should act as an
authoritarian towards his subordinates and should support them at the time of need. Ron
should be strict about the project’s deadline; he along with Harry will have to complete the
project within six months [5]. To mitigate the security breaches he should focus on the
ticketing system, this methodology is both safe and secure. Ron should act proactively and

6BSC PROJECT MANAGEMENT
should discuss with Harry about the bugs, if the project fails then there will be huge loss of
time and money, sending emails only will not going to work. The supervisors of both the
department should monitor the proceedings of the project; instead they give full responsibility
to Harry and Ron [4].
8. Justification of your proposed risk management Plan
The agile project management plan will work great in this scenario. Harry’s
responsibility is to plan, design and develop the software and handle the back-end of the
project. Therefore, Harry should divide the task properly among the subordinates via
ticketing system, after finishing each task, should send the partial report or the progress report
of the project to Ron, Ron analysing the whole partial report submission should send it to
Ron's supervisor for further approval, if it is fine, Harry should continue his work, if any
mishaps or occur Harry's supervisor and Harry will have to look upon it and discuss it via
conducting meetings. All these initiatives should be performed by conducting meetings and
not by emails and online chatting [2]. The process should be repeated for all the partial
submissions and all project activities. Ron handling the front–end of the project should also
follow the ticketing system for all his subordinates. Both Harry and Ron should set a deadline
for each partial submissions keeping in mind the project’s final deadline is six months. If all
the above approach is followed the project will definitely successful [3].
9. Conclusion
It can be concluded from the above discourse that the project should be done
according to a project management plan to get the desired result. On the other hand, Ron
should be more responsible for his job. The report highlighted all the risks associated with the
Request Tracker project and also the procedures to mitigate those risks.

7BSC PROJECT MANAGEMENT
10. References
[1] Kerzner, Harold. Project management: a systems approach to planning, scheduling, and
controlling. John Wiley & Sons, (2013).
[2] Burke, Rory. "Project management: planning and control techniques." New Jersey,
USA (2013).
[3] Larson, Erik W., and Clifford Gray. Project Management: The Managerial Process with
MS Project. McGraw-Hill, (2013).
[4] Schwalbe, Kathy. Information technology project management. Cengage Learning,
(2015).
[5] Walker, Anthony. Project management in construction. John Wiley & Sons, (2015).
[6] McNeil, Alexander J., Rüdiger Frey, and Paul Embrechts. Quantitative risk management:
Concepts, techniques and tools. Princeton university press, (2015).
[7] Lam, James. Enterprise risk management: from incentives to controls. John Wiley &
Sons, (2014).
[8] Hopkin, Paul. Fundamentals of risk management: understanding, evaluating and
implementing effective risk management. Kogan Page Publishers, (2017).