IT Project Management Techniques, Skills, And Tools In The Industry

Short summary of the project objectives

The paper mainly reflects on the Riverina Agricultural and Lifestyle Show which was mainly established in the year 2000 by founding business BT & Sons Farming Equipment. It is found that RALS is a 3-year event in the month of November and it generally helps in showcasing local business, equipment suppliers as well as various types of lifestyle products. As RALS have grown significantly and therefore now it is managed by one of the community committee. It is identified that currently the tickets are purchased at the gates of RALS which generally causes delays and it is found that when the crowd are large in number then it become quite difficult to check all the tickets properly. In order to improve the entire process, it is very much necessary to develop a ticketing system. It is found that the new ticketing system will be successfully completed within the time period of 3 months by utilizing budget of around $

  The objectives of the project are listed below:

• To develop a ticketing system for Riverina Agricultural Lifestyle Show
• To resolve the problem that generally occurs due to the use of manual process for selling tickets
• To install barcodes as well as QR codes that must be used on ticket

The in-scope of the project includes:

• Development of a ticketing system
• Procedure for e-tickets generation
• Installation of barcodes or QR codes
• Cost estimation for system development
• Detailed reporting

The out-scope of the project includes:

• Facility of training is not given to the team members
• Information related with the project suppliers is not given

Measurable organizational value is the overall goal of the project that is generally measured for achieving success. It is found that in the IT field, it must be aligned with the organizational objective, goals as well as mission of the organization. It is found that measurable organizational in context to different factors are elaborated in the table below.

Rank	Factor	Description
1	Customer	It is analyzed that the number of customers of the organization must increase by 20% due to use of online ticketing system.
2	Financial	It is quite necessary to enhance the financial revenue of the organization with the increment in the sales of ticket by 15%
3	Social	It is quite important to reach to a greater number of people for expanding the business of RAILS.
4	Strategy	It is quite necessary to utilize proper strategy of management so that the development of ticketing system can be finished on time.
5	Operational	Improvement must be reflected in the operations of RAILS due to the development of ticketing system.

 The stakeholders who are mainly associated with the development of online ticketing system are generally analyzed by identifying their interest and power in the project. The table that is provided below showcases the power and interest of the project stakeholders who are mainly associated with the project.

Stakeholders	Interest	Power
Project manager	High	High
Project planner	High	Low
Project developer	High	Low
System tester	High	Low
Financial manager	Low	Low
Human resource manager	Low	Low
Technical engineer	High	Low
Risk analyst	Low	Low

Figure 1: Stakeholder Matrix

(Source: Created by Author)

The communication plan that is developed for communicating with the project team as well as with the high authorities of the organization is reflected below:

Audience	Messages	Media	Frequency	Timing	Responsible
Team members	The objectives as well as goals of the project are generally discussed so that the project team members can be able to get proper idea about the project.	Team meeting	Once	1p.m	Project manager
Project team leaders	The team members generally discuss on the problems that they generally face within the project so that they can get solution for their problem.	Team meeting, Email	Whenever needed	11.am	Project team members
Project manager	The team leaders generally discussed about the status as well as progress of the project with the project manager.	Face to face, conference	Monthly	1.pm	Team leader

The assumptions that are generally made include:

• It is assumed that the entire project will be completed within 90 days
• The risks analysis as well as identification are helpful in resolving the risks as well as challenges.
• It is assumed that the entire project will be finished within the budget that is approved.

The risks that are associated with the project are generally identified, analyzed as well as proper strategy of managing that risk is provided in the table below:

Serial no	Risk identification	Description	Analysis of the risk	Involved team member	Mitigation
Impact	Probability
1	Inappropriate design	It is found that the design of the online ticketing system is not created properly and as a result the developers are facing issue in finishing the project.	High	High	Designer	It is very much necessary to make the design of the online ticketing system properly so that the entire project can get completed on time.
2	Technical issue	Improper connection of database with the new system	High	Medium	Database administrator	It can be resolved by hiring experienced team members as well as designers within the project.
3	Schedule slippage	It is found that if the project is not managed properly then it can cause number of issues and challenges in finishing the project on time.	High	High	Project manager	It is quite necessary to track the project quite effectively so that the entire project can be completed on time.
4	Budget shortfall	If the resources of the project are not managed properly then there is high chance of	High	Medium	Financial manager	It is found that the problem of budget shortfall can be resolved if the resources of the project can be managed effectively.
5	Inexperienced team member	The team members who are not experienced faces number of issues in finishing the project.	Medium	Medium	Hr manager	Proper facility of training must be provided to the team members so that they can finish project work effectively.

The table that is provided below reflects on the project milestones, tasks that are required to be performed, resources as well as duration of the project.

WBS	Task Name	Duration	Start	Finish	Resource Names
0	Online ticket booking system in RALS	90 days	Tue 04-12-18	Mon 08-04-19
1	Initiation phase	23 days	Tue 04-12-18	Thu 03-01-19
1.1	Business case development	6 days	Tue 04-12-18	Tue 11-12-18	Project manager, Project planner
1.2	Project requirements identification	5 days	Wed 12-12-18	Tue 18-12-18	Project developer
1.3	Feasibility analysis	4 days	Wed 19-12-18	Mon 24-12-18	Financial manager, Human resource manager, Project manager
1.4	Charter development	3 days	Tue 25-12-18	Thu 27-12-18	Project manager, Project planner
1.5	Project team members recruitment	5 days	Fri 28-12-18	Thu 03-01-19	Human resource manager, Project manager
1.6	Milestone 1: Completion of project initiation phase	0 days	Thu 03-01-19	Thu 03-01-19
2	Planning phase	27 days	Fri 04-01-19	Mon 11-02-19
2.1	Development of project plan	4 days	Fri 04-01-19	Wed 09-01-19	Project planner
2.2	Development of resource management plan	6 days	Fri 04-01-19	Fri 11-01-19	Human resource manager
2.3	Project financial plan	4 days	Thu 10-01-19	Tue 15-01-19	Financial manager
2.4	Development of project plan	5 days	Thu 10-01-19	Wed 16-01-19	Risk analyst
2.5	Development of quality plan	6 days	Fri 25-01-19	Fri 01-02-19	Project manager, Risk analyst
2.6	Assigning work	6 days	Mon 04-02-19	Mon 11-02-19	Project manager
2.7	Communication plan	5 days	Wed 16-01-19	Tue 22-01-19	Human resource manager, Project manager
2.8	Milestone 2: Completion of planning phase	0 days	Wed 16-01-19	Wed 16-01-19
3	Design phase	37 days	Thu 17-01-19	Fri 08-03-19
3.1	Project design	7 days	Wed 06-02-19	Thu 14-02-19	Project developer
3.2	Developing use case	6 days	Thu 17-01-19	Thu 24-01-19	Project developer
3.3	Creating class diagram	8 days	Fri 15-02-19	Tue 26-02-19	Project developer, Materials [1]
3.4	Designing interface	7 days	Fri 25-01-19	Mon 04-02-19	Project developer, Technical engineer
3.5	Designing phase contingency	8 days	Wed 27-02-19	Fri 08-03-19	Project developer
3.6	Development of prototype	5 days	Wed 27-02-19	Tue 05-03-19	Technical engineer
3.7	Milestone 3: Completion of designing phase	0 days	Mon 04-02-19	Mon 04-02-19
4	Development phase	37 days	Tue 05-02-19	Wed 27-03-19
4.1	Coding	6 days	Mon 11-03-19	Mon 18-03-19	Project developer
4.2	Data insertion within database	5 days	Thu 21-03-19	Wed 27-03-19	Project developer
4.3	Re-estimation of project	7 days	Tue 05-02-19	Wed 13-02-19	Human resource manager, System tester
4.4	Connection of database with online ticketing system	6 days	Tue 05-02-19	Tue 12-02-19	Technical engineer, Financial manager
4.5	Milestone 4: Completion of development phase	0 days	Wed 13-02-19	Wed 13-02-19
5	Testing phase	24 days	Thu 14-02-19	Tue 19-03-19
5.1	Checklist development	8 days	Thu 14-02-19	Mon 25-02-19	Project manager, Project planner
5.2	Testing of interface	7 days	Tue 26-02-19	Wed 06-03-19	System tester
5.3	Unit testing	5 days	Tue 26-02-19	Mon 04-03-19	Risk analyst
5.4	User acceptance testing	6 days	Tue 12-03-19	Tue 19-03-19	Human resource manager, Risk analyst
5.5	System testing	5 days	Thu 07-03-19	Wed 13-03-19	System tester
5.6	Milestone 5: Completion of testing phase	0 days	Mon 04-03-19	Mon 04-03-19
6	Implementation phase	20 days	Tue 05-03-19	Mon 01-04-19
6.1	System installation	6 days	Thu 14-03-19	Thu 21-03-19	Technical engineer
6.2	Checking of system implementation	7 days	Thu 14-03-19	Fri 22-03-19	Additional cost [1]
6.3	Barcode installation	5 days	Tue 05-03-19	Mon 11-03-19	Human resource manager, Project planner
6.4	Proper facility of user testing	7 days	Fri 22-03-19	Mon 01-04-19	Project planner
6.5	System handover	5 days	Tue 12-03-19	Mon 18-03-19	Project manager
6.6	Milestone 6: completion of implementation phase	0 days	Mon 01-04-19	Mon 01-04-19
7	Closure phase	15 days	Tue 19-03-19	Mon 08-04-19
7.1	Project review	6 days	Tue 19-03-19	Tue 26-03-19	Project manager
7.2	Re-assigning project resources	5 days	Tue 02-04-19	Mon 08-04-19	Project manager
7.3	Stakeholder sign off	3 days	Tue 02-04-19	Thu 04-04-19	Human resource manager
7.4	Documentation	4 days	Wed 27-03-19	Mon 01-04-19	Project manager
7.5	Milestone 7: Closure phase completion	0 days	Thu 04-04-19	Thu 04-04-19

 The leadership qualities that are needed by the project manager are generally elaborated below:

Team management: Project managers must have the quality of team management for successful project. It is found that a successful project manager generally helps in directing as well as coordinating the team members by resolving the conflicts as well as by setting project milestones.

Creativity: It is found that the ability of creating something new must be present within the project manager so that they can be able to promote the initial plan of the project.

Honesty: Honesty is considered as one of the integral charteristics of the project leader. It is found that they have this quality while setting benchmarks as well as standards for the project team.

 The responsibilities of the project team members are generally elaborated below:

• The project managers are mainly responsible of planning as well as controlling the entire project successfully.
• They generally involve within the preparation as well as maintenance of the project as needed
• Monitoring the overall project progress by utilizing proper resources as well as corrective action when needed
• Reporting with the help of agreed lines on the project progress with the help of reports
• Maintenance as well as awareness of various type of potential dependencies with other projects.
• Identification as well as getting proper support that is generally required for the management, planning as well as control of the project
• Conduction of proper project evaluation by assessing the procedure of project management
• Management of project risks including different types of contingency plan that is associated with the project. 

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), 761-778.

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.

Hornstein, H. A. (2015). The integration of project management and organizational change management is now a necessity. International Journal of Project Management, 33(2), 291-298.

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.

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

Kerzner, H. (2017). Project management metrics, KPIs, and dashboards: a guide to measuring and monitoring project performance. John Wiley & Sons.

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.

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

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.

Svejvig, P., & Andersen, P. (2015). Rethinking project management: A structured literature review with a critical look at the brave new world. International Journal of Project Management, 33(2), 278-290.

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.

Too, E. G., & Weaver, P. (2014). The management of project management: A conceptual framework for project governance. International Journal of Project Management, 32(8), 1382-1394.