Detailed Project Report: RALS Ticketing System for Globex and Virtucon

This report details the RALS Ticketing System project developed by Virtucon for Globex, focusing on the automation of the ticketing process for the Riverina Agriculture and Lifestyle Show (RALS). The project aims to replace the existing manual system with an automated ticketing solution to handle the increasing number of attendees and associated complexities. The report includes a project overview, describing the annual event and the issues with the current ticketing process. It outlines the project team, including their skills, roles, and responsibilities, along with communication plans, meeting procedures, and team values. The report also covers the technical aspects of the system, such as ticket options (single day, family, etc.) and the use of barcodes or QR codes for tracking. It further details the project's learning cycles, including what is known, what is assumed, and areas of uncertainty. The project's goals are to improve efficiency and provide better service to customers. This document showcases the project's planning, execution, and control phases, including the team's commitment to professional conduct and ethical standards.

qwertyuiopasdfghjklzxcvbnmqw
ertyuiopasdfghjklzxcvbnmqwert
yuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopa
sdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklz
xcvbnmqwertyuiopasdfghjklzxcv
bnmqwertyuiopasdfghjklzxcvbn
mqwertyuiopasdfghjklzxcvbnmq
wertyuiopasdfghjklzxcvbnmqwer
tyuiopasdfghjklzxcvbnmqwertyui
opasdfghjklzxcvbnmqwertyuiopa
sdfghjklzxcvbnmqwertyuiopasdf
ghjklzxcvbnmqwertyuiopasdfghj
klzxcvbnmqwertyuiopasdfghjklz
xcvbnmrtyuiopasdfghjklzxcvbnm
Riverina Agriculture and Lifecycle Show (RALS)
Project Report
8/29/2017

RALS Ticketing System
Team Member Details
Team Member Name Contact Details Signature
Abdul Mutallib Mohammed Unit 8/55 ,Dartbrook road,
Auburn,2144
Mayank Unit 56, railway terrace
granville. 2142
Venkat Nishanth Mummareddy 9/43 the trongate road granville
2

RALS Ticketing System
Table of Contents
Introduction.................................................................................................................................................4
Project Name...............................................................................................................................................4
Project Team...............................................................................................................................................4
Project Overview.........................................................................................................................................5
Project Description......................................................................................................................................5
Team Charter...............................................................................................................................................5
Skills, Knowledge Inventory, Roles and Responsibilities........................................................................5
Team Communications............................................................................................................................7
Meeting Times and Locations..............................................................................................................7
Meeting Procedures.............................................................................................................................7
Information Sharing.............................................................................................................................7
Team Rules and Expectations..............................................................................................................8
Team Values........................................................................................................................................8
Code of Conduct..................................................................................................................................8
Rules and Expectations........................................................................................................................8
Learning Cycles...........................................................................................................................................9
Organizer.................................................................................................................................................9
Scribe.......................................................................................................................................................9
Team Learning Record............................................................................................................................9
Communication Plan.................................................................................................................................10
Reflection..................................................................................................................................................14
Conclusion.................................................................................................................................................15
References.................................................................................................................................................16
3

RALS Ticketing System
Introduction
Riverina Agriculture and Lifestyle Show (RALS) is an annual show that was started in the year
2000 by B T & Sons Farming Equipment. The establishment took place before the setting up of
Globex. The event is being carried out annually and has witnessed a massive growth since its
year of inception. Currently, there are manual processes that are followed in the ticket selling
process that is involved with RALS. However, with the expansion of the number of attendees
and the increase in the requirements associated with the show, it has been proposed that an
automated ticketing system is followed in RALS. Globex has contacted Virtucon to develop the
desired system in order to fulfil the requirements and specifications. The automated ticketing
system will comprise of the functional, non-functional and user aspects to make sure that the
problems that are currently present are overcome.
Project Name
The name of the project is RALS Ticketing System.
Project Team
RALS Project Team
There will a lot many resources and teams that will be working on the project. The name of the
teams and their contact information has been presented in the table below.
Name of the Team Contact Information
Email Address Phone
Finance Team financeteam @virtucon.com 444-777-8989
Administrative Department [e-mail] 444-777-8989
Design and Development [e-mail] 444-777-8989
Human Resources [e-mail] 444-777-8989
Management [e-mail] 444-777-8989
Sales & Support [e-mail] 444-777-8989
Services & Maintenance [e-mail]
m
444-777-8989
4

RALS Ticketing System
Project Overview
RALS is an annual event that is being carried out every year since 2000. Globex is the
organization that works in the department of event management and is now responsible for the
successful organization of RALS. RALS is an event that benefits a large number of stakeholders
and parties that are associated with it. In the event, the latest technologies that may be used and
applied in the area of farming and agriculture are discussed. Currently, there are a few issues that
have been observed in the ticketing process that is followed in RALS. There are huge number of
attendees for the event and the manual ticketing process results in mismanagement. Therefore, an
automated system for the same has been proposed. Virtucon is an organization that has been
approached by Globex to carry out the project developmental activities for deploying automated
ticketing system at RALS (McKeever, 2006).
Project Description
The automated ticketing system that will be developed for RALS will include various ticket
options. It shall allow the customers to select an option as a single day pass, 2/3 days pass,
family pass, kids pass, student pass, concession pass and stall holder pass. Every pass will have a
validation applied to it to make sure that the customer is eligible to obtain the desired pass. There
shall also be a barcode or a QR code present on every ticket that is generated so that the tracking
of the same can be done. The tickets that the customers purchase shall be printed or generated as
an e-ticket as per the customer preference. The ticketing system must also provide automated
reports on the tickets that are generated over a period of time and likewise.
Team Charter
Skills, Knowledge Inventory, Roles and Responsibilities
Who (Name of the
Team Member)
Skills and Knowledge Does What (Roles and Responsibility) By When
A Accounting skills and
operations
Designing of the budget for the project
with identification of the costs,
benefits and a cost-benefit analysis for
Completion of the
Project Planning
5

RALS Ticketing System
the project. Each of the project activity
shall be assigned a cost.
Phase
B Coding and programming
skills
Development of the front end of the
ticketing system in terms of the codes
that will be required for each of the
functionalities
By the end of the
project execution
phase
C Human Resource Management Selection of the team members and
allocation of the roles and
responsibilities to the team. The
conduction of training sessions for the
resources
Completion of the
Project Planning
Phase
D User Interface (UI) skills Designing of the ticketing system in
terms of the UI elements and their
placement on each of the pages.
Layout and navigation shall be set up
by the resource
By the end of the
project execution
phase
E Application and System
Testing
Testing of the ticketing system by
covering system testing, integration
testing, regression testing,
performance and security test along
with the application testing. The
defects that are identified shall also be
reported.
During the project
implementation
and control phase
F Coordination of the sales
activities
Tracking of the tickets that are sold
and providing the development and
maintenance team with a sales data on
regular intervals
During the project
control and
closure phases
G Support and maintenance Incident recording and resolution to
make sure that the customer queries
Project control
6

RALS Ticketing System
and complaints are resolved phase
H Database management and
operations
Setting up of the database for the
ticketing system to record all the
information of the system and
execution of the data related
operations
By the end of the
project execution
phase
I Leadership and administrative
skills
Assistance to the Project Manager to
manage the respective teams and
resources and making sure that the
project deliverables are successfully
met.
Throughout the
project until the
closure report is
submitted
J Project Management skills and
knowledge
Planning of the project and the project
resources, communication with the
project client, resolution of conflicts
and disputes and project closure
activities.
Throughout the
project until the
closure report is
submitted
Team Communications
Meeting Times and Locations
Team meeting will be held internally to discuss the project status and details of the project in
terms of the activities that shall be completed and the approach that shall be followed. The time
of the meeting will be at 9:00 am every day. The meetings will be organized in the meeting
rooms that are set up in the company. There will be certain resources working remotely and they
will be asked to join the meeting with the aid of a tele-conferencing medium. A web-based
application will be used for the same.
7

RALS Ticketing System
Meeting Procedures
The facilitator of the meeting will be the Project Manager. All of the team members will be
provided with the meeting schedule along with the agenda of the meeting. The team member will
be required to acknowledge the invitation that will be sent by the Project Manager.
The meeting will be initiated with a presentation by the Project Leader on the current status of
the project which will be followed by discussion on the activities planned for the day and the
areas that may be improved. Meeting notes will be prepared and circulated among all the
meeting attendees at the end of the meeting.
There will also be a slot reserved for the discussion on the project conflicts and issues along with
the questions and answers as well.
Information Sharing
The team will share the information regarding the meeting and the project using the SharePoint
location. The project related documents will be uploaded on the SharePoint and will be
accessible to the team members.
There will also be email and instant messaging options provided to the team members for
internal communication.
Team Rules and Expectations
 The team members must acknowledge the invitation for the meeting that is circulated by
the Project Manager.
 In case of the inability to attend the meeting, a denial of the invitation shall be sent with
the reason specified for the same.
 The mobile phones shall be kept on the silent mode during the meeting.
 The team members must showcase an active participation during the meeting and must
come up with the ideas and contribution towards the project.
 The privacy of the information shall be maintained by one and all.
Team Values
Team members that will be working on the RALS ticketing system must work together as a team
with the values as team cohesion and team collaboration.
8

RALS Ticketing System
There shall also be transparency maintained among the team members in terms of the project
related activities.
Code of Conduct
The code of conduct that shall be followed by the team members must focus upon the
professional code of conduct along with the ethical values.
The team members must showcase honesty and competence in all of their project related
activities. The interest of the customer and the team shall be kept on priority and the selfish
interests shall be kept aside. The team shall work together to make sure that professional
development of self and the team is attained.
There will be a lot of information that will be associated in the project which shall be kept
private and the confidentiality of the information shall be maintained.
Rules and Expectations
 The time of the meeting shall be at 9:00 am every day. The meetings shall be organized
in the meeting rooms that are set up in the company.
 The team members must showcase an active participation during the meeting and must
come up with the ideas and contribution towards the project.
 The interest of the customer and the team shall be kept on priority and the selfish interests
shall be kept aside.
 The team shall work together to make sure that professional development of self and the
team is attained.
 The properties of the project information such as information confidentiality, integrity,
privacy and availability shall be maintained.
Learning Cycles
Organizer
 The meeting invitation shall be sent to all of the team members as a recurring event
 The organizer must also circulate the agenda for the meeting every day to make sure that
the points that are to be covered are known to all in advance.
 The organizer must make sure that the outstanding issues are resolved in the meeting.
9

RALS Ticketing System
 The organizer must make sure that the disputes associated with the project are resolved in
the meeting.
 The organizer must make sure that the conflicts associated with the project are resolved
in the meeting.
Scribe
 The scribe must adhere to the rules and guidelines that are defined for the project and the
meetings.
 The code of conduct shall be followed and maintained during the meeting.
 There shall be active participation showcased in every meeting.
 The meeting notes shall be prepared and sent by the team members in a round robin
process.
Team Learning Record
What we Know What we think we Know What we don’t know
Project schedule and budget Estimation is done correctly Associated budget and
schedule risks
Project Specifications and
functional requirements
There will be no changes in
the project requirements
Scope inflation and
requirements risks
Non-functional requirements
and system qualities
Functional requirements shall
be completed first followed by
non-functional requirements
Functional and non-functional
requirements are equally
important
Code of Conduct The ethical and professional
codes of conduct that shall be
followed in all the project
activities
The repercussions that may
result if there is a violation of
these codes and standards
Communication Guidelines Meeting schedule and
guidelines along with the rules
and expectations associated
with the communication
process
Expectations of the customer
in terms of the communication
process that shall be followed
RALS ticketing process – the There will be ticket options There may be changes or
10

RALS Ticketing System
types of tickets to be put in the
system
that shall be installed in the
system for the users on the
basis of individual, family,
kids, students and likewise.
additions in terms of the ticket
options and requirements to be
put in to the system.
Change Management Plan and
Change Requests
There may be changes in the
project in terms of the change
requirements that will be
required to be managed by the
change process and guidelines
The change requests that are
approved by the client will
only be handled and managed.
Communication Plan
Stakeholder Information to
be Shared
Frequency
of
Information
Exchange
Location of
Information
Exchange
Purpose of
Communication
Mechanism for
Communication
Project
Sponsor
Final Release,
Project Status
Report
Go-live,
weekly
SharePoint
location set
up for the
project
Project
progress
Upload on
SharePoint and
an email
notification to
be sent to the
stakeholder
Program
Manager
Final Release,
Project Status
Report
Go-live,
weekly
SharePoint
set up for the
project
Project
progress
Upload on
SharePoint and
an email
notification to
be sent to the
stakeholder
Project
Manager
Project Funds,
Project
Requirements,
Project
Initiation
phase,
SharePoint
set up for the
project
To understand
project
specifications
Upload on
SharePoint and
an email
11

RALS Ticketing System
Project Status
Reports by
team
members
Project
initiation
phase, daily
and progress notification to
be sent to the
stakeholder
Project
Team
Project
Requirements
and Project
Plan
Project
Initiation
phase,
Project
Planning
phase
SharePoint
set up for the
project
To understand
project
specifications
SharePoint and
an email
notification to
be sent to the
stakeholder
Volunteers Final Release Go-live SharePoint
set up for the
project
End-product Social groups
and RALS
website
Customers Final Release Go-live SharePoint
set up for the
project
End-product Social groups
and RALS
website
Project Name: RALS Ticketing System
Team Members. Name of the Team
Member
Skills and Knowledge
A Accounting skills and operations
B Coding and programming skills
C Human Resource Management
D User Interface (UI) skills
E Application and System Testing
F Coordination of the sales activities
G Support and maintenance
12