Project Management Plan For Online Ticket Booking System

Desired Area of Impact

Desired Area of Impact: Based on priorities, project area of impact is mentioned here over five different areas such as strategy, customer, financial, operational, and social. As per provided case study of RLAS, the order is Operational, Customer, Social, Strategy, and Financial. 

Project Values: As per case study, RALS project can improve and provide more efficiency in process. Client wanted to increase performance and improve efficiency over the entire ticket booking process. Therefore, the project can bring ‘better’ and ‘faster’ value in project as outcome is developed.

Appropriate Metric: Chosen metrics are: 1) ROI achievement of minimum 80% of the investment budget, 2) completion of activities before planned date, and 3) achieving 110% workload target at the end of the month for workers.    

Appropriate Timeframe: Target metric is limited to six months time; the targets should be achieved after six months to the implementation. Stakeholders should achieve their targets once, the project closure is reached.   

Summary MOV: MOV statement is as following:

“The project will be successful if every stakeholder can achieve 110% of workload in each month, finish work before planned date and after six months, if the outcome provides more than 70% ROI; the project has desired area of interest as Operational, Customer, Social, Strategy, and Financial and it can bring ‘better’ and ‘faster’ value for the organization.” 

New online ticket booking system should be developed and sale process should be implemented in such a way so that delay can be reduced. Crowd management can be performed; and proper alignment of sale can be performed. These were the scope of the project along with the major outcomes of the project. List of resource requirements are shown as following:

                                                                                     (Source: Created by author)

The activity scheduling is performed in Gantt chart in MS project software. To achieve proper allocation of time and activities, the scheduling table is prepared with all resources included. Furthermore, the work breakdown structure is prepared from the scheduled Gantt chart.

                                                                                                   (Source: Created by author)

Project Values

                                                                                             (Source: Created by author)

                                                                                               (Source: Created by author)

Risk analysis and planned risk management approach is to be followed for maintaining risk mitigation process. The risks are identified based on some certain assumptions;

1. Firstly, the project will be completed before the planned date
2. Secondly, the MOV will be approved from administration and managing authority
3. Thirdly, the stakeholders and employees does not require training for working in new system
4. Finally, the project will be completed within allocated budget

Risk Management Plan: Based on the scenario of project charter, MOV, and assumptions; some risks are identified, analyzed, and certain mitigation plan is identified. The identified risks are mentioned primarily;

Approval of MOV: The MOV may not be approved; it is dependent over management decision. In case they find it difficult to meet MOV requirements based on time, money and resource terms; they can deny the MOV. In this situation, the project needs to start afresh with new MOV document preparation. This risk is considered as having almost certain severity though it has low likelihood. Therefore, the mitigation plan should be formulated in low priority.

Budget risk: The project has some certain chances or tendencies of overrunning the allocated budget. Therefore, the managing authority should consider contingency planning for adjusting budget during project timeline. This risk is considered as having catastrophic severity though it has high likelihood. Therefore, the mitigation plan should be formulated in higher priority. 

Training requirements: The existing stakeholders and employees in RALS require some days training for working in the new system. Therefore, some extra expense should be spent regarding this agenda. This risk is considered as having medium severity though it has low likelihood. Therefore, the mitigation plan should be formulated in low priority.

Timeline risk: The project may not be completed before the planned date; may need some extra weeks or month’s time. Therefore, the project manager needs to consider extra slack for the entire project to complete with all deliverables. This risk is considered as having medium severity though it has medium likelihood. Therefore, the mitigation plan should be formulated in medium priority.

Quality management statement is prepared as:

“We hereby declare that we aimed to develop online ticket booking system for RALS committee and we will provide shear quality in all functionalities as collected and analyzed prior to project initiation phase.” 

1. Makes sure that the product is in-line with the organizational policies and strategies
2. Checks about proper automation
3. Ensures about proper testing tools
4. Ensures testing process in par with scheduled timeline

1. Identifies about insider flaws such as testing bugs
2. Indentifies about application functionality defects

Annotated Bibliography is in the appendix.

Closure checklist: The closure checklist should include some major activities such as stakeholder sign-out, contract sign-out, evaluation plan preparation, preparing documentation, and performance reviewing.

Evaluation Plan: Evaluation plan should involve some proper criteria such as performance, meeting requirements, completion within time, and achieving higher-level deliverables with quality.     

Besner, C., & Hobbs, B. (2012). An empirical identification of project management toolsets and a comparison among project types. Project Management Journal, 43(5), 24-46.

Besner, C., & Hobbs, B. (2013). Contextualized project management practice: A cluster analysis of practices and best practices. Project Management Journal, 44(1), 17-34.

Cook, D., Brown, D., Alexander, R., March, R., Morgan, P., Satterthwaite, G., & Pangalos, M. N. (2014). Lessons learned from the fate of AstraZeneca’s drug pipeline: a five-dimensional framework. Nature reviews. Drug discovery, 13(6), 419.

Crawford, J. K. (2014). Project management maturity model. CRC Press.

Marcelino-Sádaba, S., Pérez-Ezcurdia, A., Lazcano, A. M. E., & Villanueva, P. (2014). Project risk management methodology for small firms. International Journal of Project Management, 32(2), 327-340.

Martinelli, R. J., & Milosevic, D. Z. (2016). Project management toolbox: tools and techniques for the practicing project manager. John Wiley & Sons.

McLeod, L., Doolin, B., & MacDonell, S. G. (2012). A perspective?based understanding of project success. Project Management Journal, 43(5), 68-86.

Serra, C. E. M., & 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), 53-66.

Order an Essay Now & Get These Features For Free:

Turnitin Report

Formatting

Title Page

Citation

Outline

Place an Order