Project and Quality Management: Bendigo Tours and Travel System Plan

This project plan focuses on the development of an information system for Bendigo Tours and Travel, a major Australian tour and travel company. The plan outlines the project's scope, aiming to replace a paper-based system with an automated one and migrate data to the cloud for improved efficien...Read More

Project and Quality
Management: Bendigo Tours
and Travel
Name of the Student:
Name of the University:

Introduction
 Bendigo Tours and Travel is one of
the largest tours and travel company
in Australia that is also targeting the
international market.
 The company provides a wide range
of tour and travel related services
including airline ticket reservation,
hotel reservation, car rental,
excursions and itineraries,
conferences, catering and others.

Project Scope
Statement
 The main scope of the project is the
development of an information
system for Bendigo Tours and Travel.
 The company wants to remove the
paper based fragmented computing
system completely.
 The paper based system will be
replaced by automated computing
system.

Project Scope
Statement (Contd.)
 The development of the information
system will allow the company to
increase the speed and efficiency of
the daily operations.
 The scope of the project also allows
the company to migrate the entire
database into cloud computing
system for better storage and
management of large volumes of
data.

Stakeholder Register
Stakeholder Name Designation Duties and Roles
Mr. A Project Manager Guidance,
management,
monitoring and
control of project
Mr. B Finance Manager Control and
management of
project funds and
budget
Mr. C Information Systems
Developer
Development and
implementation of the
information system
Mr. D Technical Supervisor Supervision and
reporting of project
work

Stakeholder Management Strategy
(Stakeholder 1 – Project Manager)
 The project manager is responsible for
management of the entire project.
 In addition to management of the project, he
is responsible for guiding the team members,
monitoring the project progress and also
implement change management as required.
 In this project, the project manager will be
responsible for managing the
implementation of the information system for
Bendigo.

Stakeholder Management
Strategy (Stakeholder 2 –
Information System Developer)
 The information system developer will need
to develop and deploy the proposed
information system for Bendigo.
 The system requirements have been
specified by Bendigo and the information
system must have the mentioned features
installed.
 Migration to cloud can also be achieved and
the information system developer will have
to ensure there is sufficient security of data
stored in the cloud.

Team Contract
 The team is appointed based on the
requirements that have been set and
discussed.
 The team must follow the working
guidelines as set by the organisation.
 The team must work professionally
throughout the course of the project.
 Failing to reach the milestones of the
project and late delivery will incur
penalties for the team.

Team Contract
(Contd.)
 There should not be any conflict
among the project team members
while working in the project.
 The team must submit weekly
reports at the end of each week.
 The team must abide by the
instructions of the project manager
throughout the project.

Team Contract
(Contd.)
Name Signature of Team Members
Mr. A
______________________________________
Mr. B
______________________________________
Mr. C
______________________________________
Mr. D
______________________________________
Mr. E
______________________________________

Financial
Projections
Cost Projections
Total Costs for New Hardware $ 260,000.00
Total Costs for New Software $ 45,000.00
Development Costs for the New Information
System $ 275,000.00
Training Module for the Employees $ 100,000.00
Total Development Cost $ 680,000.00
Maintenance Cost of the Information System $ 55,000.00
Operational Costs $ 5,000.00
Other Costs $ 15,000.00 Cost After 3 Years
All Recurring Costs of the System $ 75,000.00 $ 47,500.00

Financial Projections
(Contd.)
Benefits Projections
Savings from Wages of the Employees $ 150,000.00
Reduced Various Costs $ 170,000.00
Total Benefit $ 320,000.00
Discount Rate Used 9.00%

Financial Analysis
(NPV and ROI)

Identification of SDLC
Model for the Project
 There are various SDLC models
available for the development and
execution of a project.
 Some of the models include
waterfall, agile, scrum, prototyping
and others (Hung et al. 2014).
 The selected SDLC model for this
particular project is Agile.
 Agile is best suited for projects that
are carried out in a number of

Justification of the
Chosen SDLC Model
 Agile provides a structured approach
towards project management.
 Agile model is specifically designed
for the information system
development projects (Cheng and
Yang 2014).
 Agile model involves iterations that
minimize the chances of errors and
residual issues.

Justification of the Chosen
SDLC Model (Contd.)
 Agile model will allow the project to
be executed in a number of different
phases.
 The agile model will involve six main
phases of project life cycle –
initiation, planning, execution,
monitoring and control and closing
(Laudon and Laudon 2016).

Work Breakdown
Structure
WBS Task Name
0 Information System Development for Bendigo
1 Requirement Gathering and Analysis
2 Formation of Project Team
3 Conduct Team Meeting
4 Development of Project Proposal
5 Approval for the Project
6 Determine Project Scope
7 Determine Project Schedule
8 Determine Project Budget
9 Finalise Project Plan
10 Hire Information System Developer
11 Hand Over System Requirements
12 Initiate Project Work
13 Develop Information System Architecture
14 Testing of the Architecture
15 Installation of New Hardware and Software
16 Develop System Prototype
17 Testing of Prototype
18 Integration of the System Features
19 Development of Final System
20 Detailed Testing
21 Migration of System to Cloud
22 Deploy Information System Security
23 Hand Over and Go Live

Gantt Chart

Critical Path and Earliest
Possible Completion Time

Schedule Trade
OffsTask Name Duration Early Start Early Finish Late Start Late Finish
Information System
Development for
Bendigo
32 wks Mon 6/3/19 Fri 1/10/20 Mon 6/3/19 Fri 1/10/20
Requirement
Gathering and Analysis 1 wk Mon 6/3/19 Fri 6/7/19 Mon 6/3/19 Fri 6/7/19
Formation of Project
Team 1 wk Mon 6/10/19 Fri 6/14/19 Mon 6/10/19 Fri 6/14/19
Conduct Team
Meeting 1 wk Mon 6/17/19 Fri 6/21/19 Mon 7/1/19 Fri 7/5/19
Development of
Project Proposal 3 wks Mon 6/17/19 Fri 7/5/19 Mon 6/17/19 Fri 7/5/19
Approval for the
Project 1 wk Mon 7/8/19 Fri 7/12/19 Mon 7/8/19 Fri 7/12/19
Determine Project
Scope 2 wks Mon 7/15/19 Fri 7/26/19 Mon 7/15/19 Fri 7/26/19
Determine Project
Schedule 1 wk Mon 7/29/19 Fri 8/2/19 Mon 7/29/19 Fri 8/2/19
Determine Project
Budget 1 wk Mon 7/29/19 Fri 8/2/19 Mon 7/29/19 Fri 8/2/19
Finalise Project Plan 1 wk Mon 8/5/19 Fri 8/9/19 Mon 8/5/19 Fri 8/9/19
Hire Information
System Developer 1 wk Mon 8/12/19 Fri 8/16/19 Mon 8/12/19 Fri 8/16/19
Hand Over System
Requirements 1 wk Mon 8/19/19 Fri 8/23/19 Mon 8/19/19 Fri 8/23/19
Initiate Project Work 1 wk Mon 8/26/19 Fri 8/30/19 Mon 8/26/19 Fri 8/30/19
Develop Information
System Architecture 4 wks Mon 9/16/19 Fri 10/11/19 Mon 9/30/19 Fri 10/25/19
Testing of the
Architecture 2 wks Mon 10/14/19 Fri 10/25/19 Mon 10/28/19 Fri 11/8/19
Installation of New
Hardware and Software 2 wks Mon 9/2/19 Fri 9/13/19 Mon 9/2/19 Fri 9/13/19

Activity Floats
Task Name Total Slack
Information System Development for Bendigo 0 wks
Requirement Gathering and Analysis 0 wks
Formation of Project Team 0 wks
Conduct Team Meeting 2 wks
Development of Project Proposal 0 wks
Approval for the Project 0 wks
Determine Project Scope 0 wks
Determine Project Schedule 0 wks
Determine Project Budget 0 wks
Finalise Project Plan 0 wks
Hire Information System Developer 0 wks
Hand Over System Requirements 0 wks
Initiate Project Work 0 wks
Develop Information System Architecture 2 wks
Testing of the Architecture 2 wks
Installation of New Hardware and Software 0 wks
Develop System Prototype 0 wks
Testing of Prototype 0 wks
Integration of the System Features 0 wks
Development of Final System 0 wks
Detailed Testing 0 wks
Migration of System to Cloud 1 wk
Deploy Information System Security 0 wks
Hand Over and Go Live 0 wks

Communication
Management Plan
Stakeholder Why? When? How?
Project Manager Project updates
and requests
Weekly Face to face,
update report
Finance
Manager
Funding
requirements
Whenever
required
Finance report
Information
Systems
Developer
System
requirements
Before project
initiation
Team meeting
Technical
Supervisor
Reporting and
guidance
requirements
Daily Face to face
Marketing
Manager
Marketing
requirements
Whenever
required
Emails

Potential Risks in the
Project
 Cyber security threats can create major
potential risk for the system (Erich, Amrit and
Daneva 2014).
 Complexity of the required information system
may result in unnecessary delays in the project.
 Lack of user acceptance of the information
system may result in failure of the project (Isaias
and Issa 2015).
 The staff may not be proficient enough to utilize
the information system.
 Budget overshoot is another major risk in the
project.

Risk Register
Risk Chances of
Occurrence
Impact on the
Overall
Project
Risk Rating
Cyber Security 4 5 20
System
Complexity
4 4 16
Low User
Acceptance
2 3 6
Lack of
Technical
Expertise of
Staff
3 3 9
Budget
Overshoot
4 3 12

Weekly Status
Report
 The system architecture
development is complete.
 Testing of the architecture is set to
be done next week.
 Each team member has fulfilled his
duties up to now.
 Approach to architecture testing has
been developed.

References
Cheng, H.H. and Yang, H.L., 2014. The antecedents of collective
creative efficacy for information system development teams. Journal
of Engineering and Technology Management, 33, pp.1-17.
Erich, F., Amrit, C. and Daneva, M., 2014, December. A mapping
study on cooperation between information system development and
operations. In International Conference on Product-Focused
Software Process Improvement (pp. 277-280). Springer, Cham.
Hung, Y.W., Hsu, S.C., Su, Z.Y. and Huang, H.H., 2014. Countering
user risk in information system development projects. International
Journal of Information Management, 34(4), pp.533-545.
Isaias, P. and Issa, T., 2015. Information system development life
cycle models. In High Level Models and Methodologies for
Information Systems (pp. 21-40). Springer, New York, NY.
Laudon, K.C. and Laudon, J.P., 2016. Management information
system. Pearson Education India.