Project Management Software Evaluation: A PRINCE2 Approach

Desklib provides past papers and solved assignments. This project evaluates risk management software using PRINCE2.

PROJECT PROPOSAL

Topic Title
Project Management and Information Technology
The aim of the topic
The general aim of the project is to examine multiple software for risk management and identify
the abilities of the software. This aims to select suitable software for a specific application. It
helps to develop the knowledge of software in project management discipline area. The purpose
is to investigate various software that can support the processes of the project category i.e. Risk
management. This help to increase the knowledge to use the software for project management.
Proposed methodology
For the management of the project, the proposed methodology is PRINCE 2. This is able to
manage all types of project. It is based on the process. The main steps of the project management
using PRINCE2 are:
1. Directing the project: Direction of the project runs from the start of the project until the end
of the project.
2. Start the project: This is the first phase in PRINCE2. This process ensures that all the pre-
requirements are in place for the successful completion of the project. It helps to create the
initiation phase plan.
3. Initiate the project: The objectives of project initiation are to create a stable management base
and agree to the commitment of the resources. It also offers a base guideline for the process
of decision making.
4. Manage the boundaries: It offers the key discussion points to determine that all the
deliverables planned have been completed as planned and defined. It also provides
information to assess the continuing viability of the project.
5. Stage controlling: This describes the control and monitoring activities of the manager of the
project. This stage consists of progress information gathering, authorization of the work,
reporting and reviewing the situation and take appropriate actions if required.
6. Management of project delivery: This phase is responsible for the correct delivery of the
project. It helps to ensure that the work is completed properly, and the outcome is meeting
the criteria of quality.

7. Close the project: The aim of this stage is to achieve acceptance for the deliverables of the
project. It helps to confirm the operation arrangements and maintenance are proper or not.
This process confirms the outcome of the project and closed in a controlled manner
(Vaníčková, 2017).
List of software for evaluation
There are a number of software available for risk management such as nTask, Resolver,
TimeCamp, Qualys, Master Control Risk Analysis, etc. Each software has its own set of
qualities, features, and disadvantages. Selected tools for evaluation are given below:
 nTask
 Resolver
 TimeCamp
Expected outcomes
Expected outcomes of the evaluated software using an PRINCE2 approach will give the idea
about the software. This will help to determine the suitable software on the basis of criteria. The
criteria are cost, performance, flexibility, features, accessibility, user interface, etc. This help to
determine the capabilities of the software and determine whether the software is able to integrate
with other application or not (Pimchangthong and Boonjing, 2017). List of expected outcomes
are:
 Identify potential issues and threats
 Reduce the risk
 Protect the resources
 Maximize the stability and availability of the services
 Make operations smooth
 Help to save cost and time
 Maintain the reputation of the company
 Improve the performance and productivity of the company

The proposed structure of the report
For stage 2, the report will be a detailed description. The report will be in the following format;
 Cove page with the Title
 Front page
 Content list
 Executive summary
 Investigation aim
 Topic introduction
 the significance of the investigation
 List of the available software
 Selection of the software for the evaluation
 Review the selected three criteria
 Identification and set of criteria for the evaluation
 Discussion on Criteria weighting
 Get Evaluation matrix
 justification of the software weighting criteria
 Result in discussion
 Pitfalls and problem discussion
 Recommendations and acknowledgment,
 Reference
 Appendix.

List of references
Pimchangthong, D. & Boonjing, V. (2017). Effects of Risk Management Practice on the Success
of IT Project. Procedia Engineering, 182(67), pp.579-586.
Vaníčková, R. (2017). Application of PRINCE2 Project Management Methodology. The Journal
of University of Economics in Bratislava Studia Commercialia Bratislavensia, 10(38), pp.227–
238.

Appendix

Project delivery plan with a timeline
The given work breaks down structure is a brief overview of the tasks and activities involved in
the project.
Figure 1 Work break down structure
The project delivery plan includes the tasks list, duration and estimated time to complete the
task. The project plan has main 3 tasks which are project proposal, project report and project
presentation. The project will require 18 days of duration for completion.