Project Management: Development of RAILS Rostering System Report

This project management report details the development of a rostering system for the Riverina Agricultural and Lifestyle Show (RAILS). The report covers the measurable organizational value (MOV), scope management plan, project schedule, work breakdown structure (WBS), risk analysis, and quality management plan. It includes a Gantt chart illustrating the project timeline across initiation, planning, implementation, maintenance, and closure phases. The report also addresses assumptions, risk assessment, and mitigation strategies, alongside an annotated bibliography and closure checklist. The project aims to streamline volunteer management and improve the efficiency of show operations by implementing an online rostering system.

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