Project Evaluation and Online Booking System

This assignment delves into the evaluation of a project involving the implementation of an online booking system for RAILS. The focus is on understanding the criteria used to assess project success, including meeting prerequisites, execution timelines, and achievement of established goals. The evaluation highlights the positive impact of the system, such as a 50% reduction in queues at ticket gates due to increased online ticket purchasing. The assignment utilizes various resources and frameworks related to project management for analysis.

Running head: PROJECT MANAGEMENT
Topic-Development of RAILS Rostering System
Name of the Student
Name of the University
Author’s Note

1
PROJECT MANAGEMENT
Table of Contents
Overview of the project...................................................................................................................2
1. Measurable organizational value.................................................................................................2
2. Scope management plan..............................................................................................................5
3. Project schedule and WBS...........................................................................................................6
3.1 Project schedule.....................................................................................................................6
3.2 WBS.....................................................................................................................................13
3.3 Milestone.............................................................................................................................13
4. Project risk analysis and plan....................................................................................................14
4.1 Assumptions........................................................................................................................14
4.2 Risk assessment.....................................................................................................................0
5. Quality management plan............................................................................................................0
5.1 Philosophy for delivering quality system..............................................................................0
5.2 Quality issues.........................................................................................................................0
6. Annotated bibliography and closure checklist.............................................................................2
6.1 Annotated Bibliography.........................................................................................................2
6.2 Closure checklist....................................................................................................................3
6.3 Evaluation plan......................................................................................................................5
Bibliography....................................................................................................................................6

2
PROJECT MANAGEMENT

3
PROJECT MANAGEMENT
Overview of the project
The paper reflects on the organization “Riverina Agricultural and Lifestyle show” which
is one of the events that are mainly held in the month of November for three days. It is found that
the show mainly involves in showcasing local business, farmers, agricultural equipment as well
as lifestyle products. Due to the expansion of the show in different areas the organization found
number of difficulties in managing the various operations of the show. As the show is mainly
managed with the help of the volunteers, the organization wants to develop a system that will be
helpful in tracking as well as managing the activities that are mainly undertaken by the
volunteers. The development of rostering system within the show is found to be very much
advantageous.
In this report, importance of measurable organizational value is mainly highlighted in
various fields. The paper elaborates project scope, schedule as well as project quality. It is
identified that the paper also illustrates the risks that are associated with thre project and helps in
providing proper risk mitigation strategies that are quite helpful in resolving as well as mitigating
the project risks.
1. Measurable organizational value
The measurable organizational value mainly helps in highlighting the impact areas of
RAILS rostering project. The various areas of impact that are mainly highlighted include
customer, financial, operational, strategy as well as social. It is identified that the system of
online ticketing mainly helps in analyzing the factors that are provided below:

4
PROJECT MANAGEMENT
Rank Factor Description Time frame
1st Financial The money that the
organization mainly
invested within the
project helps in
providing proper
financial outcome.
2 months
2nd Customer It is identified that
the customer’s
influence is quite
important for
continuing with the
operation of the
project. The RAILs
project development
influences customers
due to its various
functionalities that
manage the
organizational
operations effectively.
1 month
3rd Strategy The strategic
development of the
2 months

5
PROJECT MANAGEMENT
system generally
includes development
of proper integration
within the system.
4th Operational The various
operations of the
organization can be
properly managed due
to the development of
proper rostering
system. It is identified
that the system helps
in speeding the
various organizational
processes.
3 months
5th Social It is identified that
social support for the
rostering system of
RAILS is quite
necessary in order to
develop proper
processing of the
organizational
2 months

6
PROJECT MANAGEMENT
operation. In addition
to this, it is found that
social support assists
in providing proper
channel of
communication.
2. Scope management plan
The detailed scope management plan is elaborated below:
Requirements: The online ticketing system is mainly needed within the show of RAILS
for handling is well as managing the various volunteers of the organization so that the various
functions as well as operations of the organization can be managed properly. It is identified that
the online ticketing system not only helps in resolving all the issues of the manual system of
operation of the organization but also assist in speeding the entire operation of the show.
Project scope: The scope of the project is mainly divided into project in-scope as well as
project out-scope.
The in-scope of the project is illustrated below:
 To develop system of rostering various managing the volunteers of the show
 Proper documentation which includes information about various functional as well as
non-functional project needs is generally created.
 Various types of professional as well as personal details of the volunteers are added
within the system in order to track the volunteers whenever needed.

7
PROJECT MANAGEMENT
Out-scope of the project mainly include the following:
 Security associated information is not provided
 Training facility is not provided
Deliverable of project: The project deliverables mainly include the following:
 Developing documents for development phase of the system
 Creating documents for specifying the project requirements
 Developing proper planning as well as system testing
 Development of proper procedure for verifying the entire project scope
Project verification procedure: The verification procedure of the project is mainly
highlighted with the help of project acceptance criteria. It is elaborated by the project acceptance
criteria that different demands as well as requirements of the project will be generally fulfilled. It
also helps in illustrating that the developed rostering system for RAILS is quite advantageous as
it assist in reducing various types of issues that the people faces earlier. Thus it is found that the
developed system of rostering for RAILS is quite beneficial for the customers as well as for the
show of RAIL.
3. Project schedule and WBS
3.1 Project schedule
Task Name Duration Start Finish
Resource
Names
Development of RAILS project 205 days Mon Fri 7/20/18

8
PROJECT MANAGEMENT
10/9/17
Initiation phase of the project 40 days
Mon
10/9/17
Fri 12/1/17
Project charter preparation 4 days
Mon
10/9/17
Thu
10/12/17
Project manager
Project scope determination 5 days Fri 10/13/17
Thu
10/19/17
Project manager,
Business
analyst,
Frontend
developer
Gathering of resources 4 days Fri 10/20/17
Wed
10/25/17
Project manager
Analysis of requirement 6 days
Thu
10/26/17
Thu 11/2/17
Lead analyst,
Technical lead
Schedule creation 5 days Fri 11/3/17 Thu 11/9/17 Project manager
Result development 3 days Fri 11/10/17
Tue
11/14/17
Project manager
Application of CPM 4 days
Wed
11/15/17
Mon
11/20/17
Business analyst
Application of cost management
technique
5 days
Tue
11/21/17
Mon
11/27/17
Technical lead
Project performance analysis 4 days Tue Fri 12/1/17 Project manager

9
PROJECT MANAGEMENT
11/28/17
Milestone: Initiation phase
completion
0 days Fri 12/1/17 Fri 12/1/17
Project planning phase 50 days
Mon
12/4/17
Fri 2/9/18
Cost management 6 days
Mon
12/4/17
Mon
12/11/17
Project manager
Project plan for costing 5 days
Tue
12/12/17
Mon
12/18/17
Project manager,
Lead analyst
Project plan development 4 days
Tue
12/19/17
Fri 12/22/17
Frontend
developer
Creating plan for time management 5 days
Mon
12/25/17
Fri 12/29/17 Business analyst
Creating plan for change
management
4 days Mon 1/1/18 Thu 1/4/18 Project manager
Budget estimation 6 days Fri 1/5/18 Fri 1/12/18 Project manager
Cost benefit analysis 4 days
Mon
1/15/18
Thu 1/18/18
Project manager,
Lead analyst
Risk management plan 5 days Fri 1/19/18 Thu 1/25/18 Project manager
Risk treatment plan 5 days Fri 1/26/18 Thu 2/1/18
Frontend
developer, Lead
analyst
Procurement plan 6 days Fri 2/2/18 Fri 2/9/18 Frontend

10
PROJECT MANAGEMENT
developer
Milestone: Project planning
completion
0 days Fri 2/9/18 Fri 2/9/18
Project implementation phase 88 days
Mon
2/12/18
Wed
6/13/18
Development of activity 7 days
Mon
2/12/18
Tue 2/20/18
Business
analyst,
Developers,
Frontend
developer,
Technical lead
Marketing 6 days
Wed
2/21/18
Wed
2/28/18
Frontend
developer
Administration 8 days Thu 3/1/18
Mon
3/12/18
Business analyst
Testing 9 days Tue 3/13/18 Fri 3/23/18 Technical lead
UX and UI design 10 days
Mon
3/26/18
Fri 4/6/18
Business
analyst,
Developers,
Technical lead
Database design 8 days Mon 4/9/18
Wed
4/18/18
Developers
Functionality design 7 days Thu 4/19/18 Fri 4/27/18 Frontend

11
PROJECT MANAGEMENT
developer
System testing 8 days
Mon
4/30/18
Wed 5/9/18 Technical lead
Modification 6 days Thu 5/10/18 Thu 5/17/18
Tester, Business
analyst
Use case testing 9 days Fri 5/18/18
Wed
5/30/18
Tester, Frontend
developer
Quality assessment 10 days Thu 5/31/18
Wed
6/13/18
Tester, Lead
analyst
Milestone: Completion of
implementation phase
0 days
Wed
6/13/18
Wed
6/13/18
Maintenance phase 22 days Thu 6/14/18 Fri 7/13/18
Database maintenance 6 days Thu 6/14/18 Thu 6/21/18 Project manager
Online application maintenance 7 days Fri 6/22/18 Mon 7/2/18
Tester, Business
analyst
Operation maintenance 5 days Tue 7/3/18 Mon 7/9/18
Tester,
Technical lead
Training as well as learning sessions 4 days Tue 7/10/18 Fri 7/13/18
Tester,
Developers
Milestone: Maintenance phase
completion
0 days Fri 7/13/18 Fri 7/13/18
Project closure phase 5 days Mon Fri 7/20/18

12
PROJECT MANAGEMENT
7/16/18
Stakeholders Sign out 1 day
Mon
7/16/18
Mon
7/16/18
Project manager
Post implementation review 2 days Tue 7/17/18
Wed
7/18/18
Business analyst
Contract closure 1 day Thu 7/19/18 Thu 7/19/18 Project manager
Performance appraisal 1 day Fri 7/20/18 Fri 7/20/18 Project manager
Milestone: Completion of closure
phase
0 days Fri 7/20/18 Fri 7/20/18

Running head: PROJECT MANAGEMENT

1
PROJECT MANAGEMENT
Figure 1: Gantt chart
(Source: Created by Author)
Screenshots of Gantt chart

2
PROJECT MANAGEMENT

3
PROJECT MANAGEMENT

Running head: PROJECT MANAGEMENT
3.2 WBS
WBS Task Name
0 Development of RAILS project
1 Initiation phase of the project
1.1 Project charter preparation
1.2 Project scope determination
1.3 Gathering of resources
1.4 Analysis of requirement
1.5 Schedule creation
1.6 Result development
1.7 Application of CPM
1.8 Application of cost management technique
1.9 Project performance analysis
1.10 Milestone: Initiation phase completion
2 Project planning phase
2.1 Cost management
2.2 Project plan for costing
2.3 Project plan development
2.4 Creating plan for time management
2.5 Creating plan for change management
2.6 Budget estimation

1
PROJECT MANAGEMENT
2.7 Cost benefit analysis
2.8 Risk management plan
2.9 Risk treatment plan
2.10 Procurement plan
2.11 Milestone: Project planning completion
3 Project implementation phase
3.1 Development of activity
3.2 Marketing
3.3 Administration
3.4 Testing
3.5 UX and UI design
3.6 Database design
3.7 Functionality design
3.8 System testing
3.9 Modification
3.10 Use case testing
3.11 Quality assessment
3.12 Milestone: Completion of implementation phase
4 Maintenance phase
4.1 Database maintenance
4.2 Online application maintenance
4.3 Operation maintenance

2
PROJECT MANAGEMENT
4.4 Training as well as learning sessions
4.5 Milestone: Maintenance phase completion
5 Project closure phase
5.1 Stakeholders Sign out
5.2 Post implementation review
5.3 Contract closure
5.4 Performance appraisal
5.5 Milestone: Completion of closure phase
Figure 2: WBS
(Source: Created by Author)
3.3 Milestone
Task Name Expected date
Milestone: Initiation phase completion Fri 12/1/17
Milestone: Project planning completion Fri 2/9/18
Milestone: Completion of implementation phase Wed 6/13/18
Milestone: Maintenance phase completion Fri 7/13/18
Milestone: Completion of closure phase Fri 7/20/18

3
PROJECT MANAGEMENT
4. Project risk analysis and plan
4.1 Assumptions
The assumptions that are made in order to develop the rostering system for RAILS rae as
follows:
Resources: It is assumed that the resources that are used in the project will be beneficial
enough to complete the project successfully within time without compromising with the quality
of the project. In addition to this, it is also assumed that the assigned tasks to the project
stakeholders will be completed within time.
Budget: The project manager estimated that the entire activities of the project can be
accomplished within the assumed budget. The budget assumptions are mainly made after
gathering proper information about the needs as well as requirements of the project.
Time: The time that is estimated for executing this project successfully is around 205
days. It is quite important to complete the project within the time limit that is estimated so that
the project managers do not face difficulty associated with project.

Running head: PROJECT MANAGEMENT
4.2 Risk assessment
N
o.
Ra
nk
Risk Descrip
tion
Categ
ory
Root
Cause
Potentia
l
Respons
es
Risk
Owner
Probab
ility
Impa
ct
Statu
s
R
44
1 Imprope
r design
of the
database
If the
database
of the
rostering
system
is not
designed
properly
then the
personal
as well
as
confiden
tial data
that is
stored
within
the
database
can be
Techn
ical
risk
Due to
improper
knowled
ge as
well as
skills of
the
database
administr
ator, the
design of
the
database
is not
done
properly.
It is
quite
importan
t to hire
experien
ced
database
administ
rator so
that the
risks that
are
associate
d with
design
of the
database
can be
resolved
easily.
Databas
e
administ
rator
Low High Can
be set
up in
2
week
s

1
PROJECT MANAGEMENT
accessed
by
anyone
and as
result
security
related
issues
might
occur.
In
addition
to this,
security
related
issues as
well as
challeng
es can
also be
avoided.
R
19
2 Inapprop
riate
training
facility
If
proper
training
facility
is not
provided
to the
team
member
of the
show
then it
will be
quite
Projec
t risk
Insuffici
ent
training
facility is
present
in the
show for
training
the staffs
so that
they can
perform
well in
the
Proper
as well
as
sufficien
t facility
of
training
must be
arranged
by the
show so
that the
team
member
Risk
analyst
Mediu
m
Medi
um
Will
be set
up
prope
rly
withi
n 1
mont
hs.

2
PROJECT MANAGEMENT
difficult
for them
to
perform
well in
the
project.
project in
order to
complete
the entire
project
successf
ully
within
budget
and time.
s of the
project
are
provided
proper
training
facility
and they
can be
able to
complet
e various
tasks as
well as
activities
of the
project
associate
with the
system
develop
ment
quite
easily.
R 3 Imprope If If the It is Financi High Medi Will

3
PROJECT MANAGEMENT
8 r
estimatio
n of
budget
project
estimati
on is not
done
properly
then the
project
manager
faces lot
of
difficult
y in
completi
ng the
project
successf
ully. In
addition
to this,
the
organiza
tion
faces
number
of
financial
Finan
cial
risk
market
analysis
of the
project is
done
properly
and if the
project
manager
s are not
intereste
d in
highlight
ing the
various
needs as
well as
requirem
ents of
the
project
then the
budget
that is
assumed
will not
quite
importan
t to
utilize
earned
value
manage
ment for
estimati
ng the
budget
of the
project
in order
to
predict
proper
budget
for the
project
so that
the
project
do not
face any
financial
al
manager
um be set
up in
two
mont
hs.

4
PROJECT MANAGEMENT
pressure
on the
organiza
tion.
be
accurate.
related
challeng
es while
progress
ing with
the
project.
R
32
4 Imprope
r
manage
ment of
the
project
If the
project
activitie
s are not
manage
d
properly
then it
will be
quite
difficult
to
complet
e the
project
successf
ully
within
Proje
ct risk
If the
project
manager
s of the
organizat
ion are
not
experien
ce then
face
number
of
difficulti
es in
managin
g as well
as
controlli
It is
quite
importan
t to hire
experien
ced
project
manager
who will
be quite
capable
of
managin
g the
various
activities
of the
project
Project
manager Mediu
m
Medi
um
Will
be set
up in
1
mont
hs

5
PROJECT MANAGEMENT
the
estimate
time as
well as
budget.
ng the
project
and as
result the
project
faces
number
of
challeng
es
including
obstructi
on in the
project
progress.
quite
successf
ully that
will be
helpful
in
avoiding
project
related
risk
within
the
project
R
28
5 Inapprop
riate
informat
ion
gatherin
g
If the
project
related
informat
ion are
not
gathered
properly
then it
will be
Projec
t risk Improper
knowled
ge about
the
project
generally
causes
this
problem.
Proper
informat
ion
about
the
needs as
well as
requirem
ents of
the
project
manager
s
Low Medi
um
Set
up in
2
week
s

6
PROJECT MANAGEMENT
quite
difficult
to
progress
with the
project.
If proper
informati
on about
the
project is
not
circulate
d then it
will be
quite
difficult
to
complete
the
project
successf
ully.
project
must be
circulati
ng
among
the team
member
s so that
the
entire
project
can be
complet
ed
successf
ully.

Running head: PROJECT MANAGEMENT
5. Quality management plan
5.1 Philosophy for delivering quality system
It is identified that the quality management plan of the project mainly states that online
ticketing framework or system is mainly created for RAILS by providing appropriate number of
functionalities in order to meet various requirements as well as needs of the project.
Verification activities of the projects mainly include:
 Helps in making sure that the item is as per the authoritative system as well as
approaches
 Legitimated automation is generally checked
 Helps in guaranteeing about various activities of testing
 Helps in guaranteeing various procedures of testing with proper booked timetable
Validation activities generally include the following:
 Helps in differentiating various insider testing bugs
 Usefulness of various applications are generally identified
5.2 Quality issues
Project Name: RALS Rostering System Project manager Name:
(<<Name of the Student>>)
Sl.No Issues related with quality Time
required for
mitigation
Methodology
for mitigation
Owner Status
1 Improper quality of materials: 1month Inspection Project Open

1
PROJECT MANAGEMENT
The materials that are utilized in
order to develop the RALS
rostering system is found to be
not of proper quality. Low
qualities of materials as well as
equipments are mainly utilized
within the project in order to
complete the project within the
budget that is assumed during
the planning phase of the project.
manager
2 Improper training: The show
does not provide proper facility
of training to the project team
members and as a result the team
members of the project faces
number of difficulties in
progressing with the project and
as a result it became quite
difficult to complete the project
within the specified time and
budget.
1 months Inspection Project
manager
Open
3 Improper gathering of
information: Due to improper
information gathering it is
identified that the project
2 months Inspection project
manger
Open

2
PROJECT MANAGEMENT
managers faces number of
difficulties in progressing with
the project. Thus it is quite
important to understand the
needs as well as requirements of
the project quite effectively.
6. Annotated bibliography and closure checklist
6.1 Annotated Bibliography
Article 1: Davis, K. (2014). Different stakeholder groups and their perceptions of project
success. International Journal of Project Management, 32(2), 189-201
In this article, the author highlighted the significance of different stakeholders group as
well as other perceptions that are quite helpful in achieving the success of the project (Davis
2014). It is identified that the article mainly helps in giving proper knowledge as well as
information about various project perceptions by senior authority as well as stakeholders of the
organization. It mainly helps in providing proper suggestions that improper agreement of project
success helps in creating discontinuity between them.
Article 2: Mir, F. A., &Pinnington, A. H. (2014). Exploring the value of project management:
linking project management performance and project success. International journal of project
management, 32(2), 202-217.
The article mainly highlighted the relationship that mainly exists between project
execution as well as project accomplishment. Various factors that are associated with the

3
PROJECT MANAGEMENT
execution of the project are mainly highlighted with appropriate goal in order to achieve proper
success within the project (Mir & Pinnington 2014). It is found that in order to identify or
determine the accomplishment of the project proper multidimensional systems are generally
utilized. Moreover, it is differentiated that various sorts of relationship are generally investigated
in order to achieve proper success within the project.
Article 3: Anca, U., Cezar, B., & Adrian, U. (2015, November). Risk Identification in Project
Management. In International Conference on Economic Sciences and Business
Administration (Vol. 2, No. 1, pp. 259-266).SpiruHaret University
The article mainly highlighted the method of identifying risk that are mainly associated
with the project. It is found that project risk is mainly referred as one of the significant event that
generally assists in creating either negative or positive results on the project. It is identified that
different types of conditions that are associated with the risk mainly include various aspects of
the projects that generally assist in contributing within the project which is one of immature
activity of the project (Anca, Cezar & Adrian). Risk management procedure is one of the
methodologies that are very much beneficial in managing as well as controlling various types of
project related risks.
6.2 Closure checklist
Activities Stakeholder’s Name
Stakeholder’s
Signature
Project charter preparation Project manager
Project scope determination Project manager,
Business analyst,