Project and Quality Management Plan for Bendigo Tours and Travel

This project plan outlines the development of an information system for Bendigo Tours and Travel, addressing the company's need to replace its paper-based system with an automated computing system. The plan encompasses a detailed project scope statement, stakeholder register, and management strategies. It includes a team contract, financial projections, and a cost-benefit analysis justifying the project's viability. The Agile SDLC model is selected and justified. The project plan also details a work breakdown structure, Gantt chart, schedule trade-offs, and a communication management plan. Furthermore, it identifies potential risks and provides a risk register, along with a weekly status report, offering a comprehensive guide for the project's execution, monitoring, and control, with a focus on enhancing business operations and marketing processes.

Running Head: PROJECT AND QUALITY MANAGEMENT
Project and Quality Management: Bendigo Tours and Travel
Name of the Student
Name of the University

1PROJECT AND QUALITY MANAGEMENT
Table of Contents
1. Introduction..................................................................................................................................2
2. Project Scope Statement..............................................................................................................2
3. Stakeholder Register and Stakeholder Management Strategy.....................................................2
4. Team Contract.............................................................................................................................4
5. Financial Projection.....................................................................................................................5
6. Identification and Justification of the SDLC Model for this Project...........................................7
7. Work Breakdown Structure.........................................................................................................7
8. Gantt Chart and Scheduling Details............................................................................................8
9. Schedule Trade Offs....................................................................................................................9
10. Communication Management Plan..........................................................................................11
11. Potential Risks in the Project and Risk Register.....................................................................11
12. Weekly Status Report..............................................................................................................12
References......................................................................................................................................13

2PROJECT AND QUALITY MANAGEMENT
1. 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.
In this report, a project plan has been developed for Bendigo who wants to deploy an
information system for enhancing its business operations and marketing processes.
2. 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. 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.
3. Stakeholder Register and Stakeholder Management Strategy
Stakeholder Name Designation Duties and Roles
Mr. A Project Manager Guidance, management,
monitoring and control of

3PROJECT AND QUALITY MANAGEMENT
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
Mr. E Marketing Manager Marketing for Bendigo
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 implementing change management as required. In this project, the
project manager will be responsible for managing the implementation of the information system
for Bendigo.
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

4PROJECT AND QUALITY MANAGEMENT
be achieved and the information system developer will have to ensure there is sufficient security
of data stored in the cloud.
4. Team Contract
The team contract for the project will consist of the following terms and conditions.
 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.
 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.
Name Signature of Team Members
Mr. A _____________________________________
_
Mr. B _____________________________________
_
Mr. C _____________________________________
_
Mr. D _____________________________________
_

5PROJECT AND QUALITY MANAGEMENT
Mr. E _____________________________________
_
5. Financial Projection
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
Benefits Projections
Savings from Wages of the Employees $ 150,000.00

6PROJECT AND QUALITY MANAGEMENT
Reduced Various Costs $ 170,000.00
Total Benefit $ 320,000.00
Discount Rate Used 9.00%
Cost Benefit Analysis and Financial
Statement for Bendigo Tours and
Travels
Analysis Variables:
Discount Rate Used 9.00%
Annual Benefits
$
320,00
0.00
Annual Operational Costs
$
75,000.
00
$
47,500.
00
One-Time Development Cost
$
680,00
0.00
Year of
Project
0 1 2 3 4 5
TOTAL
S
Economic Benefit $0.00
$
320,000.
00
$
320,000.
00
$
320,000.0
0
$
320,000.
00
$
320,000.
00
Discount Rate 1.0000 0.9174 0.8417 0.7722 0.7084 0.6499
PV of Benefits $0.00
$293,577
.98
$269,337
.60
$247,098.
71
$226,696
.07
$207,97
8.04
NPV of all BENEFITS $0.00
$
293,577.
98
$
562,915.
58
$
810,014.2
9
$
1,036,71
0.36
$
1,244,68
8.40
$
1,244,68
8.40
One-Time COSTS
$(680,
000.00
)
Recurring Costs $0.00
$
(75,000.0
0)
$
(75,000.0
0)
$
(75,000.0
0)
$
(47,500.0
0)
$
(47,500.
00)
Discount Rate 1.0000 0.9174 0.8417 0.7722 0.7084 0.6499
PV of Recurring Costs $0.00
$
(68,807.3
4)
$
(63,126.0
0)
$
(57,913.7
6)
$
(33,650.2
0)
$
(30,871.
74)
NPV of all COSTS
$(680,
000.00
$
(748,807.
34)
$
(811,933.
34)
$
(869,847.
10)
$
(903,497.
30)
$
(934,369
.04)
$
(934,36
9.04)

7PROJECT AND QUALITY MANAGEMENT
)
Overall NPV
$
310,319.
37
Overall ROI 33%
6. Identification and Justification of the SDLC Model for this 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 phases.
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. 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).
7. Work Breakdown Structure
The work breakdown structure including the schedule, dependencies and resource
assignments are shown as follows.
WBS Task Name Duration Start Finish Predecessors Resource Names
0 Information System
Development for Bendigo 32 wks Mon 6/3/19 Fri 1/10/20
1 Requirement Gathering and
Analysis 1 wk Mon 6/3/19 Fri 6/7/19 Project Manager, Marketing
Manager
2 Formation of Project Team 1 wk Mon 6/10/19 Fri 6/14/19 1 Project Manager
3 Conduct Team Meeting 1 wk Mon 6/17/19 Fri 6/21/19 2 Project Manager

8PROJECT AND QUALITY MANAGEMENT
4 Development of Project
Proposal 3 wks Mon 6/17/19 Fri 7/5/19 2 Technical Supervisor
5 Approval for the Project 1 wk Mon 7/8/19 Fri 7/12/19 3,4 Project Manager
6 Determine Project Scope 2 wks Mon 7/15/19 Fri 7/26/19 4,5 Technical Supervisor
7 Determine Project Schedule 1 wk Mon 7/29/19 Fri 8/2/19 6 Technical Supervisor
8 Determine Project Budget 1 wk Mon 7/29/19 Fri 8/2/19 6 Finance Manager
9 Finalise Project Plan 1 wk Mon 8/5/19 Fri 8/9/19 7,8 Project Manager
10 Hire Information System
Developer 1 wk Mon 8/12/19 Fri 8/16/19 6,9 Project Manager
11 Hand Over System
Requirements 1 wk Mon 8/19/19 Fri 8/23/19 6,10 Technical Supervisor
12 Initiate Project Work 1 wk Mon 8/26/19 Fri 8/30/19 11 Information Systems
Developer
13 Develop Information System
Architecture 4 wks Mon 9/16/19 Fri 10/11/19 15 Information Systems
Developer
14 Testing of the Architecture 2 wks Mon 10/14/19 Fri 10/25/19 13 Information Systems
Developer
15 Installation of New Hardware
and Software 2 wks Mon 9/2/19 Fri 9/13/19 12 Information Systems
Developer
16 Develop System Prototype 5 wks Mon 9/16/19 Fri 10/18/19 15 Information Systems
Developer
17 Testing of Prototype 3 wks Mon 10/21/19 Fri 11/8/19 16 Information Systems
Developer
18 Integration of the System
Features 2 wks Mon 11/11/19 Fri 11/22/19 14,17 Information Systems
Developer
19 Development of Final System 2 wks Mon 11/25/19 Fri 12/6/19 18 Information Systems
Developer
20 Detailed Testing 2 wks Mon 12/9/19 Fri 12/20/19 19 Information Systems
Developer
21 Migration of System to Cloud 1 wk Mon 12/9/19 Fri 12/13/19 19 Information Systems
Developer
22 Deploy Information System
Security 2 wks Mon 12/23/19 Fri 1/3/20 20,21 Information Systems
Developer
23 Hand Over and Go Live 1 wk Mon 1/6/20 Fri 1/10/20 22 Information Systems
Developer

9PROJECT AND QUALITY MANAGEMENT
8. Gantt Chart and Scheduling Details
The Gantt chart of the project along with the critical path is shown in the following
diagram.
Figure 1: Gantt Chart of the Project with Critical Path Marked in Red
(Source: Created by Author)
9. Schedule Trade Offs
WBS Task Name Duration Start Finish Early Start Early
Finish Late Start Late Finish Total
Float
0
Information
System
Development for
Bendigo
32 wks Mon 6/3/19 Fri 1/10/20 Mon 6/3/19 Fri 1/10/20 Mon 6/3/19 Fri 1/10/20 0 wks
1 Requirement
Gathering and
1 wk Mon 6/3/19 Fri 6/7/19 Mon 6/3/19 Fri 6/7/19 Mon 6/3/19 Fri 6/7/19 0 wks

10PROJECT AND QUALITY MANAGEMENT
Analysis
2 Formation of
Project Team 1 wk Mon
6/10/19 Fri 6/14/19 Mon
6/10/19 Fri 6/14/19 Mon
6/10/19 Fri 6/14/19 0 wks
3 Conduct Team
Meeting 1 wk Mon
6/17/19 Fri 6/21/19 Mon
6/17/19 Fri 6/21/19 Mon 7/1/19 Fri 7/5/19 2 wks
4 Development of
Project Proposal 3 wks Mon
6/17/19 Fri 7/5/19 Mon
6/17/19 Fri 7/5/19 Mon
6/17/19 Fri 7/5/19 0 wks
5 Approval for the
Project 1 wk Mon 7/8/19 Fri 7/12/19 Mon 7/8/19 Fri 7/12/19 Mon 7/8/19 Fri 7/12/19 0 wks
6 Determine Project
Scope 2 wks Mon
7/15/19 Fri 7/26/19 Mon
7/15/19 Fri 7/26/19 Mon
7/15/19 Fri 7/26/19 0 wks
7 Determine Project
Schedule 1 wk Mon
7/29/19 Fri 8/2/19 Mon
7/29/19 Fri 8/2/19 Mon
7/29/19 Fri 8/2/19 0 wks
8 Determine Project
Budget 1 wk Mon
7/29/19 Fri 8/2/19 Mon
7/29/19 Fri 8/2/19 Mon
7/29/19 Fri 8/2/19 0 wks
9 Finalise Project
Plan 1 wk Mon 8/5/19 Fri 8/9/19 Mon 8/5/19 Fri 8/9/19 Mon 8/5/19 Fri 8/9/19 0 wks
10 Hire Information
System Developer 1 wk Mon
8/12/19 Fri 8/16/19 Mon
8/12/19 Fri 8/16/19 Mon
8/12/19 Fri 8/16/19 0 wks
11
Hand Over
System
Requirements
1 wk Mon
8/19/19 Fri 8/23/19 Mon
8/19/19 Fri 8/23/19 Mon
8/19/19 Fri 8/23/19 0 wks
12 Initiate Project
Work 1 wk Mon
8/26/19 Fri 8/30/19 Mon
8/26/19 Fri 8/30/19 Mon
8/26/19 Fri 8/30/19 0 wks
13
Develop
Information System
Architecture
4 wks Mon
9/16/19 Fri 10/11/19 Mon
9/16/19 Fri 10/11/19 Mon
9/30/19 Fri 10/25/19 2 wks
14 Testing of the
Architecture 2 wks Mon
10/14/19 Fri 10/25/19 Mon
10/14/19 Fri 10/25/19 Mon
10/28/19 Fri 11/8/19 2 wks
15
Installation of
New Hardware and
Software
2 wks Mon 9/2/19 Fri 9/13/19 Mon 9/2/19 Fri 9/13/19 Mon 9/2/19 Fri 9/13/19 0 wks
16 Develop System
Prototype 5 wks Mon
9/16/19 Fri 10/18/19 Mon
9/16/19 Fri 10/18/19 Mon
9/16/19 Fri 10/18/19 0 wks
17 Testing of
Prototype 3 wks Mon
10/21/19 Fri 11/8/19 Mon
10/21/19 Fri 11/8/19 Mon
10/21/19 Fri 11/8/19 0 wks
18 Integration of the
System Features 2 wks Mon
11/11/19 Fri 11/22/19 Mon
11/11/19 Fri 11/22/19 Mon
11/11/19 Fri 11/22/19 0 wks
19 Development of
Final System 2 wks Mon
11/25/19 Fri 12/6/19 Mon
11/25/19 Fri 12/6/19 Mon
11/25/19 Fri 12/6/19 0 wks

11PROJECT AND QUALITY MANAGEMENT
20 Detailed Testing 2 wks Mon
12/9/19 Fri 12/20/19 Mon
12/9/19 Fri 12/20/19 Mon
12/9/19 Fri 12/20/19 0 wks
21 Migration of
System to Cloud 1 wk Mon
12/9/19 Fri 12/13/19 Mon
12/9/19 Fri 12/13/19 Mon
12/16/19 Fri 12/20/19 1 wk
22
Deploy
Information System
Security
2 wks Mon
12/23/19 Fri 1/3/20 Mon
12/23/19 Fri 1/3/20 Mon
12/23/19 Fri 1/3/20 0 wks
23 Hand Over and
Go Live 1 wk Mon 1/6/20 Fri 1/10/20 Mon 1/6/20 Fri 1/10/20 Mon 1/6/20 Fri 1/10/20 0 wks
10. 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

12PROJECT AND QUALITY MANAGEMENT
11. Potential Risks in the Project and Risk Register
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. The final major risk with this project is budget overshoot that may arise due to
overspending, missing project deadline and improper cost estimation during planning.
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
12. Weekly Status Report
The weekly status is as follows.
 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.

13PROJECT AND QUALITY MANAGEMENT
 Approach to architecture testing has been developed.

14PROJECT AND QUALITY MANAGEMENT
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.