In this new technical era traditional manual data management system is becoming obsolete thus it is necessary for any company to introduce online booking system to grab new consumers and to retain the existing consumers. This report depicts the importance of executing online booking system that has been designed by Sub Sea Adventures. SSA has approached a VUISC for supporting the transition of the new electronic Scuba Booking system (SSB). The scope of the project including the aim and objectives of the booking system and the approach to be applied for successfully accomplishing the online booking system are also illustrated in this report. A project schedule is also developed for the online booking system to estimate the overall project cost and time that will be needed for the completion of the project.
Aim
The aim of the project is to design an online booking system for Sub Sea Adventures (SSA) so that the consumers can book as per their demand.
Objectives
The suitable project management methodology for the project to develop Scuba Booking System and website for Sub Sea Adventures is PRINCE2 which is denoted as Projects in Controlled Environments. It is the most commonly used methodology for project management worldwide across almost 150 countries (Hornstein 2015). This approach is based on process and it focuses on organizing and controlling the entire project from the beginning to completion. This means that proper planning is being done prior to project kickoff and every stage of the project is clearly structured. This project management is being built on various principles as illustrated below:
This methodology is being carried out into different stages from beginning to completion as discussed below:
Starting the project: In this phase the final submission of the new project request which is also known as project mandate is done. The project mandate are always precise and briefly represented. The project mandate covers the details of the project request that has to be followed for the successful accomplishment of the projects.
Directing the project: Whether the company is capable to take the project or not is analyzed by that person who access the project mandate (Nicholas and Steyn 2017). In this phase, the project head shows a path to the project team members that should be followed for the successful accomplishment of the project.
Initiation of project: In order to initiate the project, SSA should estimate a project budget and timeline as well. It is the responsibility of the project manager and the project team members to complete the project within the estimated timeframe.
Control of stages: All the project development stages are to be monitored and controlled by the project lead. The online scuba diving booking system needs to be monitored throughout the iterative phases.
Manage delivery of product: Th online system that has to be designed for SSA, will operate the booking for many countries thus some necessary features are to be incorporated to it in terms of simple account creation, updated notification, branch management, timeout delay etc (Martinelli and Milosevic 2016).
Management of stage boundaries: PRICE2 project development methodology helps the project manager to manage the project stage boundaries. With strategic plan, risk management plan and activity management the stage boundaries will be managed appropriately.
Closure of the project: This is the last phase of project development. In this phase post maintenance plan for the online system will be created and additionally the stakeholder’s signoff from the project at this phase.
The project on development of the new electronic Scuba Booking System (SBS) for Sub Sea Adventures (SSA) will be carried out in six different phases as discussed below:
|
Phase |
Duration |
Description |
|
Initiation Phase |
17 days |
This phase will comprise of planning, requirements analysis along with presenting the budget for project. Further, a feasibility study for the project will be also conducted in this phase to ensure success of the project. |
|
Analysis phase |
8 days |
In this phase, analysis of existing issues and the procedure of handling business operations will be executed for better understanding of the exact requirements of Sub Sea Adventures. |
|
Design phase |
23 days |
This phase mainly comprises of the designing related activities so that a conceptual view of the new system could be presented to the client. The development of new system will depend entirely upon approval of system and website design being presented to the client. |
|
Development phase |
49 days |
In this phase, the development of the system and website will take place simultaneously along with testing of the modules to ensure success of the project. |
|
Implementation phase |
10 days |
This phase represents the activities that are required for implementing the new system as well as website to help in business processes of Sub Sea Adventures. The database will be connected with system and business to check proper running of the systems. |
|
Closure phase |
18 days |
This phase relates to close out of the project means that it has come to an end where documentation is prepared for project review and lessons learnt. Further, training of the staffs is also included in this phase. |
The resources required for executing the project on development of new electronic Scuba Booking System (SBS) has been identified as below:
|
Resource Name |
Type |
Initials |
Max. Units |
Std. Rate |
|
Project Manager |
Work |
PM |
100% |
$185.00/hr |
|
Business Analyst |
Work |
BA |
100% |
$125.00/hr |
|
Technical Writer |
Work |
TW |
100% |
$95.00/hr |
|
Developer |
Work |
DV |
100% |
$80.00/hr |
|
Designer |
Work |
DS |
100% |
$85.00/hr |
|
Technical Lead |
Work |
TL |
100% |
$82.00/hr |
|
System tester |
Work |
ST |
100% |
$75.00/hr |
|
Quality Analyst |
Work |
QA |
100% |
$84.00/hr |
|
Trainer |
Work |
TR |
100% |
$125.00/hr |
The above table presents the list of resource along with the availability and the standard rate with which they will be allocated for executing the project.
In the below table, a proper breakdown of the resources has been presented who will be responsible for execution of the project. The table reflects on the total duration for which a particular resource will be associated with the project along with the start date and finish date of their involvement. This means that the resource will engaged for a particular duration and after that it will be released as soon as the work is finished.
|
Name |
Start |
Finish |
Remaining Work |
|
Project Manager |
Fri 03-01-14 |
Mon 02-06-14 |
296 hrs |
|
Business Analyst |
Fri 03-01-14 |
Mon 02-06-14 |
232 hrs |
|
Technical Writer |
Mon 12-05-14 |
Tue 13-05-14 |
16 hrs |
|
Developer |
Thu 06-02-14 |
Thu 01-05-14 |
560 hrs |
|
Designer |
Fri 07-02-14 |
Tue 01-04-14 |
216 hrs |
|
Technical Lead |
Fri 31-01-14 |
Tue 13-05-14 |
104 hrs |
|
System tester |
Tue 08-04-14 |
Wed 16-04-14 |
56 hrs |
|
Quality Analyst |
Tue 08-04-14 |
Wed 07-05-14 |
104 hrs |
|
Trainer |
Wed 14-05-14 |
Tue 27-05-14 |
80 hrs |
The above chart is a graphical presentation of the involvement of resources in the project. The individual bars colored in organge presents the duration of each resource for which that particualr resource will be engaged with the project.
|
Resource Name |
Work |
|
Project Manager |
296 hrs |
|
Analysis of requirements |
40 hrs |
|
Preparation of objectives |
32 hrs |
|
Statement of project scope |
24 hrs |
|
Feasibility analysis for the project |
32 hrs |
|
Requirement analysis documentation signoff |
8 hrs |
|
Analyze existing business process |
24 hrs |
|
Approval of the designs |
8 hrs |
|
Review of project |
16 hrs |
|
Training of staffs |
80 hrs |
|
Lessons learnt |
24 hrs |
|
Project closeout |
8 hrs |
|
Business Analyst |
232 hrs |
|
Analysis of requirements |
40 hrs |
|
Feasibility analysis for the project |
32 hrs |
|
Budgeting for the project |
16 hrs |
|
Requirement analysis documentation signoff |
8 hrs |
|
Analyze existing business process |
24 hrs |
|
Determining the execution procedures |
16 hrs |
|
Approval of the designs |
8 hrs |
|
Training of staffs |
80 hrs |
|
Project closeout |
8 hrs |
|
Technical Writer |
16 hrs |
|
Preparation of training documentation |
16 hrs |
|
Developer |
560 hrs |
|
Preparing the process flow documentation |
8 hrs |
|
Preparing the design of website contents |
56 hrs |
|
Coding for the system |
200 hrs |
|
Developing the structure for website |
160 hrs |
|
Development of database for the system and website |
40 hrs |
|
Establishment of connection between the system and website |
16 hrs |
|
Implementation of database for system and website |
16 hrs |
|
Alteration of codes and fixing errors |
40 hrs |
|
Installation of the system |
16 hrs |
|
Hosting the website |
8 hrs |
|
Designer |
216 hrs |
|
Designing the interface for system |
40 hrs |
|
Preparing the design of website contents |
56 hrs |
|
Design of the GUI for system and website |
80 hrs |
|
Development of database for the system and website |
40 hrs |
|
Technical Lead |
104 hrs |
|
Determining the execution procedures |
16 hrs |
|
Screening of manual processes |
16 hrs |
|
Preparing the process flow documentation |
8 hrs |
|
Determining the data to be stored in the system |
24 hrs |
|
Installation of the system |
16 hrs |
|
Connecting with database |
8 hrs |
|
Preparation of training documentation |
16 hrs |
|
System tester |
56 hrs |
|
Unit testing of codes |
24 hrs |
|
User acceptance testing |
32 hrs |
|
Quality Analyst |
104 hrs |
|
Unit testing of codes |
24 hrs |
|
User acceptance testing |
32 hrs |
|
Checking of proper running of system modules |
16 hrs |
|
Checking of modules in the website |
32 hrs |
|
Trainer |
80 hrs |
|
Training of staffs |
80 hrs |
The budget that has been estimated for the project to develop a new electronic Scuba Booking System (SBS) is $179,904.00 and the detailed breakdown of the project budget has been illustrated for each activity as below:
|
WBS |
Task Name |
Duration |
Cost |
|
0 |
Scuba Booking System Development Project |
107 days |
$179,904.00 |
|
1 |
Initiation Phase |
17 days |
$37,160.00 |
|
1.1 |
Analysis of requirements |
5 days |
$12,400.00 |
|
1.2 |
Preparation of objectives |
4 days |
$5,920.00 |
|
1.3 |
Statement of project scope |
3 days |
$4,440.00 |
|
1.4 |
Feasibility analysis for the project |
4 days |
$9,920.00 |
|
1.5 |
Budgeting for the project |
2 days |
$2,000.00 |
|
1.6 |
Requirement analysis documentation signoff |
1 day |
$2,480.00 |
|
2 |
Analysis phase |
8 days |
$13,360.00 |
|
2.1 |
Analyze existing business process |
3 days |
$7,440.00 |
|
2.2 |
Determining the execution procedures |
2 days |
$3,312.00 |
|
2.3 |
Screening of manual processes |
2 days |
$1,312.00 |
|
2.4 |
Preparing the process flow documentation |
1 day |
$1,296.00 |
|
3 |
Design phase |
23 days |
$21,920.00 |
|
3.1 |
Designing the interface for system |
5 days |
$3,400.00 |
|
3.2 |
Preparing the design of website contents |
7 days |
$9,240.00 |
|
3.3 |
Design of the GUI for system and website |
10 days |
$6,800.00 |
|
3.4 |
Approval of the designs |
1 day |
$2,480.00 |
|
4 |
Development phase |
49 days |
$52,032.00 |
|
4.1 |
Coding for the system |
25 days |
$16,000.00 |
|
4.2 |
Developing the structure for website |
20 days |
$12,800.00 |
|
4.3 |
Determining the data to be stored in the system |
3 days |
$1,968.00 |
|
4.4 |
Development of database for the system and website |
5 days |
$6,600.00 |
|
4.5 |
Establishment of connection between the system and website |
2 days |
$1,280.00 |
|
4.6 |
Implementation of database for system and website |
2 days |
$1,280.00 |
|
4.7 |
Testing |
12 days |
$12,104.00 |
|
4.7.1 |
Unit testing of codes |
3 days |
$3,816.00 |
|
4.7.2 |
User acceptance testing |
4 days |
$5,088.00 |
|
4.7.3 |
Alteration of codes and fixing errors |
5 days |
$3,200.00 |
|
5 |
Implementation phase |
10 days |
$7,920.00 |
|
5.1 |
Installation of the system |
2 days |
$2,592.00 |
|
5.2 |
Connecting with database |
1 day |
$656.00 |
|
5.3 |
Checking of proper running of system modules |
2 days |
$1,344.00 |
|
5.4 |
Hosting the website |
1 day |
$640.00 |
|
5.5 |
Checking of modules in the website |
4 days |
$2,688.00 |
|
6 |
Closure phase |
18 days |
$47,512.00 |
|
6.1 |
Review of project |
2 days |
$2,960.00 |
|
6.2 |
Preparation of training documentation |
2 days |
$2,832.00 |
|
6.3 |
Training of staffs |
10 days |
$34,800.00 |
|
6.4 |
Lessons learnt |
3 days |
$4,440.00 |
|
6.5 |
Project closeout |
1 day |
$2,480.00 |
The schedule for the project has been presented below so that the development of new electronic Scuba Booking System can be executed successfully to solve the existing issues of Sub Sea Adventures. The schedule being prepared for the project reflects that it will require 107 days to complete starting from the initiation to closure phase assuming that the project will begin on 03 January 2014 and will complete on 02 June 2014. The date that has been decided for implementation of the new electronic system is 02 June 2014. Hence, the schedule has been prepared so that it can be completed within the planned date of implementation. The scheduling of the project has been done with proper allocation of resources and determining the required duration of each activity for completion of the project.
|
WBS |
Task Name |
Duration |
Start |
Finish |
Predecessors |
Resource Names |
|
0 |
Scuba Booking System Development Project |
107 days |
Fri 03-01-14 |
Mon 02-06-14 |
||
|
1 |
Initiation Phase |
17 days |
Fri 03-01-14 |
Mon 27-01-14 |
||
|
1.1 |
Analysis of requirements |
5 days |
Fri 03-01-14 |
Thu 09-01-14 |
Business Analyst, Project Manager |
|
|
1.2 |
Preparation of objectives |
4 days |
Fri 10-01-14 |
Wed 15-01-14 |
2 |
Project Manager |
|
1.3 |
Statement of project scope |
3 days |
Thu 16-01-14 |
Mon 20-01-14 |
2,3 |
Project Manager |
|
1.4 |
Feasibility analysis for the project |
4 days |
Tue 21-01-14 |
Fri 24-01-14 |
4 |
Business Analyst, Project Manager |
|
1.5 |
Budgeting for the project |
2 days |
Thu 16-01-14 |
Fri 17-01-14 |
3 |
Business Analyst |
|
1.6 |
Requirement analysis documentation signoff |
1 day |
Mon 27-01-14 |
Mon 27-01-14 |
5,6 |
Business Analyst, Project Manager |
|
2 |
Analysis phase |
8 days |
Tue 28-01-14 |
Thu 06-02-14 |
||
|
2.1 |
Analyze existing business process |
3 days |
Tue 28-01-14 |
Thu 30-01-14 |
7 |
Business Analyst, Project Manager |
|
2.2 |
Determining the execution procedures |
2 days |
Fri 31-01-14 |
Mon 03-02-14 |
9 |
Business Analyst, Technical Lead |
|
2.3 |
Screening of manual processes |
2 days |
Tue 04-02-14 |
Wed 05-02-14 |
10,9 |
Technical Lead |
|
2.4 |
Preparing the process flow documentation |
1 day |
Thu 06-02-14 |
Thu 06-02-14 |
11 |
Developer, Technical Lead |
|
3 |
Design phase |
23 days |
Fri 07-02-14 |
Tue 11-03-14 |
||
|
3.1 |
Designing the interface for system |
5 days |
Fri 07-02-14 |
Thu 13-02-14 |
12 |
Designer |
|
3.2 |
Preparing the design of website contents |
7 days |
Mon 17-02-14 |
Tue 25-02-14 |
10,14 |
Designer, Developer |
|
3.3 |
Design of the GUI for system and website |
10 days |
Wed 26-02-14 |
Tue 11-03-14 |
15 |
Designer |
|
3.4 |
Approval of the designs |
1 day |
Fri 14-02-14 |
Fri 14-02-14 |
14 |
Business Analyst, Project Manager |
|
4 |
Development phase |
49 days |
Fri 14-02-14 |
Wed 23-04-14 |
||
|
4.1 |
Coding for the system |
25 days |
Fri 14-02-14 |
Thu 20-03-14 |
14 |
Developer |
|
4.2 |
Developing the structure for website |
20 days |
Wed 26-02-14 |
Tue 25-03-14 |
15 |
Developer |
|
4.3 |
Determining the data to be stored in the system |
3 days |
Fri 21-03-14 |
Tue 25-03-14 |
19 |
Technical Lead |
|
4.4 |
Development of database for the system and website |
5 days |
Wed 26-03-14 |
Tue 01-04-14 |
20,21 |
Designer, Developer |
|
4.5 |
Establishment of connection between the system and website |
2 days |
Wed 02-04-14 |
Thu 03-04-14 |
22 |
Developer |
|
4.6 |
Implementation of database for system and website |
2 days |
Fri 04-04-14 |
Mon 07-04-14 |
23 |
Developer |
|
4.7 |
Testing |
12 days |
Tue 08-04-14 |
Wed 23-04-14 |
||
|
4.7.1 |
Unit testing of codes |
3 days |
Tue 08-04-14 |
Thu 10-04-14 |
24,19 |
System tester, Quality Analyst |
|
4.7.2 |
User acceptance testing |
4 days |
Fri 11-04-14 |
Wed 16-04-14 |
26,24 |
System tester, Quality Analyst |
|
4.7.3 |
Alteration of codes and fixing errors |
5 days |
Thu 17-04-14 |
Wed 23-04-14 |
27,19 |
Developer |
|
5 |
Implementation phase |
10 days |
Thu 24-04-14 |
Wed 07-05-14 |
||
|
5.1 |
Installation of the system |
2 days |
Thu 24-04-14 |
Fri 25-04-14 |
28 |
Developer, Technical Lead |
|
5.2 |
Connecting with database |
1 day |
Mon 28-04-14 |
Mon 28-04-14 |
30 |
Technical Lead |
|
5.3 |
Checking of proper running of system modules |
2 days |
Tue 29-04-14 |
Wed 30-04-14 |
31 |
Quality Analyst |
|
5.4 |
Hosting the website |
1 day |
Thu 01-05-14 |
Thu 01-05-14 |
32 |
Developer |
|
5.5 |
Checking of modules in the website |
4 days |
Fri 02-05-14 |
Wed 07-05-14 |
33 |
Quality Analyst |
|
6 |
Closure phase |
18 days |
Thu 08-05-14 |
Mon 02-06-14 |
||
|
6.1 |
Review of project |
2 days |
Thu 08-05-14 |
Fri 09-05-14 |
34 |
Project Manager |
|
6.2 |
Preparation of training documentation |
2 days |
Mon 12-05-14 |
Tue 13-05-14 |
36 |
Technical Lead, Technical Writer |
|
6.3 |
Training of staffs |
10 days |
Wed 14-05-14 |
Tue 27-05-14 |
37 |
Business Analyst, Project Manager, Trainer |
|
6.4 |
Lessons learnt |
3 days |
Wed 28-05-14 |
Fri 30-05-14 |
38 |
Project Manager |
|
6.5 |
Project closeout |
1 day |
Mon 02-06-14 |
Mon 02-06-14 |
39 |
Business Analyst, Project Manager |
Gantt chart is the graphical representation of project schedule that illustrates the various activities required to execute a project. Gantt chart reflects the duration of activities required to complete a project along with the resources allocated to each activity. The resource allocation details can also be determined from Gantt chart to check if any resource required to complete the project is being over burdened with work or has to work longer than required duration. The Gantt chart also helps to display the activities that are on critical path to determine the shortest path for the project with longest duration. Hence, the Gantt chart being prepared for the project by scheduling of activities has been presented as below:
References
Badewi, A., 2016. The impact of project management (PM) and benefits management (BM) practices on project success: Towards developing a project benefits governance framework. International Journal of Project Management, 34(4), pp.761-778.
Binder, J., 2016. Global project management: communication, collaboration and management across borders. Routledge.
Chih, Y.Y. and Zwikael, O., 2015. Project benefit management: A conceptual framework of target benefit formulation. International Journal of Project Management, 33(2), pp.352-362.
Daniel, P.A. and Daniel, C., 2018. Complexity, uncertainty and mental models: From a paradigm of regulation to a paradigm of emergence in project management. International Journal of Project Management, 36(1), pp.184-197.
Fernandes, G., Ward, S. and Araújo, M., 2015. Improving and embedding project management practice in organisations—A qualitative study. International Journal of Project Management, 33(5), pp.1052-1067.
Fleming, Q.W. and Koppelman, J.M., 2016, December. Earned value project management. Project Management Institute.
Harrison, F. and Lock, D., 2017. Advanced project management: a structured approach. Routledge.
Heagney, J., 2016. Fundamentals of project management. AMACOM Div American Mgmt Assn.
Heldman, K., 2018. PMP: project management professional exam study guide. John Wiley & Sons.
Hornstein, H.A., 2015. The integration of project management and organizational change management is now a necessity. International Journal of Project Management, 33(2), pp.291-298.
JOSEPH. PHILLIPS, P.M.P., CBAP, I. and PMP, C., 2018. PMP PROJECT MANAGEMENT PROFESSIONAL STUDY GUIDE. McGraw-Hill Education.
Joslin, R. and Müller, R., 2015. Relationships between a project management methodology and project success in different project governance contexts. International Journal of Project Management, 33(6), pp.1377-1392.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.
Kerzner, H., 2017. Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons.
Kerzner, H., 2018. Project management best practices: Achieving global excellence. John Wiley & Sons.
Leach, L.P., 2014. Critical chain project management. Artech House.
Martinelli, R.J. and Milosevic, D.Z., 2016. Project management toolbox: tools and techniques for the practicing project manager. John Wiley & Sons.
Mir, F.A. and Pinnington, A.H., 2014. Exploring the value of project management: linking project management performance and project success. International journal of project management, 32(2), pp.202-217.
Nicholas, J.M. and Steyn, H., 2017. Project management for engineering, business and technology. Taylor & Francis.
Portny, S.E., 2017. Project management for dummies. John Wiley & Sons.
Riol, H. and Thuillier, D., 2015. Project management for academic research projects: balancing structure and flexibility. International Journal of Project Organisation and Management, 7(3), pp.251-269.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Serra, C.E.M. and Kunc, M., 2015. Benefits realisation management and its influence on project success and on the execution of business strategies. International Journal of Project Management, 33(1), pp.53-66.
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.
Too, E.G. and Weaver, P., 2014. The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), pp.1382-1394.
Turner, R., 2016. Gower handbook of project management. Routledge.
Essay Writing Service Features
Our Experience
No matter how complex your assignment is, we can find the right professional for your specific task. Contact Essay is an essay writing company that hires only the smartest minds to help you with your projects. Our expertise allows us to provide students with high-quality academic writing, editing & proofreading services.
Free Features
Free revision policy
$10Free bibliography & reference
$8Free title page
$8Free formatting
$8How Our Essay Writing Service Works
First, you will need to complete an order form. It's not difficult but, in case there is anything you find not to be clear, you may always call us so that we can guide you through it. On the order form, you will need to include some basic information concerning your order: subject, topic, number of pages, etc. We also encourage our clients to upload any relevant information or sources that will help.
Complete the order form
Once we have all the information and instructions that we need, we select the most suitable writer for your assignment. While everything seems to be clear, the writer, who has complete knowledge of the subject, may need clarification from you. It is at that point that you would receive a call or email from us.
Writer’s assignment
As soon as the writer has finished, it will be delivered both to the website and to your email address so that you will not miss it. If your deadline is close at hand, we will place a call to you to make sure that you receive the paper on time.
Completing the order and download