Developing Information System For Bendigo Tours And Travel

Project Scope

The project scope includes:

Development of an information system for Bendigo Tours and travel
Providing facilities like online reservation, hotel reservation, catering, ticket delivery and more.
Syncing hotel reservation system with the present website
Integration of system with social media

The risk register that is developed for the stakeholders who are engaged with the information system development for Bendigo tours and travel is provided in the table that is provided below:

Stakeholders	Impact	Probability Save Time On Research and Writing Hire a Pro to Write You a 100% Plagiarism-Free Paper. Get My Paper
Project manager	High	High
Project planner	High	Low
Application manager	Medium	Low
Developer	Medium	Medium
Database administrator	Medium	High
Coder	Medium	Low
Tester	Medium	Low
Quality analyst	Low	Low
Financial manager	Medium	Medium

The strategies that are required to be adopted in order to mange the stakeholders who are involved with the information system development are listed below:

Stakeholder mapping: Before the initiation phase, stakeholder analysis is needed to be conducted for identifying the stakeholders. Identification and examination of various types of key factors including various types of proximity as per the project, demographics as well as interest in the project (Mok, Shen and Yang 2015). Gaining proper understanding of the internal stakeholders such as suppliers, contractors, shareholders and more are required.

Influence: Understanding the level of influence generally helps in allowing stakeholders to interact directly with the team members of the project. The influence range is broad from positive sentiment and supports activism against the project. For measuring the possible influence of the project stakeholders, determining the level of influence is important.

Determination of triggers: Stakeholders reacts in a way to various actions of the project by determining the triggers and mitigating various actions by avoiding preventable complaints (Schnackenberg and Tomlinson 2016). When the stakeholders experience the changes within the environment or business expectation then they generally create a reaction.

The contract that is created for the project team mainly include information regarding team agreement, code of conduct and ground rules for a team.

Team agreement

The mission of the team is to work together as a unit so that the team members can be able to complete the project work on time.
The primary outcome and goals of the project team is to successfully complete the team assignment that is provided
Improving the understanding of the team members in the field of data management
Team members must work as per the work that is assigned to them by taking proper decision in a group
The main purpose of the team is to work hard and achieve maximum efficiency

Code of conduct

Arriving on time to the meetings quite punctually
Finishing the assigned tasks quite effectively as well as efficiently
Complete the work diligently and honestly
Proper contribution should be provided to the members positively as well as equally.

Ground rules for communication

It is a necessity to understand the goals and objectives of communication
Keeping the discussion on any topic of communication quite concisely
Listening to the views of others and acknowledging the valid points which are made by the person

The financial analysis that is mainly performed for the development of information system for the organization “Bendigo Tours and travel” is provided in the given table.


Discount Rate	6.5%
	0	1	2	3	4	5	Total
Cost	$ 4,60,000.00	$ 55,000.00	$ 55,000.00	$ 55,000.00	$ 27,500.00	$ 27,500.00	$ 6,80,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	$ 1,87,114.26

Benefits		$ 3,20,000.00	$ 3,20,000.00	$ 3,20,000.00	$ 3,20,000.00	$ 3,20,000.00	$ 16,00,000.00
Discount Factor		0.94	0.88	0.83	0.78	0.73
Discounted Benefits		$ 3,00,469.48	$ 2,82,130.97	$ 2,64,911.71	$ 2,48,743.39	$ 2,33,561.87	$ 13,29,817.42
Discounted Benefits – Costs		$ 2,48,826.29	$ 2,33,639.71	$ 2,19,380.01	$ 2,27,367.00	$ 2,13,490.14	$ 11,42,703.16
Cumulative Benefits – Costs		$ 2,65,000.00	$ 2,65,000.00	$ 2,65,000.00	$ 2,92,500.00	$ 2,92,500.00	$ 13,80,000.00
ROI	6.11					NPV	6,82,703.16

Agile SDLC model can be utilized for this particular project as this project helps in promoting continuous iteration of testing and development throughout the entire software development life. The main reason behind using agile project methodology is that agile project helps in allowing the changes within the project and provides an opportunity to constantly refine as well as reprioritize the changes that are needed within the project (Peroni 2016). In addition to this, with the help of this project methodology, the entire project is broken down into number of manageable units so that the entire project team can be able to focus on high-quality development, collaboration as well as testing (Tavakoli, Gandomani and Ahmadi 2016). In addition to this, it is found that agile is one of the powerful tools that is mainly used for software development that not only helps in providing benefits to the project development team but also assists in giving number of important business-related benefits to the client.

Stakeholder Management

The phases of the selected agile methodology for the development of the information system within the project is mainly elaborated below:

Conception phase: Projects are generally envisioned as well as prioritized in order to focus on the project goals and objectives.

Inception phase: In this phase, team members are identified, funding take place and other type of discussion are performed for the development of the website.

Iteration phase: In this phase, the development team mainly works in order to deliver the working of the entire software-based iteration (Elsayed et al. 2015).

Release phase: In this phase, quality of the project is checked and other activities like testing and documentation development is generally performed.

Production phase: In this particular phase, ongoing support to the software is generally provided (Sánchez 2015).

Retirement phase: This is the last phase of the project, in which the project activities are ended including the customer notification as well as migration.

On the basis of critical path method, schedule trade off is generally performed in order to calculate the float which is reflected in the below table.

WBS	Task Name	Duration	Total Slack
0	Implementation of information system for Bendigo Tours and travel	78 days	0 days
1	Conceptualization phase	11 days	0 days
1.1	Conservation with project team	3 days	0 days
1.2	Development of project proposal	2 days	0 days
1.3	Development of proper agreement	3 days	0 days
1.4	Determination of project stakeholders	2 days	0 days
1.5	Approval of project plan	1 day	0 days
2	Inception phase	21 days	0 days
2.1	Collecting ideas	4 days	63 days
2.2	Collecting review from the clients	3 days	0 days
2.3	Developing design	5 days	0 days
2.4	Checking project feasibility	3 days	0 days
2.5	Analyzing budget	5 days	0 days
2.6	Conducting meeting	4 days	0 days
2.7	Approval of final design	1 day	0 days
3	Iteration phase	36 days	0 days
3.1	Construction of prototype	3 days	0 days
3.2	Database development	5 days	0 days
3.3	Validation of code	4 days	0 days
3.4	Cross-browser testing	3 days	0 days
3.5	Optimization	2 days	0 days
3.6	Building web content	17 days	0 days
3.6.1	Developing navigation structure	1 day	0 days
3.6.2	Creating site content pages	1 day	0 days
3.6.3	International airline reservation and ticketing	2 days	25 days
3.6.4	Worldwide hotel reservation feature	2 days	0 days
3.6.5	Catering feature	2 days	0 days
3.6.6	Free ticket delivery	3 days	0 days
3.6.7	Camping services	2 days	0 days
3.6.8	Ground handling services	3 days	0 days
3.6.9	Conferences	3 days	12 days
3.7	Developing user experience	5 days	0 days
3.7.1	Updating details	2 days	0 days
3.7.2	Integrating with social media	3 days	0 days
4	Release phase	7 days	0 days
4.1	Web application access	3 days	0 days
4.2	Estimation of hardware and software	4 days	3 days
4.3	Testing and reviewing	3 days	0 days
5	Closure phase	4 days	0 days
5.1	Risk assessment	3 days	1 day
5.2	Quality management	3 days	0 days
5.3	Reviewing project	1 day	0 days

The communication plan that is developed for the development of information system is generally reflected in the table that is provided below:

Audience	Message	Vehicle	Frequency	Responsible
Team members	The project team members communicate the project objectives and goals so that the project team can be able to perform effectively.	Face to face	Once	Project manager
Project manager	The team leaders discuss the difficulties that are faced by the project team in order to develop the information system	Face to face, Email	Monthly	Team leaders
Project planner	The team leader provides project status report for providing information about project progress.	Face to face, Email	Weekly	Team leaders
Project manager	The financial manager provides information about the project finances to the project manager	Face to face, Email	Weekly	Project manager

The potential risks and challenges that are related with the development of information system are generally reflected in the table below:

ID	Risk	Description	Consequence	Likelihood	Mitigation
R1	Improper schedule slippage	If the schedule of the project is not tracked on a regular basis, then it is quite difficult to finish the project on time.	Critical	Almost certain	The schedule of the project must be tracked on a regular basis for avoiding schedule slippage.
R2	Lack of resources	If sufficient project resources are provided then it is quite difficult to complete the project on time.	Major	Possible	The resources that are required for the project must be estimated before the project initiation phase.
R3	Improper construction of prototype	If the project prototype is not properly constructed then the system that will be developed will not function properly.	Major	Likely	The designed prototype must be checked on regular basis for avoiding technical issues.
R4	Inexperienced team members	If the team members who are involved with the project are not experienced then they face lot of difficulties in finishing the project work.	Moderate	Likely	Hiring experienced project team member is necessary for finishing the work of the project

	Consequence
Likelihood		Insignificant	Minor	Moderate	Major	Critical
Rare
Unlikely
Possible				R2
Likely			R4	R3
Almost certain					R1

Week	Weekly status
Week 1	In week 1, conversation with the project team members is done and project proposal for the project is prepared.
Week 2	In week 2, proper agreement is prepared and the stakeholders who will be engaged with the project are identified.
Week 3	In week 3, proper ideas as well as review from the clients are collected.
Week 4	In week 4, project design is created and the feasibility of the project design is checked.
Week 5	In week 5, budget for the project is analyzed and proper meeting for the project is conducted.
Week 6	In week 6, navigation structure and site content pages of the website is developed.
Week 7	In week 7, feature of airline reservation and hotel reservation is created.
Week 8	In week 8, catering features as well as free ticket delivery feature is developed.
Week 9	In week 9, proper user experience for the website is mainly developed.
Week 10	In week 10, web application access is developed and the required software and hardware is developed.
Week 11	In week 11, information system that is developed is tested.
Week 12	In week 12, risk assessment and quality management is done for closing the project.

De Carvalho, M.M., Patah, L.A. and de Souza Bido, D., 2015. Project management and its effects on project success: Cross-country and cross-industry comparisons. International Journal of Project Management, 33(7), pp.1509-1522.

Diouf, D. and Boiral, O., 2017. The quality of sustainability reports and impression management: A stakeholder perspective. Accounting, Auditing & Accountability Journal, 30(3), pp.643-667.

Elsayed, H.A.G., Alharbi, A.N., AlNamlah, H. and Saba, T., 2015. Role of agile methodology in project management and leading management tools. J Bus Technov, 3, pp.188-193.

Kaiser, M.G., El Arbi, F. and Ahlemann, F., 2015. Successful project portfolio management beyond project selection techniques: Understanding the role of structural alignment. International Journal of Project Management, 33(1), pp.126-139.

Mok, K.Y., Shen, G.Q. and Yang, J., 2015. Stakeholder management studies in mega construction projects: A review and future directions. International Journal of Project Management, 33(2), pp.446-457.

Papke-Shields, K.E. and Boyer-Wright, K.M., 2017. Strategic planning characteristics applied to project management. International Journal of Project Management, 35(2), pp.169-179.

Peroni, S., 2016. A simplified agile methodology for ontology development. In OWL: Experiences and Directions–Reasoner Evaluation (pp. 55-69). Springer, Cham.

Sánchez, M.A., 2015. Integrating sustainability issues into project management. Journal of Cleaner Production, 96, pp.319-330.

Schnackenberg, A.K. and Tomlinson, E.C., 2016. Organizational transparency: A new perspective on managing trust in organization-stakeholder relationships. Journal of Management, 42(7), pp.1784-1810.

Tavakoli, Z., Gandomani, T.J. and Ahmadi, M., 2016. Knowledge Management in Agile Software Development: A Case Study of XP Agile Methodology. International Journal of Software Engineering and Technology, 2(1).

Todorovi?, M.L., Petrovi?, D.?., Mihi?, M.M., Obradovi?, V.L. and Bushuyev, S.D., 2015. Project success analysis framework: A knowledge-based approach in project management. International Journal of Project Management, 33(4), pp.772-783.

Turn in your highest-quality paper
Get a qualified writer to help you with

“ Developing Information System For Bendigo Tours And Travel ”

Get high-quality paper

NEW! AI matching with writer

Order an Essay Now & Get These Features For Free:

Turnitin Report

Formatting

Title Page

Citation

Outline

Place an Order