Project and Quality Management: Bendigo Tours Information System Plan

This project plan outlines the development of a new information system for Bendigo Tours & Travel Company, focusing on supporting business operations and customer needs. The plan encompasses project scope, deliverables, and objectives, including a 7-month timeline and a budget of $680,000. It details stakeholder management strategies, a team contract emphasizing collaboration and timely execution, and a financial analysis with a positive NPV. The project adopts an Agile SDLC model, emphasizing customer satisfaction. The Work Breakdown Structure (WBS) organizes the project into manageable tasks, and a Gantt chart visualizes the schedule, with an earliest completion time of 144 days. The Communication Management Plan outlines communication strategies, and a risk management plan identifies and mitigates potential risks, including financial, resource allocation, and time management issues. The plan concludes with a bibliography of relevant sources.

Project and Quality
Management
STUDENT NAME:
STUDENT ID:

Project Scope Statement
This project is focused on development of an information system for
Bendigo Tours & Travel Company, which is a Leading Australian
Travel Agency. The information system will help to support the
company and ensure future growth. The information system could
be used by both the Company as well as Customers to fulfil their
desired needs and requirements.
The information system will help to cater the business needs along
with fulfilment of the customer requests. The development of an
information system will help the company to maintain their business
operations effectively and efficiently. The system will help the
company to get rid of paper based work and fragmented computer
systems.

Project Scope
Project Deliverables
 An information system to support the business as well as
maintaining the customers.
 24 hours x 7 days a week support for the customers so that they
can access the system at their own convenience.
 User documentation along with training of staffs and
maintenance documentation.
Objective
 The main objective of this project is the information system will
be developed within 7 months. The initial cost for this project has
been estimated to be $680,000 considering the procurement and
maintenance costs.

Stakeholder Register
Stakeholder Role in Project Type of
Stakeholder
Type of
Communication
Expectations Influence on
project
CEO Sponsor Internal Weekly meetings
(Video Conference)
Delivery of project on time and
within budget
High
Business
Analyst
Advisor Internal Weekly face to face
meetings
Support for operations and
business growth
Medium
IT Project
Manager
Project Manager Internal Weekly status
reports
Achievement of desired goals
and objectives
High
System
Administrator
Designer Internal Team meetings and
Weekly status
Support for operations and
proper data management
Low
System
Developer
Developer External Team meetings and
Progress reports
Proper delivery of functional
modules
Medium
System Tester Tester External Test reports and Bi-
weekly meetings
Error and bug free system Low
Quality Analyst Quality Analyst External Checkpoints and
monthly progress
reports
Quality of the system Low
Customer Client External Final delivery of
project
Access to the new system High

Stakeholder Management
Strategy There are four strategies for stakeholder
management based on their power and
interest on the project as illustrated in four
quadrants of the figure. The two key
stakeholders that have should be
managed well to ensure success of the
project is the CEO and Customers. The
CEO has high power as well as high
interest on the project so she will be
managed with utmost care. The
Customers have low power but high
interest on the project so they have to be
kept informed at every stage.

Team Contract
Team Agreement
 Successful completion of the
project by maintaining proper
quality
 The assignment needs to be
completed within assumed
timeframe
 The project manager requires to
possess leadership skills
 Each member should have clear
understanding regarding the
project scope and goal
 Each team member needs to be
cooperative
Code of Conduct
 Requires to be punctual and on time
arrival in every meeting
 Effectively and efficiently completing
the individually assigned roles
 Positive contribution from each
member to accomplish the
assignment
 Positive interaction and involvement
of all members in decision making
 Timely response on phone calls and
emails
 Each team members needs to take
care of their assigned roles
I have read and understood the team agreement and I will abide by the terms
and conditions stated in the contract. I will provide my full support towards
successful achievement of the team goals and objectives.

Financial analysis
Discount Rate 6.5%
0 1 2 3 4 5 Total
Cost
$
460,000.00 $ 55,000.00 $ 55,000.00 $ 55,000.00 $ 27,500.00 $ 27,500.00 $ 680,000.00
Discount Factor 0.94 0.88 0.83 0.78 0.73
Discounted Costs $ 51,643.19 $ 48,491.26 $ 45,531.70 $ 21,376.38 $ 20,071.72 $ 187,114.26
Benefits $ 320,000.00 $ 320,000.00 $ 320,000.00 $ 320,000.00 $ 320,000.00 $ 1,600,000.00
Discount Factor 0.94 0.88 0.83 0.78 0.73
Discounted Benefits $ 300,469.48 $ 282,130.97 $ 264,911.71 $ 248,743.39 $ 233,561.87 $ 1,329,817.42
Discounted Benefits - Costs $ 248,826.29 $ 233,639.71 $ 219,380.01 $ 227,367.00 $ 213,490.14 $ 1,142,703.16
Cumulative Benefits - Costs $ 265,000.00 $ 265,000.00 $ 265,000.00 $ 292,500.00 $ 292,500.00 $ 1,380,000.00
ROI 6.11 NPV $ 682,703.16

Appropriate SDLC model
In order to implement the Information system successfully the Software
development life cycle model that has to be followed by the project
manager and the project team members is Agile method. The agile
SDLC model is referred to as a combination of incremental and iterative
process models. This model is strictly focused on customer satisfaction
and process adoptability therefore, application of this SDLC will stand
beneficial for the project manager.
The large information System products are subdivided into small
parts after the application of agile project management method.
These are builds which provide iteration. Agile model is a realistic
approach that is focused on developing a software. This process
helps to promote teamwork, cross training and other functional
activities. Implementation of agile SDLC can fix the change
requirements with a minimum numbers of resources. The agile
project development method can deliver early partial working
solution to the consumers and to the employees.

WBS (Work Breakdown Structure)
0 - Information System
Development
1 - Planning
1.1 - Defining project scope
1.2 - Determining preliminary
resources
1.3 - Preparing the budget
1.4 - Analysis and gathering
of requirements
2 - Requirements analysis
2.1 - Identification of
business requirements
2.2 - Draft Preliminary
specifications of the
system
2.3 - Prepare blueprint of the
system
2.4 - Review of draft and
blueprint
2.5 - Approval of draft and
blueprint
3 - Designing
3.1 - Review preliminary
system specifications
3.2 - Identification of
required modules
3.3 - Development of
functional specifications
3.4 - Development of security
requirements
3.5 - Development of
prototype for the system
3.6 - Validation of the
functional and security
requirements
3.7 - Approval of prototype
design
4 - Development
4.1 - Review of functional
design
4.2 - Identification of external
interfaces
4.3 - Development of the
system and interfaces
4.4 - Development of the
functional modules
5 - Test plan preparation
5.1 - Development of test
plans
5.2 - Development of
external interface test
plan
5.3 - Development of security
test plan
5.4 - Review of test plans
5.5 - Approval of plans
6 - Testing
6.1 - Testing the modules
6.2 - Checking for error and
bugs
6.3 - Fixing of errors and
bugs
6.4 - User acceptance testing
6.5 - Quality check of the
system
6.6 - Finalization of the
system
7 - Training
7.1 - Identification of the
training requirements
7.2 - Development of training
materials
7.3 - Training of support staff
7.4 - Training of employees
8 - Documentation
8.1 - Development of help
documentation
8.2 - Development of user
manual
9 - Deployment
9.1 - Preparation of the
deployment plan
9.2 - Installation and
deployment of the system
10 - Closure
10.1 - Post implementation
review
10.2 - Documentation of
lessons learnt
10.3 - Stakeholders sign-off

Gantt chart

Earliest possible time for project
completion
The earliest possible
time by which the
project could be
completed is 144 days
with a start date of 21
January 2019.

Critical path in
Gantt chart