University Project: Project Management of RALS Ticketing System

This project management assignment details the development of a ticketing system for the Riverina Agriculture and Lifestyle Show (RALS). The assignment covers various aspects of project management, including MOV values, scope management, project scheduling (Gantt chart), risk analysis, quality management, and project closure. The MOV (Measurable Organizational Value) analysis identifies financial, customer, operational, strategic, and social impacts, with customer satisfaction as the top priority. The scope management plan defines the project's scope, requirements, deliverables, and acceptance criteria. The project schedule, presented in a Gantt chart, outlines the timeline for project activities. Risk analysis identifies and ranks potential risks, proposing mitigation strategies. The quality management plan outlines verification and validation activities. The project closure and evaluation section includes an annotated bibliography, a closure checklist, and a project evaluation based on cost-effectiveness and performance. The assignment references key project management concepts and methodologies, such as SDLC and Prince2, and includes a list of resources. The project aims to improve the efficiency and effectiveness of the RALS ticketing process within a specified budget and timeframe.

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

1PROJECT MANAGEMENT
Table of Contents
Part 1: MOV Values........................................................................................................................2
Part 2: Scope Management Plan......................................................................................................4
Part 3: Project Schedule...................................................................................................................5
Part 4: Project Risk Analysis...........................................................................................................7
Part 5: Quality Management Plan....................................................................................................8
Part 6: Project Closure and Evaluation............................................................................................9
Bibliography..................................................................................................................................12

2PROJECT MANAGEMENT
Part 1: MOV Values
Ranking: The project of RALS ticketing system development is made for forming an
appropriate system for making the tickets for the Riverina Agriculture and Lifestyle Show. The
areas of impact for the project are Financial Area, Customer Area, Operational Area, Strategy
Area, and Social Area. These factors for the project are given below,
Factor Description Ran
k
Financial
Area
The financial area is the primary factor for the development of the
project and the investment of the operations would be formed for the
project.
2nd
Customer
Area
The customer dependency for the project is largely impactful and the
management of the system operations. The project is client based and
hence the customer’s requirement gets the highest priority of operations.
1st
Operationa
l Area
The project operational area has been marked for the development and
the alignment of the specific project system development to overcome
the probability of the issues in functions.
3rd
Strategy
Area
The strategic implication of the project operations is largely formed for
developing the supportive and improved functional analysis of the
project.
4th
Social Area The social area forms the lesser impact on the project as the project 5th

3PROJECT MANAGEMENT
involves development of the ticketing system for the show.
a. Better- The operations of the Riverina Agriculture and Lifestyle Show would be improved
with the alignment of the ticketing system with the database as the process would be machine
dependent
b. Faster- The operations of the Riverina Agriculture and Lifestyle Show would become faster as
the time taken for the process would be decreased with the implication of the system for RALS
c. Cheaper- Due to decrease in the time taken for the operations of the Riverina Agriculture and
Lifestyle Show, the operations would be cheaper in compare to the time effectiveness
d. Do more- The ticketing system for Riverina Agriculture and Lifestyle Show would also serve
the purpose of information integration and the development of the communication process
Appropriate Metric with timeframe:
Factor Customer Strategy Financial Operational Social
Metrics Feedback and
Suggestions
Strategic
Analysis
Matrix
NPV, Revenue, and
Profit Calculation
Management
Plan
Social
Sites
Timeframe
(in
months)
4 3 3 2 2

4PROJECT MANAGEMENT
MOV statement: The acquisition of the project is formed for the time efficient and improved
functions for the analysis of the project development for the Riverina Agriculture and Lifestyle
Show
Part 2: Scope Management Plan
Define the scope: the project scope for the formation of an improved system for generating
tickets for the Riverina Agriculture and Lifestyle Show or RALS. The project plan, system
development, and system design are also a part of the project scope.
Requirements: The project comprises of the development of the ticketing system along with the
integration of the project management principles. The requirements of the project consist of
human resources like Planner, Documenter, Project Manager, Contractor, Engineer, and tester.
The project also requires the materials like computer devices, network components, wireless
cards, LAN wires, and cables.
In scope-out scope items: The project is developed for the development of the ticketing system
for the Riverina Agriculture and Lifestyle Show. The project plan, system development, and
system design are a part of the project in-scope. The communication plan, change management
and transportation plan are out of scope of the project.
Deliverables: The initiation plan, project schedule plan, charter documents, implementation
plan, system design, and the final ticketing system are the deliverables for the project.
Acceptance Criteria: The project is developed for alignment of the effective project
management principles and processes so that the project would be completed in the appropriate
development model. The project acceptance criteria are,

5PROJECT MANAGEMENT
 Completion of the project in 5 months of time
 Meeting the estimated budget for the project of $75000
 Appropriate functioning of the ticketing system for the project
Provide a list of Resources:
Figure 1: List of resources for the project
Part 3: Project Schedule

6PROJECT MANAGEMENT
ID Task
Mode
WBS Task Name Duration Start Finish
0 0 RALS ticketing system
development
125 days Mon 6/4/18 Fri
11/23/18
1 1 Project Initialization 14 days Mon 6/4/18 Thu 6/21/18
2 1.1 Sustainability Analysis 3 days Mon 6/4/18 Wed 6/6/18
3 1.2 Analyzing the Requirements2 days Thu 6/7/18 Fri 6/8/18
4 1.3 Project Charter Documentation4 days Mon 6/11/18 Thu 6/14/18
5 1.4 Project Initiation Documents3 days Fri 6/15/18 Tue 6/19/18
6 1.5 Kick off meetings 1 day Wed 6/20/18 Wed 6/20/18
7 1.6 Submission of documents 1 day Thu 6/21/18 Thu 6/21/18
8 M1 Signing the documents 0 days Thu 6/21/18 Thu 6/21/18
9 2 Project Planning and
Resource Accumulation
25 days Fri 6/22/18 Thu 7/26/18
10 2.1 Selection of planning
methodology
1 day Fri 6/22/18 Fri 6/22/18
11 2.2 Developing plan outline 4 days Mon 6/25/18 Thu 6/28/18
12 2.3 Reviewing the plan 2 days Fri 6/29/18 Mon 7/2/18
13 2.4 Client's requirement analysis3 days Tue 7/3/18 Thu 7/5/18
14 2.5 Team members are selected6 days Fri 7/6/18 Fri 7/13/18
15 2.6 Budget development 2 days Mon 7/16/18 Tue 7/17/18
16 2.7 Resources are accumulated7 days Wed 7/18/18 Thu 7/26/18
17 M2 Project Plan is approved 0 days Thu 7/26/18 Thu 7/26/18
18 3 System Development and Testing80 days Fri 7/27/18 Thu 11/15/18
19 3.1 Designing the system 23 days Fri 7/27/18 Tue 8/28/18
20 3.1.1 Selecting design platform3 days Fri 7/27/18 Tue 7/31/18
21 3.1.2 Making appropriate design10 days Wed 8/1/18 Tue 8/14/18
22 3.1.3 Reviewing the design 3 days Wed 8/15/18 Fri 8/17/18
23 3.1.4 Prototyping the design 4 days Mon 8/20/18 Thu 8/23/18
24 3.1.5 Design Simulation 3 days Fri 8/24/18 Tue 8/28/18
25 M3 Design Approval 0 days Tue 8/28/18 Tue 8/28/18
26 3.2 Developing the system 42 days Wed 8/29/18 Thu 10/25/18
27 3.2.1 Storage system is developed10 days Wed 8/29/18 Tue 9/11/18
28 3.2.2 Database is integrated 3 days Wed 9/12/18 Fri 9/14/18
29 3.2.3 User Interface is developed4 days Mon 9/17/18 Thu 9/20/18
30 3.2.4 Programming and
Coding the ticketing
system
10 days Fri 9/21/18 Thu 10/4/18
31 3.2.5 Functions Integration
in the system
5 days Fri 10/5/18 Thu
10/11/18
32 3.2.6 Infrastructure is developed7 days Fri 10/12/18 Mon 10/22/18
33 3.2.7 Hardware components
are deployed
3 days Tue 10/23/18 Thu
10/25/18
34 M3 System is developed
for Globex
0 days Thu 10/25/18 Thu
10/25/18
35 3.3 System Testing 15 days Fri 10/26/18 Thu 11/15/18
36 3.3.1 User Interface is tested3 days Fri 10/26/18 Tue 10/30/18
37 3.3.2 Black box testing 3 days Wed 10/31/18Fri 11/2/18
38 3.3.3 White Box testing 3 days Mon 11/5/18 Wed 11/7/18
39 3.3.4 User experience analysis3 days Thu 11/8/18 Mon 11/12/18
40 3.3.5 Test run and Simulation3 days Tue 11/13/18 Thu 11/15/18
41 M4 Testing Reports are
developed
0 days Thu 11/15/18 Thu
11/15/18
42 4 Final Documentation 6 days Fri 11/16/18 Fri 11/23/18
43 4.1 Project Closure checklist
is formed
2 days Fri 11/16/18 Mon
11/19/18
44 4.2 Final reports are developed3 days Tue 11/20/18 Thu 11/22/18
45 4.3 Submission of documents 2 hrs Fri 11/23/18 Fri 11/23/18
46 4.4 Reviewing the documents 5 hrs Fri 11/23/18 Fri 11/23/18
47 4.5 Signing the documents 1 hr Fri 11/23/18 Fri 11/23/18
48 M5 Project Closed 0 days Fri 11/23/18 Fri 11/23/18
Budgeter
Planner
Documenter
Documenter
Project Manager
Documenter
6/21
Planner
Planner
Planner
Project Manager
Project Manager
Budgeter
Budgeter
7/26
System Analyst
System Analyst
IT Engineer
System Analyst
IT Engineer
8/28
IT Engineer,Storage[1]
IT Engineer
IT Engineer
IT Engineer
System Analyst
Contractor
Computer Devices[1],IT Engineer,Network Compo
10/25
Tester
Tester
Tester
Tester
Tester
11/15
Documenter
Documenter
Documenter
Project Manager
Project Manager
11/23
S T M F T S W S T
Apr 22, '18 Jul 1, '18 Sep 9, '18 Nov 18, '18 Jan 27, '19
Figure 2: Gantt chart showing project schedule

7PROJECT MANAGEMENT
Part 4: Project Risk Analysis
Risk name: Incompatible Design Methodology
Related Project Phase: Design Phase
Risk Owner: Designer
Probability: Likely
Severity: Catastrophic
Potential Response: Implementation of SDLC methodology
Ranking: 1st
Risk name: Inappropriate plan methodology
Related Project Phase: Plan Phase
Risk Owner: Planner
Probability: Possible
Severity: Major
Potential Response: Alignment of Prince 2 Plan development process
Ranking: 2nd
Risk name: Lack of pre-information
Related Project Phase: Initiation Phase
Risk Owner: Analyst
Probability: Likely
Severity: Moderate
Potential Response: Going through various past reports and records of previous completed
project

8PROJECT MANAGEMENT
Ranking: 3rd
Risk name: Poor Quality of raw materials
Related Project Phase: Execution Phase
Risk Owner: Project Manager
Probability: Likely
Severity: Moderate
Potential Response: Quality Management Plan should be implied for the product management
Ranking: 4th
Risk name: Missing final documents
Related Project Phase: Closing Phase
Risk Owner: Documenter
Probability: Unlikely
Severity: Moderate
Potential Response: Appropriate final documentation should be used for the project
Ranking: 5th
Part 5: Quality Management Plan
The quality management plan is implied for the development of the improved operations in the
system development. The quality management for the RALS ticketing system development
project is given below,
Development of Verification Activities: The user interface, white box, and black box testing is
implied for the project verification and operations.

9PROJECT MANAGEMENT
Development of Validation Activities: The issue management, quality management, and
implementation management is implied for the validation of the project.
Part 6: Project Closure and Evaluation
Annotated Bibliography: According to Kerzner (2017), the project management is very
important for the management of the project operations and ensuring that the project is
completed successfully. The alignment of the project activities would form the management of
the operations by the help of project scheduling, budgeting, and analysis for ensuring that the
project is completed in the estimated time duration. The project management tools of scheduling
like Calender, Gantt chart, and Rational Plan would help in forming a project schedule
compatible for the achievement of the final project outcome. The scheduling is followed by
resource allocation for forming the complete analysis of the project integration management.
Ruehl and Ingenhoff (2015), have pointed out that communication management plan forms a
sequential flow of information in the project so that the activities of the project can be completed
successfully. The development of the communication management plan would help in
integrating the formation of the supportive and improved project analysis model. The use of
communication means like reports, emails, conference, and board meetings are helpful for
overcoming the probability of the occurrence of the project communication. The effective
communication plan would help in transmitting the information so that the project team can
develop effective operations for the project. Some scholars like McNeil, Frey and Embrechts
(2015), have pointed that risk management is very helpful for securing the expected outcome
from the project. The project of integrated management would help the system development of
the alignment. The examination of the risk factors would help the organization in forming the
functional budget. The improved risk management is aligned for the transformation and the

10PROJECT MANAGEMENT
effective system integration. The risk analysis can be formed with the help of the development
model for the project. The use of risk priority matrix is helpful for the classification of the risk
development factor. The induction of the project management is helpful for forming the
appropriate analysis of the project integration management.
Closure Checklist: The system development projects are largely technology dependent and the
alignment of the improved project development. The general closure checklist for the project is
given below,
Figure 3: Project Closure Checklist
Project Evaluation: The project evaluation for RALS ticketing system development project is
implied for effective and improved system development. The project evaluation can be based on
the cost effectiveness and performance. The cost effectiveness is the first aspect of the project

11PROJECT MANAGEMENT
evaluation method. The project has been set for a budget of $ 75000 and the project manager is
bound to ensure effective project is completed. The performance is another factor that would
have an impact on the development of the project. The performance factor for the project is
aligned with the success completion of the project.