Development of Web-Based Interface for RALS Online Booking System

This project management report details the development of a web-based interface for online bookings for the Riverina Agriculture Lifestyle Show (RALS). The project encompasses various stages, including initiation, planning, execution, control, and closure. The report outlines the project's MOV (Measurable Organizational Value), scope, schedule, and WBS (Work Breakdown Structure). It also includes a risk analysis plan, a quality management plan based on TQM (Total Quality Management), and a closure and evaluation section. The project aims to enhance the user experience and streamline the ticket booking process, impacting strategy, customer satisfaction, social trends, financial performance, and operational efficiency. The report covers stakeholder roles, project phases, charter, and a Gantt chart for scheduling. The risk analysis identifies potential challenges and mitigation strategies. The quality management plan emphasizes TQM to maintain standards. The closure checklist confirms deliverables, quality, and documentation. The evaluation assesses budget and quality, concluding the project's success in meeting its objectives.

PROJECT
MANAGEMENT

TABLE OF CONTENTS
INTRODUCTION......................................................................................................................3
PART 1.......................................................................................................................................3
MOV......................................................................................................................................3
PART 2.......................................................................................................................................5
Scope of the project................................................................................................................5
PART3........................................................................................................................................6
Project schedule and WBS.....................................................................................................6
PART 4.......................................................................................................................................8
Risk analysis and plan............................................................................................................8
PART 5.......................................................................................................................................9
Quality management plan......................................................................................................9
PART 6.....................................................................................................................................10
Closure and evaluation.........................................................................................................10
CONCLUSION........................................................................................................................10
REFERENCES.........................................................................................................................12
APPENDIX..............................................................................................................................14
A1. Detailed Gantt chart......................................................................................................14

INTRODUCTION
The project is a temporary task that is undertaken for accomplishing a special work
with a definite time of start and end. The project management undertakes a number of tasks
within it by breaking down various operations into simple functions so as to accomplish it in
a projected manner (Garel, 2013). The present report is based on accomplishing a project
where it has been proposed to develop a web system which can help in online bookings in
Riverina Agriculture Lifestyle show operations. Thus, the project is undertaken with the
name of ‘installation of a web based interface for online bookings in RALS.’ For this
purpose, a team has been appointed in which members with different specialisation have been
structured. The evaluation of the entire project has been done with the help of a specific
approach as well.
PART 1
MOV
Respective project has been proposed for developing a web based interface which will
help in booking of tickets through online medium. After successful completion of stated
project, it will help in enhancing the user interface as they can take help of a better facility for
booking of tickets without facing difficulties of standing in queues (Memon & et.al., 2011).
As per this, some of the areas will be affected which has been mention below:
Strategy: The proposed project demonstrates the use of effective strategy in the development
of an interface which will make booking of tickets easier. RALS will also have a better
system which can be handled in easier way.
Customer: The major impact will be on customers who will be benefitted with this system
development. The usage of internet is high among people who will be utilised in such a
facility for booking tickets (Hanisch & Wald, 2011).
Social: The trends are ever changing in market according to which companies have to
manage their strategies. The present project has resourcefully decided to develop the interface
which will help in benefitting the society.
Financial: The said project has the capability to make the performance of RALS better and
faster. Thus, it will help in impacting the financial position positively.

Operational: The proposed project has been imposed to make operations related to booking
of tickets faster and easier so that performance and efficiency of the system can be improved
to generate better facilities (Lee & Yu, 2012).
Types of value
Faster: The present project based on online system will deliver services based on faster
interface.
Better: The stated project will help in improving the facility, thereby increasing the
performance and efficiency of the system (Teller & Kock, 2013).
Acceptance criteria
 The delivery of the project on stipulated time and budget.
 The feasibility of the project as per the usability and its performance will make it
deliverable.
 The duration of the project has been set from 2nd October to 2nd December 2017.
Stakeholder no. Roles Responsibility
1 Client Accepting or rejecting the project
2 Project manager Supervision and management of the
entire project.
3 IT manager Developing the web interface and
similar operations
4 Trainer To provide training for proper
functioning related to web system
development
5 Engineer Handling all types of operational
functions.
6 Documenter Creating project charter and arrange for
all types of documents at initial and
ending stage.

PART 2
Scope of the project
The present project has been established for enhancing the web interface for providing
the facility of booking tickets online. Accordingly, the project has been proposed to be
accomplished within four phases of Initiation, Planning, System development and
Documentation of the project (Fortune & et.al., 2011). These phases describe the scope of
project according to which a new system will be designed and developed. The first phase of
the project originates from initiation stage where all types of documents will be arranged,
charter of project will be created and all required documents will be submitted. The planning
phase of the project covers the determination of planning and outlining the plan for
developing the system. The next phase of execution in this project will include development
of designs and developing the system to ensure project functionality. The system
development will include coding and programming of various functions so as to make a
complete system on web for desired purpose. The final phase will consist of documentation
where, closure of project will be done after successful completion and acceptance of project
(Garel, 2013).
Charter
Designation Roles and responsibility
Project manager Managing the project and leading entire team
for execution of various tasks.
Planner Outlining the phases of project and execute entire
project as per the plan.
Documenter Generating all documentation process and
managing it in all stages.
Technical head Handling all operations related to technical field
and solving any breakdowns in system.
System programmer Programming all systems to develop the web
based interface.
System engineer To handle all the operations and functions related
to technical and system development.
All the above stated people will work as a team to accomplish the present project with
the help of various resources like hardware and developed software which cam aid in
inception of a new interface for online booking of tickets. Besides this, some of the team

members may need a training and direction for accomplishing the allotted task (Memon &
et.al., 2011). The efforts made by team with cooperation and utilising all the resource will
help in completing the project on determined time.
PART3
Project schedule and WBS
WBS Task Name Duration Start Finish Predecessors Resource Names
1 Web based interface to
initiate online booking 90 days Mon
10/2/17 Fri 2/2/18
1.1 Initiating the project 19 days Mon
10/2/17
Thu
10/26/17
1.1.1 Conducting research 5 days Mon
10/2/17 Fri 10/6/17 Planner ,Projec
t manager
1.1.2 Drafting project scope 4 days Mon
10/9/17
Thu
10/12/17 3 Project
manager
1.1.3 Initiating documentation 3 days Fri
10/13/17
Tue
10/17/17 4,3 Documenter
1.1.4 Project charter 4 days Wed
10/18/17
Mon
10/23/17 5 Planner
1.1.5 Structuring planning 3 days Tue
10/24/17
Thu
10/26/17 6 Planner
1.2 Planning phase 25 days Fri
10/27/17
Thu
11/30/17
1.2.1 Methodology planning 4 days Fri
10/27/17
Wed
11/1/17 7 Planner
1.2.2 Developing planning
outline 3 days Thu
11/2/17
Mon
11/6/17 9,6 Planner
1.2.3 Developing design 5 days Tue
11/7/17
Mon
11/13/17 10 System
engineer
1.2.4 Web development plan 3 days Tue
11/14/17
Thu
11/16/17 11 System
engineer
1.2.5 System evaluation 4 days Fri
11/17/17
Wed
11/22/17 12,11 Technical head
1.2.6 Plan approval 3 days Thu
11/23/17
Mon
11/27/17 13 Project
manager
1.2.7 Communication planning 3 days Tue
11/28/17
Thu
11/30/17 14 Planner
1.3 Execution phase 20 days Fri 12/1/17 Thu
12/28/17
1.3.1 Software development 5 days Fri 12/1/17 Thu
12/7/17 15 System
engineer
1.3.2 Initiating coding 4 days Fri 12/8/17 Wed
12/13/17 17 Technical head
1.3.3 Debugging 5 days Thu
12/14/17
Wed
12/20/17 18 Technical head
1.3.4 Restructuring design plan 3 days Thu
12/21/17
Mon
12/25/17
19 System
engineer ,Tech

nical head
1.3.5 Finalizing interface 3 days Tue
12/26/17
Thu
12/28/17 20 System
engineer
1.4 Control phase 20 days Fri
12/29/17
Thu
1/25/18
1.4.1 Developing network
connection 5 days Fri
12/29/17 Thu 1/4/18 21 System
engineer
1.4.2 System testing 7 days Fri 1/5/18 Mon
1/15/18 23 System
engineer
1.4.3 Functionality testing 3 days Tue
1/16/18
Thu
1/18/18 24 System
programmer
1.4.4 Finalizing interface 5 days Fri 1/19/18 Thu
1/25/18 25,24 System
engineer
1.5 Project closure 6 days Fri 1/26/18 Fri 2/2/18
1.5.1 Drafting final documents 3 days Fri 1/26/18 Tue
1/30/18 26 Documenter
1.5.2 Signing off 3 days Wed
1/31/18 Fri 2/2/18 28 Project
manager
Gantt chart

PART 4
Risk analysis and plan
The risk analysis plan will be as follows:
Risk description Cause
Internal
/
Externa
l
Positive/
Negative Likelihood Impact
Inadequate
resources to assign
all the team
members for
execution of tasks.
Inability to plan
for arranging
resources and
making forecast
about required
resources.
External Negative Low
Inadequate
resources
arrangement
can make
difficulties in
allotment of
tasks and
responsibilitie
s leading to
delay in work
progress.
Ineffective
arrangement of
technical support
which may impact
system
development
negatively.
Inability in
appointing the
technical
support team
who can handle
the system
development
requirements
(Hanisch &
Wald, 2011).
Internal Negative Moderate
Project
delivery can
be delayed
and objective
to install web
interface may
get failed.
Improper
designing which
does not support
the system
development as
The
engineering and
designing work
may not be
efficient
Internal Negative Low The project
may get
rejected as it
may not serve
the purpose as

per the plan
leading to
improper
design
determined.
Conflicts among
team members
result into
execution of work
in improper
manner.
The team
members do not
cooperate each
other and share
resources
Internal Negative High
This will
make delay in
project
delivery and
completion of
project may
not match the
expectation
(Lee & Yu,
2012).
Inadequate
customer support
to the new system
in market
The increased
competition and
advancement in
techniques may
impact the
proposed
project success
(Teller & Kock,
2013).
External Negative High
The project
may get failed
or become
obsolete as
compared to
other
advancements
of market.
The conflicts among team members are very common as each person belongs to
different background and has different way of thinking. Therefore, the project manager is
responsible for supervising and directing the team members so that less number of conflicting
situations can be raised. Besides this, the cooperation and sharing of resources can be
encouraged by manager.
PART 5
Quality management plan
For managing the quality within the proposed project of installing a web interface for
online booking of tickets in RALS, a specific approach is essential to be applied for having
control on quality standards (Fortune & et.al., 2011). This purpose can be fulfilled by

adopting TQM or Total Quality management approach. This is very helpful way to maintain
quality of project as it manages entire system and its branches under supervision. This
approach favours in making a standard criteria of performance for each task. As per this, the
actual task is compared so that deviation can be identified easily. On this basis, a control can
be maintained on quality of each performance and corrective actions can be taken to
eliminate deviations. The major requirement of this approach is in planning phase and in
application of tools and techniques. The planning can be done in effective way by setting
standard of achievement. Besides this, the application of tools and techniques can be analysed
in each stage to maintain its performance quality (Hanisch & Wald, 2011).
PART 6
Closure and evaluation
The closure checklist has been mentioned below:
Deliverables Description check Notes
Web interface
development
Developed new web based
system of online booking in
RALS to enhance efficiency
and experience of customers.
Check Delivered the developed
system to client
Quality The developed system is based on
high standard and quality which
will service clients in efficient
way
Check The new interface is tested and
outcomes match the standard
criteria.
Documentation The documents have been
submitted and all payments are
required to be made to all
concerned parties.
Check All documents are proper and
submitted to the relevant party
after payments.
Evaluation
Budget: The present project meets the requirements of the RALS and its customers without
diverting from the set budget. Thus, project manager made a good contribution in execution
of new web interface (Garel, 2013).

Quality: The testing of new system is done which demonstrate that performance of interface
matches to the standard criteria set for each task. Thus, the quality of project is high and
meets the standard.
CONCLUSION
The present project is developed to install a web based interface that can help in
booking of online tickets in RALS. As per this, the MOV of the project has been set which
can help in valuing the project scope. The team has been managed and assigned their
respective tasks to ensure a proper execution of project. The risk register has been developed
to anticipate various risks that can impact project progress negatively. Besides this, the
quality of project has been maintained as per the TQM approach which has given the
satisfying results.

REFERENCES
Books and Journals
Fortune, J. (2011). Looking again at current practice in project management. International
Journal of Managing Projects in Business, 4(4), 553-572.
Garel, G. (2013). A history of project management models: From pre-models to the standard
models. International Journal of Project Management, 31(5), 663-669.
Hanisch, B., & Wald, A. (2011). A project management research framework integrating
multiple theoretical perspectives and influencing factors. Project Management
Journal, 42(3), 4-22.
Lee, S. K., & Yu, J. H. (2012). Success model of project management information system in
construction. Automation in construction, 25, 82-93.
Memon, A. H. (2011). Factors affecting construction cost in Mara large construction project:
perspective of project management consultant. International Journal of Sustainable
Construction Engineering and Technology, 1(2), 41-54.
Teller, J., & Kock, A. (2013). An empirical investigation on how portfolio risk management
influences project portfolio success. International Journal of Project Management,
31(6), 817-829.