ITC505 Project Management Assignment 3: RALS & Globex Ticketing System

This document presents a comprehensive project management assignment solution for ITC505, focusing on the development of a ticketing system for RALS and Globex. The assignment is divided into six parts, starting with the Measurable Organizational Value (MOV) analysis, evaluating financial, customer, operational, strategic, and social areas. Part two defines the project scope, outlines requirements, and creates a scope management plan. Part three provides a detailed project schedule. Part four conducts a project risk analysis, identifying potential risks and mitigation strategies. Part five focuses on the quality management plan, including verification and validation activities. Finally, part six covers closure and evaluation, along with an annotated bibliography. The solution includes diagrams, tables, and references to support the analysis and planning of the project.

Running head: ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
ITC505 Assignment 3: Project Management
Name of the Student:
Student ID:
Name of the University:
Author’s note:

1ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
1. Part One: MOV - Measurable Organisational Value
The analysis of the areas of comparison for the development of the project in terms of
financial, customer, operational, strategy, and social are given below,,
a) Financial Area: The aspect of financial area is very crucial for the development of the
project and its implication for the management of the functions. The analysis would
show the formation of the figurative development of the finances and their implication
for the development of the final aspects.
b) Customer Area: The customers play a crucial role in aligning the development of the
effective and improved processes. The customer area is a measure of the influence of
the customers on the operations of the project. It would form the prospect of
developing the operations of the organization.
c) Operational Area: The operations of the project would tend to imply the formation of
the sufficient deployment of the project and its functions. The RALS project would
have to ensure that the operations of the project would tend to imply the magnificent
deployment of operations.
d) Strategy Area: Business organizations have been using the business operation
development by the help of smart and effective strategy development. The strategy
area would form the integration of the supportive management of the operations for
forming the analysis of the project.
e) Social Area: Project organizations have been using the formation of the social
upliftment and management for ensuring the support of the government and local
community. The social area helps in forming the management of the operations for
developing the organizational process.

2ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
 Better- Ticketing system developed in the project would help in overcoming the
management of the operations for RALS and Globex. The improvement of the
operations would help in critical evaluation of the operations and functions.
 Faster- Ticketing system developed in the project would help in improving the
efficiency of operations by critical evaluation of the project integration and
management. The increased pace of operations would help in final management of the
operations.
 Cheaper- Ticketing system developed in the project would help in forming the ease of
operations which would involuntarily decrease the overall cost of the functions. The
services of RALS and Globex.
 Do more- Ticketing system developed in the project would help in increasing the
functionality and aspect of developing the project operation.
Rank Impact Metrics Timeframe
1 Financial Profit Calculation, Revenue, and NPV 180 days
2 Customer Customer feedback and Suggestions 130 days

3ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
3 Operational Operation Management Plan 240 days
4 Strategy Strategic Analysis Matrix 320 days
5 Social Support from local community and government 100 days
2. Part Two: Define Scope and produce a Scope Management Plan
Define the scope: The extent of the project scope can be realized as the advancement of the
ticketing framework for shaping the viable and enhanced operations of the association for
RALS by dealing with the client's data
Requirements: The human prerequisites of the task are Budgeter, Documenter, IT Engineer,
Planner, Project Manager, System Analyst, Tester, and Contractor. The materialistic
prerequisites of the task are Computer Devices, Network Components, Storage, and Wireless
switches.
In scope-out scope items: The project design, advancement of the framework, change of
operations, and joining of the capacity are in-scope things of the task. The transportation of
the materials, correspondence design, and investigate change administration are of degree for
the undertaking.
Deliverables: The Project Plan, Initiation Documents, Charter Documents, System Design,
and Ticketing System are the expectations for the project deliverables.
Acceptance Criteria: The statement of the acceptance criteria for the project is,

4ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
The ticket system for RALS in Globe would help in building up the quicker operations and
procedures of the association and improvement of the viable operations for Globex that
would diminish the general cost of upkeep and administration of information for RALS
Provide a list of Resources: The following diagram would show the use of the resources in
the project,

5ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
ID Resource Name Work
1 Budgeter 112 hrs
Feasibility Analysis 16 hrs
Budget development 32 hrs
Resources are accumulated 64 hrs
2 Computer Devices 1
Hardware components are deployed 1
3 Documenter 100 hrs
Project Charter Documentation 32 hrs
Project Initiation Documents 24 hrs
Submission of documents 2 hrs
Project Closure checklist is formed 16 hrs
Final reports are developed 24 hrs
Submission of documents 2 hrs
4 IT Engineer 216 hrs
Reviewing the design 8 hrs
Design Simulation 16 hrs
Storage system is developed 40 hrs
Database is integrated 24 hrs
User Interface is developed 32 hrs
Programming and Coding the ticketing system 80 hrs
Hardware components are deployed 16 hrs
5 Network Components 1
Hardware components are deployed 1
6 Planner 72 hrs
Analyzing the Requirements 24 hrs
Selection of planning methodology 8 hrs
Developing plan outline 24 hrs
Reviewing the plan 16 hrs
7 Project Manager 76 hrs
Kick off meetings 6 hrs
Client's requirement analysis 24 hrs
Team members are selected 40 hrs
Reviewing the documents 5 hrs
Signing the documents 1 hr
8 Storage 1
Storage system is developed 1
9 System Analyst 128 hrs
Selecting design platform 16 hrs
Making appropriate design 56 hrs
Prototyping the design 24 hrs
Functions Integration in the system 32 hrs
10 Tester 120 hrs
User Interface is tested 24 hrs
Black box testing 24 hrs
White Box testing 24 hrs
User experience analysis 24 hrs
Test run and Simulation 24 hrs
11 Wireless routers 1
Hardware components are deployed 1
12 Contractor 48 hrs
Infrastructure is developed 48 hrs
Details
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
Work
S T T S M W F S T T S
Sep 24, '17 Oct 29, '17 Dec 3, '17 Jan 7, '18 Feb 11, '18
16h 24h 72h
16h
24h 8h
64h
1
1
8h 50h 42h
8h 24h
24h
2h
16h
24h
2h
8h 96h 88h 8h 16h
8h
16h
40h
24h
16h 16h
72h 8h
16h
1
1
24h 40h 8h
24h
8h
24h
8h 8h
6h 64h 6h
6h
24h
40h
5h
1h
1
1
8h 88h 32h
8h 8h
56h
24h
32h
80h 40h
24h
24h
24h
8h 16h
24h
1
1
48h
48h

6ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
3. Part Three: Project Schedule
The schedule of the project can be understood by the help of the following diagrams,
ID Task
Mode
WBS Task Name Duration Start Finish Predecessors
0 0 Ticketing System
Development for RALS
109 days Mon
10/2/17
Thu 3/1/18
1 1 Project Initialization 13 days Mon 10/2/17Wed 10/18/17
2 1.1 Feasibility Analysis 2 days Mon 10/2/17 Tue 10/3/17
3 1.2 Analyzing the Requirements 3 days Wed 10/4/17 Fri 10/6/17 2
4 1.3 Project Charter Documentation4 days Mon 10/9/17 Thu 10/12/17 3
5 1.4 Project Initiation Documents 3 days Fri 10/13/17 Tue 10/17/17 4
6 1.5 Kick off meetings 6 hrs Wed 10/18/17Wed 10/18/17 5
7 1.6 Submission of documents 2 hrs Wed 10/18/17Wed 10/18/17 6
8 M1 Signing the documents 0 days Wed 10/18/17Wed 10/18/17 7
9 2 Project Planning and
Resource Accumulation
26 days Thu
10/19/17
Thu
11/23/17
10 2.1 Selection of planning methodology1 day Thu 10/19/17 Thu 10/19/17 8
11 2.2 Developing plan outline 3 days Fri 10/20/17 Tue 10/24/17 10
12 2.3 Reviewing the plan 2 days Wed 10/25/17Thu 10/26/17 11
13 2.4 Client's requirement analysis 3 days Fri 10/27/17 Tue 10/31/17 12
14 2.5 Team members are selected 5 days Wed 11/1/17 Tue 11/7/17 13
15 2.6 Budget development 4 days Wed 11/8/17 Mon 11/13/17 14
16 2.7 Resources are accumulated 8 days Tue 11/14/17 Thu 11/23/17 15
17 M2 Project Plan is approved 0 days Thu 11/23/17 Thu 11/23/17 16
18 3 System Development and Testing64 days Fri 11/24/17 Wed 2/21/18
19 3.1 Designing the system 15 days Fri 11/24/17 Thu 12/14/17
20 3.1.1 Selecting design platform 2 days Fri 11/24/17 Mon 11/27/17 17
21 3.1.2 Making appropriate design 7 days Tue 11/28/17 Wed 12/6/17 20
22 3.1.3 Reviewing the design 1 day Thu 12/7/17 Thu 12/7/17 21
23 3.1.4 Prototyping the design 3 days Fri 12/8/17 Tue 12/12/17 22
24 3.1.5 Design Simulation 2 days Wed 12/13/17Thu 12/14/17 23
25 M3 Design Approval 0 days Thu 12/14/17 Thu 12/14/17 24
26 3.2 Developing the system 34 days Fri 12/15/17 Wed 1/31/18
27 3.2.1 Storage system is developed5 days Fri 12/15/17 Thu 12/21/17 25
28 3.2.2 Database is integrated 3 days Fri 12/22/17 Tue 12/26/17 27
29 3.2.3 User Interface is developed4 days Wed 12/27/17Mon 1/1/18 28
30 3.2.4 Programming and Coding
the ticketing system
10 days Tue 1/2/18 Mon 1/15/18 29
31 3.2.5 Functions Integration in the system4 days Tue 1/16/18 Fri 1/19/18 30
32 3.2.6 Infrastructure is developed 6 days Mon 1/22/18 Mon 1/29/18 31
33 3.2.7 Hardware components are
deployed
2 days Tue 1/30/18 Wed 1/31/18 32
34 M3 System is developed for Globex0 days Wed 1/31/18 Wed 1/31/18 33
35 3.3 System Testing 15 days Thu 2/1/18 Wed 2/21/18
36 3.3.1 User Interface is tested 3 days Thu 2/1/18 Mon 2/5/18 34
37 3.3.2 Black box testing 3 days Tue 2/6/18 Thu 2/8/18 36
38 3.3.3 White Box testing 3 days Fri 2/9/18 Tue 2/13/18 37
39 3.3.4 User experience analysis 3 days Wed 2/14/18 Fri 2/16/18 38
40 3.3.5 Test run and Simulation 3 days Mon 2/19/18 Wed 2/21/18 39
41 M4 Testing Reports are developed0 days Wed 2/21/18 Wed 2/21/18 40
42 4 Final Documentation 6 days Thu 2/22/18 Thu 3/1/18
43 4.1 Project Closure checklist is formed2 days Thu 2/22/18 Fri 2/23/18 41
44 4.2 Final reports are developed 3 days Mon 2/26/18 Wed 2/28/18 43
45 4.3 Submission of documents 2 hrs Thu 3/1/18 Thu 3/1/18 44
46 4.4 Reviewing the documents 5 hrs Thu 3/1/18 Thu 3/1/18 45
47 4.5 Signing the documents 1 hr Thu 3/1/18 Thu 3/1/18 46
48 M5 Project Closed 0 days Thu 3/1/18 Thu 3/1/18 47
Budgeter
Planner
Documenter
Documenter
Project Manager
Documenter
10/18
Planner
Planner
Planner
Project Manager
Project Manager
Budgeter
Budgeter
11/23
System Analyst
System Analyst
IT Engineer
System Analyst
IT Engineer
12/14
IT Engineer,Storage[1]
IT Engineer
IT Engineer
IT Engineer
System Analyst
Contractor
Computer Devices[1],IT Engineer,Network Component
1/31
Tester
Tester
Tester
Tester
Tester
2/21
Documenter
Documenter
Documenter
Project Manager
Project Manager
3/1
S T M F T S W S
Sep 24, '17 Dec 3, '17 Feb 11, '18 Apr 22, '18

7ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
0
Ticketing System
Development for RALS
1
Project Initialization
1.1
Feasibility Analysis
1.2
Analyzing the
Requirements
1.3
Project Charter
Documentation
1.4
Project Initiation
Documents
1.5
Kick off meetings
1.6
Submission of
documents
M1
Signing the documents
2
Project Planning and
Resource Accumulation
2.1
Selection of planning
methodology
2.2
Developing plan
outline
2.3
Reviewing the plan
2.4
Client's requirement
analysis
2.5
Team members are
selected
2.6
Budget development
2.7
Resources are
accumulated
M2
Project Plan is
approved
3
System Development
and Testing
3.1
Designing the system
3.1.1
Selecting design
platform
3.1.2
Making appropriate
design
3.1.3
Reviewing the design
3.1.4
Prototyping the design
3.1.5
Design Simulation
M3
Design Approval
3.2
Developing the system
3.2.1
Storage system is
developed
3.2.2
Database is integrated
3.2.3
User Interface is
developed
3.2.4
Programming and
Coding the ticketing
system
3.2.5
Functions Integration in
the system
3.2.6
Infrastructure is
developed
3.2.7
Hardware components
are deployed
M3
System is developed
for Globex
3.3
System Testing
3.3.1
User Interface is tested
3.3.2
Black box testing
3.3.3
White Box testing
3.3.4
User experience
analysis
3.3.5
Test run and
Simulation
M4
Testing Reports are
developed
4
Final Documentation
4.1
Project Closure
checklist is formed
4.2
Final reports are
developed
4.3
Submission of
documents
4.4
Reviewing the
documents
4.5
Signing the documents
M5
Project Closed
0
1
2345678
9
1011121314151617
18
19
202122232425
26
2728293031323334
35
363738394041
42
434445464748
109 days 0%
10/2/17 3/1/18
13 days 0%
10/2/17 10/18/17
2 days 0%
10/2/17 10/3/17
3 days 0%
10/4/17 10/6/17
4 days 0%
10/9/17 10/12/17
3 days 0%
10/13/17 10/17/17
6 hours 0%
10/18/17 10/18/17
2 hours 0%
10/18/17 10/18/17
0 days 0%
10/18/17 10/18/17
26 days 0%
10/19/17 11/23/17
1 day 0%
10/19/17 10/19/17
3 days 0%
10/20/17 10/24/17
2 days 0%
10/25/17 10/26/17
3 days 0%
10/27/17 10/31/17
5 days 0%
11/1/17 11/7/17
4 days 0%
11/8/17 11/13/17
8 days 0%
11/14/17 11/23/17
0 days 0%
11/23/17 11/23/17
64 days 0%
11/24/17 2/21/18
15 days 0%
11/24/17 12/14/17
2 days 0%
11/24/17 11/27/17
7 days 0%
11/28/17 12/6/17
1 day 0%
12/7/17 12/7/17
3 days 0%
12/8/17 12/12/17
2 days 0%
12/13/17 12/14/17
0 days 0%
12/14/17 12/14/17
34 days 0%
12/15/17 1/31/18
5 days 0%
12/15/17 12/21/17
3 days 0%
12/22/17 12/26/17
4 days 0%
12/27/17 1/1/18
10 days 0%
1/2/18 1/15/18
4 days 0%
1/16/18 1/19/18
6 days 0%
1/22/18 1/29/18
2 days 0%
1/30/18 1/31/18
0 days 0%
1/31/18 1/31/18
15 days 0%
2/1/18 2/21/18
3 days 0%
2/1/18 2/5/18
3 days 0%
2/6/18 2/8/18
3 days 0%
2/9/18 2/13/18
3 days 0%
2/14/18 2/16/18
3 days 0%
2/19/18 2/21/18
0 days 0%
2/21/18 2/21/18
6 days 0%
2/22/18 3/1/18
2 days 0%
2/22/18 2/23/18
3 days 0%
2/26/18 2/28/18
2 hours 0%
3/1/18 3/1/18
5 hours 0%
3/1/18 3/1/18
1 hour 0%
3/1/18 3/1/18
0 days 0%
3/1/18 3/1/18

8ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
4. Part Four: Project Risk Analysis and Plan
Risk Over
budgeting
Management
Issues
Delay in
Project
System
failure
Design Flaws
Ref no RTF2001 RTF2002 RTF2003 RTF2004 RTF2005
Description
Rank 2nd 4th 5th 1st 3rd
Category Financial Operational Performance Technical Technical
Triggers Insufficient
resources
and Issues in
project
Lack of the
Strategic
management
framework
Issues in
Project
Management
and
Operations
System
Flaws
Designing
errors
Potential
Responses
use of
contingency
or
provisional
resources
Deploying
strategic
management
structure in
the project
Deploying
scheduling
methods of
project and
system
administration
Preliminary
testing and
Prototyping
SDLC
implementation
for system
designing
Risk Owner Budgeter Project
Manager
Planner IT Engineer Designer

9ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
Probability Possible Possible Almost
Certain
Likely Likely
Impact Medium Medium Very Low Critical Medium
5. Part Five: Quality Management Plan.
The association of RALS would incorporate the utilization of task advancement standards for
building up the successful and enhanced administrations in the association with the assistance
of Ticket System to be produced
A set of verification activities: The quality affirmation can be checked by playing out a few
tests like discovery testing comes about, UX testing, and execution testing.
A set of validation activities: The quality affirmation can be confirmed by playing out a few
activities like Identification of the Quality Issues, Development of Quality Management Plan,
and Implementation of the Quality Management Plan
6. Part Six: Closure and Evaluation

10ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
Annotated Bibliography: As characterized by Kendrick (2015), the undertaking comprises
of various dangers and dangers. The examination of the different variables of hazard would
have a tendency to enhanced the advancement of the venture administration ideas would be
useful for the improvement of the hazard evaluation for the undertaking. The basic
examination of the task advance would tend to utilize the administration of operations for the
venture. Braglia and Frosolini (2014) have sent the utilization of the venture joining and its
pertinence with the administration of the undertaking for data framework improvement. The
advancement of the venture for the execution of the data framework would contain the
administration of the operations and its arrangement with the framework improvement. The
investigation of the article by Stark (2015), would help in building up some arrangement for
the change of the operations and creating successful correspondence for the operations of the
venture. The examination of the diverse factors of risk would tend to upgraded the headway
of the endeavour organization thoughts would be valuable for the change of the danger
evaluation for the undertaking. The essential examination of the venture progress would have
a tendency to use the organization of operations for the assignment.
Checklist for the project

11ITC505 ASSIGNMENT 3PROJECT MANAGEMENT
Evaluation Criteria
i. Successful finishing the task in assessed time
ii. Following the task spending plan and asset
iii. Meeting the extents of the task