VIT Project Management: Online Ticketing System for Riverina Show
VerifiedAdded on 2023/06/03
|21
|2464
|355
Report
AI Summary
This report presents a comprehensive project management plan for the development of an online ticketing system for the Riverina Agriculture and Lifestyle Show (RALS). The project aims to replace the existing manual ticketing process with an online system to improve efficiency and reduce errors. The report includes an executive summary, project plan, detailing the scope, functional and non-functional requirements, work breakdown structure, time and cost estimations, and resource allocation. It covers quality assurance, stakeholder analysis, a communication plan, and a detailed risk management plan with assessment and mitigation strategies. The deployment plan outlines the phased rollout of the system, followed by a project sign-off and conclusion, along with post-project review and recommendations. The report follows PMBoK principles and offers insights for future projects.

Assignment title
Assignment title
Student name
Student number
Lecturer details
Assignment title
Student name
Student number
Lecturer details
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Executive summary
Globex organization aims a developing an online ticketing system for Riverina Agriculture and
Lifestyle Show. The current system faces considerable number of issues due to manual processing of
managing tickets. Along with this, manual system makes it difficult for the exhibitors to manage
ticket booking. In order to avoid human mistakes, Globex decided to develop an online system for
booking tickets for the show. The report provides a project management plan for planning,
executing and monitoring the project. PMBoK principles hall be applied to successfully complete the
project. Also, the report presents the recommendations for future developments in the similar
projects.
1
Globex organization aims a developing an online ticketing system for Riverina Agriculture and
Lifestyle Show. The current system faces considerable number of issues due to manual processing of
managing tickets. Along with this, manual system makes it difficult for the exhibitors to manage
ticket booking. In order to avoid human mistakes, Globex decided to develop an online system for
booking tickets for the show. The report provides a project management plan for planning,
executing and monitoring the project. PMBoK principles hall be applied to successfully complete the
project. Also, the report presents the recommendations for future developments in the similar
projects.
1

Table of Contents
Title.......................................................................................................................................................3
Start date...............................................................................................................................................3
End date................................................................................................................................................3
Goals and objectives..............................................................................................................................3
Project plan...........................................................................................................................................3
Project scope.....................................................................................................................................3
Constraints........................................................................................................................................4
Functional requirements...................................................................................................................4
Non-functional requirements............................................................................................................4
Work Breakdown Structure...............................................................................................................5
Time estimation................................................................................................................................6
Project resources..............................................................................................................................7
Gantt chart........................................................................................................................................7
Network diagram..............................................................................................................................8
Cost estimation...............................................................................................................................10
Quality plan.....................................................................................................................................11
Stakeholder analysis........................................................................................................................12
Communication plan.......................................................................................................................14
Risk management plan....................................................................................................................15
Risk assessment..........................................................................................................................15
Risk Mitigation............................................................................................................................16
Deployment plan.............................................................................................................................17
Project sign off.....................................................................................................................................17
Conclusion...........................................................................................................................................18
Post project review and recommendations.......................................................................................18
References...........................................................................................................................................20
2
Title.......................................................................................................................................................3
Start date...............................................................................................................................................3
End date................................................................................................................................................3
Goals and objectives..............................................................................................................................3
Project plan...........................................................................................................................................3
Project scope.....................................................................................................................................3
Constraints........................................................................................................................................4
Functional requirements...................................................................................................................4
Non-functional requirements............................................................................................................4
Work Breakdown Structure...............................................................................................................5
Time estimation................................................................................................................................6
Project resources..............................................................................................................................7
Gantt chart........................................................................................................................................7
Network diagram..............................................................................................................................8
Cost estimation...............................................................................................................................10
Quality plan.....................................................................................................................................11
Stakeholder analysis........................................................................................................................12
Communication plan.......................................................................................................................14
Risk management plan....................................................................................................................15
Risk assessment..........................................................................................................................15
Risk Mitigation............................................................................................................................16
Deployment plan.............................................................................................................................17
Project sign off.....................................................................................................................................17
Conclusion...........................................................................................................................................18
Post project review and recommendations.......................................................................................18
References...........................................................................................................................................20
2
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

Title
Ticketing System for Riverina Agriculture and Lifestyle Show (RALS)
Start date
1st November 2018
End date
29th January 2019
Goals and objectives
Following are key goals and objectives of proposed online ticketing system of RALS:
The exhibitors will be able to book exhibition sites through online medium.
The facility will be able to book tickets through mobile phone also.
The proposed online system will be able to allow end users to reduce manual mistakes in
RALS work.
The online system ticket and entry passes have a barcode to conduct verification and
validation of exhibition sites.
Project plan
Project scope
In Scope Includes
System Functions Ability to allow RALS users to manage tickets online i.e.
users will be able crate a booking, cancel a booking and
update booking through online system.
Ability to demonstrate system qualities such as
usability, reliability, scalability and availability.
Ability to ensure that only authorized users are allowed
to access the online site to make any changes in the
system such as booking tickets, etc.
System Documentation Project charter
Security plan report
User manual
Implementation plan
Closure reports
Training Staff shall be provided training to understand the
3
Ticketing System for Riverina Agriculture and Lifestyle Show (RALS)
Start date
1st November 2018
End date
29th January 2019
Goals and objectives
Following are key goals and objectives of proposed online ticketing system of RALS:
The exhibitors will be able to book exhibition sites through online medium.
The facility will be able to book tickets through mobile phone also.
The proposed online system will be able to allow end users to reduce manual mistakes in
RALS work.
The online system ticket and entry passes have a barcode to conduct verification and
validation of exhibition sites.
Project plan
Project scope
In Scope Includes
System Functions Ability to allow RALS users to manage tickets online i.e.
users will be able crate a booking, cancel a booking and
update booking through online system.
Ability to demonstrate system qualities such as
usability, reliability, scalability and availability.
Ability to ensure that only authorized users are allowed
to access the online site to make any changes in the
system such as booking tickets, etc.
System Documentation Project charter
Security plan report
User manual
Implementation plan
Closure reports
Training Staff shall be provided training to understand the
3
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

features of new online ticketing system.
End users shall be provided with a guidance “Help”
section for the same.
Constraints
Following are key constraints of the proposed project:
In case, project exceeds the assigned budget, project manager should consult the RALS
management for extra budget.
Resources are required to be available 100% throughout the project. In case as resource is
not available, an immediate replacement shall need to be done.
If project is not able to meet deadline, then project manager should update the sponsor and
get extra resources allocated to the project.
Functional requirements
Following are key functional requirements of the proposed system:
Customer should be able to create online account.
Customer should be able to book, update or cancel a ticket.
Customer should be able to make payment for the booking.
Customer should be able to report any feedbacks about the system.
Management should be able to generate reports.
Non-functional requirements
Following are key non-functional requirements of the proposed system:
System should be 24x7 available.
System should have very low learning curve.
System should prompt users about next likely action during performing an action.
System should allow access only to the authorized users.
4
End users shall be provided with a guidance “Help”
section for the same.
Constraints
Following are key constraints of the proposed project:
In case, project exceeds the assigned budget, project manager should consult the RALS
management for extra budget.
Resources are required to be available 100% throughout the project. In case as resource is
not available, an immediate replacement shall need to be done.
If project is not able to meet deadline, then project manager should update the sponsor and
get extra resources allocated to the project.
Functional requirements
Following are key functional requirements of the proposed system:
Customer should be able to create online account.
Customer should be able to book, update or cancel a ticket.
Customer should be able to make payment for the booking.
Customer should be able to report any feedbacks about the system.
Management should be able to generate reports.
Non-functional requirements
Following are key non-functional requirements of the proposed system:
System should be 24x7 available.
System should have very low learning curve.
System should prompt users about next likely action during performing an action.
System should allow access only to the authorized users.
4

Work Breakdown Structure
5
5
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

(Siami-Irdemoosa, Dindarloo & Sharifzadeh, 2015)
Time estimation
6
Time estimation
6
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Project resources
Gantt chart
7
Gantt chart
7

Network diagram
8
8
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

9
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

Cost estimation
10
10

Quality plan
The quality framework at RALS includes for quadrants: staff and customer access and outcomes,
organizational health, financial health and innovation. The purpose of quality plan includes:
To ensure customer and staff access to the proposed online ticketing system which stands
on expectations of RALS.
To satisfy the objectives of agreed requirements in providing quality platform with
innovative strategies.
To explore best practices in providing service delivery.
Quality plan shall investigate processes and not the people:
Quality improvement must be continuous which should include defining, improving and
measuring quality.
Quality online ticketing system should include effort of both developing team and staff. All
RALS staff is responsible for quality improvement.
Accountabilities of management should be clearly defined for efficient improvement.
Implementation of quality plan
All staff members of every department will have a defined action plan for every project objective.
The action plan will include supporting actions and implementation plan along with the evaluation
plan with defined timeline. The improvement model used for quality plan implementation is Deming
Cycle i.e. “Plan, Do, Study, Act” (PDSA) model (Milunovic & Filipovic, 2013).
11
The quality framework at RALS includes for quadrants: staff and customer access and outcomes,
organizational health, financial health and innovation. The purpose of quality plan includes:
To ensure customer and staff access to the proposed online ticketing system which stands
on expectations of RALS.
To satisfy the objectives of agreed requirements in providing quality platform with
innovative strategies.
To explore best practices in providing service delivery.
Quality plan shall investigate processes and not the people:
Quality improvement must be continuous which should include defining, improving and
measuring quality.
Quality online ticketing system should include effort of both developing team and staff. All
RALS staff is responsible for quality improvement.
Accountabilities of management should be clearly defined for efficient improvement.
Implementation of quality plan
All staff members of every department will have a defined action plan for every project objective.
The action plan will include supporting actions and implementation plan along with the evaluation
plan with defined timeline. The improvement model used for quality plan implementation is Deming
Cycle i.e. “Plan, Do, Study, Act” (PDSA) model (Milunovic & Filipovic, 2013).
11
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 21
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.