Answer:

Part 1: Measurable Organizational Goal

 Part 1: Measurable organizational goal

(a) Measurable organization value is generally considered as one of the significant goal of the project that is mainly used for elaborating the value that is brought within the project with the help of various project team members.

(b) The project plan of online ticketing system assists in delivering some of the values which are as follows:

Faster: The response time between the clients as well as RALS decreases which enhances the speed of organizational operations as well as functions.

Better: The customers of RALS can be able to receive proper facility of booking as well as payment thus it can be analyzed that due to the implementation of online ticketing system within RALS, the customer service of the organization can be easily improved.

Cheaper: The organization implements online ticketing system for providing cheaper means in order to manage the organizational operation as the newly implemented system assists in reducing the operation cost of RALS.

Part 2: Scope management plan

(a) The in-scope as well as out-scope of the project are as follows:

In-scope: The project in-scope includes:

• Implementation of ticketing system for customers
• Boosting financial revenue of the organization
• Helps in providing the opportunity of booking and payment irrespective of the place to the customers

Out-scope: The project out-scope includes:

• Proper details of the materials are not provided
• Information about suppliers is absent

(b) Procedure of scope management

The procedures that are generally used within the project in order to manage the project scope are elaborated below:

  Collecting proper information about project scope: It is quite important to collect proper information about scope of the project in order to complete the project as per scope.

 Proper communication: Proper communication must be present between the team members as well as higher authorities so that the scope of the project can be easily managed.

Tracking project activities: It is very much necessary to track all the activities of the project in order to complete the entire project within estimated time and budget. This assists in managing the scope of the project.

(c) Project resources

  The resources that are utilized in the project are as follows:

Human resources: The people who are associated with the implementation of online ticketing system are as follows:

Resource Name	Std. Rate
Project manager	$45.00/hr
Project planner	$40.00/hr
Project developer	$35.00/hr
System tester	$35.00/hr
Financial manager	$30.00/hr
Human resource manager	$35.00/hr
Technical engineer	$35.00/hr
Risk analyst	$30.00/hr

Software requirements: The software requirements of the project include reporting tool, management tool, communication tool and more.

Hardware requirements: The hardware that is needed within the project includes processor, backup system, data storage and more.

Facility requirement: The project manager must create teams in order to execute the project as per the assumed time and budget.

Others: The workers of the organization must be provided with proper facility of training in order to complete the entire project effectively.

Part 3: Schedule and work breakdown structure

Part 2: Scope Management Plan

(a) Project Milestone

Task Name	Completion date
Milestone 1: Completion of initiation phase	Thu 2/22/18
Milestone 2: Completion of planning phase	Thu 3/8/18
Milestone 3: Completion of designing phase	Wed 3/28/18
Milestone 4: Completion of development phase	Tue 4/10/18
Milestone 5: Completion of testing phase	Mon 4/30/18
Milestone 6: completion of implementation phase	Mon 5/28/18
Milestone 7: Closure phase completion	Thu 5/31/18

(b) Project activities

                                                  

(c) Resources of the project

                                                    

(d)  Time estimation

Task Name	Duration	Start	Finish
Online ticket booking system in RALS	91 days	Mon 1/22/18	Mon 6/4/18
Initiation phase	23 days	Mon 1/22/18	Thu 2/22/18
Creating business case	6 days	Mon 1/22/18	Tue 1/30/18
Identifying project requirements	5 days	Wed 1/31/18	Tue 2/6/18
Analyzing feasibility of the project	4 days	Wed 2/7/18	Mon 2/12/18
Creating project charter	3 days	Tue 2/13/18	Thu 2/15/18
Hiring project team members	5 days	Fri 2/16/18	Thu 2/22/18
Milestone 1: Completion of initiation phase	0 days	Thu 2/22/18	Thu 2/22/18
Planning phase	26 days	Fri 2/23/18	Wed 4/4/18
Creating plan of the project	5 days	Fri 2/23/18	Thu 3/1/18
Creating plan for managing resources	6 days	Fri 2/23/18	Fri 3/2/18
Financial plan	4 days	Fri 3/2/18	Wed 3/7/18
development of project management plan	5 days	Fri 3/2/18	Thu 3/8/18
Quality management plan	6 days	Fri 3/16/18	Fri 3/23/18
Assigning works to project team members	6 days	Mon 3/26/18	Wed 4/4/18
Developing communication plan	5 days	Thu 3/8/18	Thu 3/15/18
Milestone 2: Completion of planning phase	0 days	Thu 3/8/18	Thu 3/8/18
Design phase	36 days	Fri 3/9/18	Thu 5/3/18
Development of project design	7 days	Thu 3/29/18	Tue 4/10/18
Creating use case	6 days	Fri 3/9/18	Mon 3/19/18
Creating class diagram for the ticketing system	8 days	Wed 4/11/18	Fri 4/20/18
designing interface for the system	7 days	Tue 3/20/18	Wed 3/28/18
Designing of phase contingency for the project	8 days	Mon 4/23/18	Thu 5/3/18
Creating system prototype	5 days	Mon 4/23/18	Mon 4/30/18
Milestone 3: Completion of designing phase	0 days	Wed 3/28/18	Wed 3/28/18
Development phase	34 days	Thu 3/29/18	Fri 5/18/18
Coding	6 days	Fri 5/4/18	Fri 5/11/18
Inserting data with database	5 days	Mon 5/14/18	Fri 5/18/18
Project re-estimation	7 days	Thu 3/29/18	Tue 4/10/18
Connecting database with the online ticketing system	6 days	Thu 3/29/18	Mon 4/9/18
Milestone 4: Completion of development phase	0 days	Tue 4/10/18	Tue 4/10/18
Testing phase	24 days	Wed 4/11/18	Tue 5/15/18
Making development checklist	8 days	Wed 4/11/18	Fri 4/20/18
Interface testing	7 days	Mon 4/23/18	Wed 5/2/18
Unit testing	5 days	Mon 4/23/18	Mon 4/30/18
User acceptance testing	6 days	Tue 5/8/18	Tue 5/15/18
System testing	5 days	Thu 5/3/18	Wed 5/9/18
Milestone 5: Completion of testing phase	0 days	Mon 4/30/18	Mon 4/30/18
Implementation phase	20 days	Tue 5/1/18	Mon 5/28/18
Installation of the system	6 days	Thu 5/10/18	Thu 5/17/18
System implementation checking	7 days	Thu 5/10/18	Fri 5/18/18
Training	5 days	Tue 5/1/18	Mon 5/7/18
Providing proper facility of user testing	7 days	Fri 5/18/18	Mon 5/28/18
System handover	5 days	Tue 5/8/18	Mon 5/14/18
Milestone 6: completion of implementation phase	0 days	Mon 5/28/18	Mon 5/28/18
Closure phase	15 days	Tue 5/15/18	Mon 6/4/18
Review of post project	6 days	Tue 5/15/18	Tue 5/22/18
Re-assigning project resources	5 days	Tue 5/29/18	Mon 6/4/18
Stakeholder sign off	3 days	Tue 5/29/18	Thu 5/31/18
Documentation	4 days	Wed 5/23/18	Mon 5/28/18
Milestone 7: Closure phase completion	0 days	Thu 5/31/18	Thu 5/31/18

(e) Budget

Budget calculation

Resources	Cost
Human resources (as per Gantt chart)	$80,280.00
Fringe 20%	$16,056.00
Total cost of human resource	$96,336.00
Material cost	$15,000.00
Training cost	$12,000.00
Total budget of the project	$123,336

Time budget

                                                 

                                                                Figure 3: Time phase budget

                                                                  (Source: Created by Author)

Part 4: Project risk analysis and plan

(a) Assumptions

The assumptions which are made within the project are as follows:

• The entire project will be successfully executed within the budget that is estimated
• The project will be completed within 91 days
• The system which will be developed helps in resolving the organizational issues and assists in providing proper facilities to the customers.

(b) Project risks and management strategy

Risks	Description	Impact	Probability	Responsible person	Mitigation strategies
Improper interface testing	If interface testing is not done appropriately then the users of the project may face number of challenges as well as issues while using it.	Medium	Low	Tester	It is quite important to undertake system interface testing before installation so that the users does not face any issues or challenges.
Inappropriate estimation of budget	If the project budget is not estimated after analyzing the market price of various resources then it will be quite difficult to complete the entire project within estimated budget as well as time.	High	High	Financial manager	It is very much necessary to estimate the project budget after analyzing the market prices in order to estimate budget accurately.
Inappropriate allocation of resources	If project resources are not allocated properly then the project managers faces difficulty in executing the entire project within the assumed time.	High	Medium	Resource manager	It is very much necessary to allocate the resources properly within the project for successfully completing the project within time.
Inappropriate training facility	Due to improper training facility, the project team members may face difficulty in completing the project.	High	High	Human resource manager	Proper facility of training must be providing to the project team members so that they can be able to complete the project successfully.
Improper time estimation	As the project managers of the project does not have proper experience of managing project they estimated time for implementing the online ticketing system is found to be inaccurate.	High	High	Project manager	Experienced project managers must be hired within the project.

Part 5: Quality management plan

(a) Statement on quality management

The organization RALS helps in providing proper facility of online booking as well as payment to the customers with the help of online ticketing system. It is identified that with the help of the newly implemented system the customers can book their tickets as well as can be able to complete the payment procedure from anywhere irrespective of the place and time. The system also resolves the problem of the customers that they face due to the manual procedure of ticket buying. In addition to this, it is identified that the organization provides proper customer experiences so that more of customers get attracted due to the facilities that is provided by RALS.

(b) Description of activities for maintaining project quality

The project team of RALS generally implements for ensuring project quality. This can be elaborated with the help of two testing methods which are elaborated below:

Part 3: Schedule and Work Breakdown Structure

Verification testing: Verification testing method is generally performed in order to verify that whether the requirements of the project can be met by running the software or not. The outputs the development stages are generally subjected to verification in order to check against the various input specification of the project. Additionally, it is analyzed that verification procedure generally comprises of all the activities that are helpful in producing proper quality of outcome.

Validation testing: Validation testing method is undertaken for elaborating the system within its development phase so that it can be easily analyzed that all the project requirements are met. Furthermore, the aim of the system is to check the accuracy of the final work of the project.

Part 6. Closure and evaluation

(a) Annotated Bibliography

Provided in the appendix.

(b) Developing closure checklist

Task Name	Resource Names	Signature
Creating business case	Project manager, Project planner
Identifying project requirements	Project developer
Hiring project team members	Human resource manager, Project manager
Creating plan for managing resources	Human resource manager
Financial plan	Financial manager
development of project management plan	Risk analyst
Quality management plan	Project manager, Risk analyst
Developing communication plan	Human resource manager, Project manager
Creating use case	Project developer
Creating class diagram for the ticketing system	Project developer
designing interface for the system	Project developer, Technical engineer
Designing of phase contingency for the project	Project developer
Coding	Project developer
Inserting data with database	Project developer
Project re-estimation	Human resource manager, System tester
Connecting database with the online ticketing system	Technical engineer, Financial manager
Interface testing	System tester
Unit testing	Risk analyst
User acceptance testing	Human resource manager, Risk analyst
Installation of the system	Technical engineer
System implementation checking
Training	Human resource manager, Project planner
Providing proper facility of user testing	Project planner
Review of post project	Project manager
Re-assigning project resources	Project manager
Stakeholder sign off	Human resource manager

                                                                                                                                                                                                                                                      

(c) Project evaluation

The project will be evaluated in context to MOV with the help of procedure that are provided below:

• Determining different areas of impact within the project
• Identifying value of the project
• Development of appropriate metric within the project
• Setting appropriate project timeframe
• Identifying and getting agreement from different project stakeholders

Conforto, E. C., Salum, F., Amaral, D. C., da Silva, S. L., & de Almeida, L. F. M. (2014). Can agile project management be adopted by industries other than software development?. Project Management Journal, 45(3), 21-34.

Fleming, Q. W., &Koppelman, J. M. (2016, December). Earned value project management. Project Management Institute.

Joslin, R., & 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), 1377-1392.

Kasemsap, K. (2016). The roles of information technology and knowledge management in project management metrics. Project Management: Concepts, Methodologies, Tools, and Applications: Concepts, Methodologies, Tools, and Applications, 229.

Kerzner, H., &Saladis, F. P. (2017). Project management workbook and PMP/CAPM exam study guide. John Wiley & Sons.

Laudon, K. C., & Laudon, J. P. (2016). Management information system. Pearson Education India.

Lientz, B., & Rea, K. (2016). Breakthrough technology project management. Routledge.

Nicholas, J. M., & Steyn, H. (2017). Project management for engineering, business and technology. Taylor & Francis.

Schwalbe, K. (2015). Information technology project management. Cengage Learning.

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.

Serrador, P., & Turner, R. (2015). The relationship between project success and project efficiency. Project Management Journal, 46(1), 30-39.

Sharbatoghlie, A., &Sepehri, M. (2015). An Integrated Continuous Auditing Project Management Model (CAPM). In 4th International Project Management Conference.

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

Turk, D., France, R., &Rumpe, B. (2014). Assumptions underlying agile software development processes. arXiv preprint arXiv:1409.6610.

Vareilles, E., Coudert, T., Aldanondo, M., Geneste, L., &Abeille, J. (2015). System design and project planning: Model and rules to manage their interactions. Integrated Computer-Aided Engineering, 22(4), 327-342.

Verzuh, E. (2015). The fast forward MBA in project management. John Wiley & Sons.

Walker, A. (2015). Project management in construction. John Wiley & Sons.