Choice of Area of Impact
Choice of Area of Impact: The area of project for the assessment of the impact is to be generally mentioned from different areas, which includes the customer domain, financial sector, social strategy management sector and the strategy for the betterment of the organization. The sector also include the operational sector keeping the organizational work in check. The projects main objective has been defined for the development procedure of an online booking system for the RAILS. Thus, the required operational sectors include the sectors of operational, strategy, customers, social and financial. These sectors will be helpful for the implementation procedure of the sector and keep the project development and the follow up of the project on track.
Project Values: For the development of the project it has been found that the dependence of the working point of view of the RAILS along with the requirements of the Globex, the project has the objective of providing the organization with a faster as well as the objective of providing a better value within thee working environment of the organization. The organization has the idea for the improvement of the ticketing system for the world with the implementation of the rostering system. The rostering system is to be implemented within the show. This has been thought due to the problem, which the customers face while booking tickets. The customers always want to have the faster access to the process. The user’s wants to keep the time they spend of the process of purchasing of the tickets to be short and the process should be simple. Another requirement for the project is to effectively manage the crowd in times of rush hours at the ticket counters.
Appropriate Metric: It has been found that the definition of the metrics is to be selected based on certain points as follows:
- Following of the timeline: it is important for the project manager to keep a track of the project timeline in order to deliver the complete project on time.
- Over shooting of production: it is a positive feedback from the working community for the production to overshoot to a factor of 110 % of the original production so that they can excel in their field of work.
- Positive Return of Investment: For the project to become successful in the market, the best metric to follow by the developers is to follow the Return of Investment metric of the project. The Return of Investment metric is the earned back profit from in ratio to the amount of revenue that was invested in the project.
Appropriate Timeframe: The target, which has to be set before, the starting of the project has to be set for a period of six months. The target metric needs to be reached within the period of six months from the date the project has been completed and launched. At the end of the project, it is important for the organization to calculate the metric for the stakeholders of the project. It is important for the organization as well as the project to assess the proper achievement of the stakeholders. This has to be done in a short time period, as this metric will help in the assessment of the performance of the project easily.
Project Values
To summarize the Measurable Organizational Value of the project it can be said that the following of the timeline and the project assessment plan would help the project to be on track for the achievement of the target based on the objectives, which has been set forward for the project.
The scope that has been developed for the development of the project is to develop an online ticket booking system with the inclusion of a sales procedure to track the amount of tickets being sold every day. The project has the target of reduction of challenges like management of large crowd, delay in the queues due to high demand of tickets during peak season. During the implementation procedure it has been identified that the process of implementation of the ticketing system for the better operation of the ticketing procedure properly. The requirements for the development of the project has been discussed in the following table:
Type of resources |
Roles of resources |
Responsibilities |
People |
1. Project manager 2.Business analyst 3.Developer 4. Frontend developer 5.Lead analyst 6.Tester |
1. A major portion of the stakeholders is responsible for being directly engaged with the project development procedure. They help the developers throughout the working time line of the project with resources and help which would provide the support to them for the fast completion of the work. They are also responsible for doing proper and valid decision-making techniques, which would help the flow of the project. 2. They are the people who are responsible for producing the periodical documentation of the working progress of the project. The documentation of the project is shared with the stakeholders and other members of the board to let them know about the working progress of the development of the project. 3. They are main brain behind the development of the project. They are the ones who make the decision if the design of the project is to be developed with a certain software or to be developed using some other software. They are able to suggest different architectural changed to the project. They are also responsible for the resolving of issues and problems that might occur during the implementation of the project. 4. They work with the developers to ensure that the backend and the frontend of the project can run together without any hindrance or without the generation of any error. They are responsible for the meeting of the deadlines for the development phase of the project. They are responsible for knowing and checking the working procedure of the database. Apart from all these work, they are also responsible for looking after the proper development of the user interface of the project. If the user interface of the project is not developed with respect to the usability of the project then the user interface has to be changed with respect to the instructions from them. 5. After the complete development of the project the bugs and issue needs to be found out from the project so that the project can be made into one without any bugs. The finding out of such bugs from a project is the work of an analyst. They would estimate the total amount of time and the steps that would be used for the testing of the project to find and notify the developers about the bugs of the project. They are the ones who set out the testing objectives of the project. 6. They work under the guidance of the lead analyst. They help the analyst to find out as many numbers of bugs possible from the project so that they can be removed from the project and a good quality project can be delivered to the client. |
Facilities |
CXA, Angular JS3, CSS3, Java 8 OCp |
A projects needs to be developed with the help of different programming languages who are to be synchronized and connected into one form to make them into a complete project. Thus, for the development of the ticketing system as well as the booking procedure of the project the following list of languages and software’s has been used. |
Technologies |
Deployment as well as the inclusion of the development department |
For the [proper development and the best understanding of the working procedure of the project proper working environments needs to be used with the languages and software so that the project can also be executed to find if it is working or not. Thus the requirement of proper development tools and infrastructure, which is able to provide the backbone of the project is required. These are required for the implementation of the online application for the ticketing system. |
Others |
Training of the members of the team |
For the development of the project, a team of under skilled workers and employees would lead to the failure of the project in an instant. It is thus customary and necessary for the team, which has been compiled to be trained with proper knowledge of the working of the project and to let them know those procedures, which are to be used, and when to use them during the development of the project. |
The main problem of several project failures has been found to be because of the problems of the lack of time management among the team members. Management of time for a large project is essential as the steps requite time to be developed and missing a deadline will result in the late delivery of the project. The management of project is done with the help of a software names Microsoft Project Software. To achieve the best possible method and appropriate allocation of time along the course of development of the project the use of the scheduling table has been used which provides the details of all the resources that are to be used for the project. This would help in the completion of the project successfully and without any delay in the working procedure of the project. Moreover, for the complete understanding of the project steps to be followed by the team members there is the inclusion of a work break down structure, which helps in identifying the steps of the working procedure of the project. A work break down structure is helpful at times when the steps of the project is not understandable from the project Gantt chart.
Task Name |
Duration |
Start |
Finish |
Development of RAILS Project |
190 days |
Tue 10-10-17 |
Mon 02-07-18 |
Project initiating phase |
32 days |
Tue 10-10-17 |
Wed 22-11-17 |
Preparation of project plan |
4 days |
Tue 10-10-17 |
Fri 13-10-17 |
Determination of scope of project |
5 days |
Mon 16-10-17 |
Fri 20-10-17 |
Resource gathering |
4 days |
Mon 23-10-17 |
Thu 26-10-17 |
Requirement analysis |
3 days |
Fri 27-10-17 |
Tue 31-10-17 |
Creating schedule |
4 days |
Wed 01-11-17 |
Mon 06-11-17 |
Development of results |
5 days |
Tue 07-11-17 |
Mon 13-11-17 |
CPM application |
2 days |
Tue 14-11-17 |
Wed 15-11-17 |
cost management techniques applications |
3 days |
Thu 16-11-17 |
Mon 20-11-17 |
Analysis of project performance |
2 days |
Tue 21-11-17 |
Wed 22-11-17 |
Milestone: Completion of the initiation phase |
0 days |
Wed 22-11-17 |
Wed 22-11-17 |
Planning phase of the project |
44 days |
Thu 23-11-17 |
Tue 23-01-18 |
Management of cost |
4 days |
Thu 23-11-17 |
Tue 28-11-17 |
Plan the costing of the project |
5 days |
Wed 29-11-17 |
Tue 05-12-17 |
Develop the plan of the project |
4 days |
Wed 06-12-17 |
Mon 11-12-17 |
Management of time line of the project |
4 days |
Tue 12-12-17 |
Fri 15-12-17 |
Change management of the plan |
5 days |
Mon 18-12-17 |
Fri 22-12-17 |
Budget Evaluation process |
5 days |
Mon 25-12-17 |
Fri 29-12-17 |
Analysis of the budget of the plan |
3 days |
Mon 01-01-18 |
Wed 03-01-18 |
Risk management plan |
3 days |
Thu 04-01-18 |
Mon 08-01-18 |
Risk mitigation plan |
4 days |
Tue 09-01-18 |
Fri 12-01-18 |
Procurement plan |
7 days |
Mon 15-01-18 |
Tue 23-01-18 |
Milestone: Completion of the planning phase |
0 days |
Tue 23-01-18 |
Tue 23-01-18 |
Implementation phase |
89 days |
Wed 24-01-18 |
Mon 28-05-18 |
Development of the Activity |
8 days |
Wed 24-01-18 |
Fri 02-02-18 |
Marketing Strategy |
9 days |
Mon 05-02-18 |
Thu 15-02-18 |
Administration |
8 days |
Fri 16-02-18 |
Tue 27-02-18 |
Testing of the project |
9 days |
Wed 28-02-18 |
Mon 12-03-18 |
UI and UX design |
7 days |
Tue 13-03-18 |
Wed 21-03-18 |
Database design and implementation |
8 days |
Thu 22-03-18 |
Mon 02-04-18 |
Designing of the functionality of project |
9 days |
Tue 03-04-18 |
Fri 13-04-18 |
Testing fot he complete system |
7 days |
Mon 16-04-18 |
Tue 24-04-18 |
Chnages to be made |
9 days |
Wed 25-04-18 |
Mon 07-05-18 |
Use case testing |
8 days |
Tue 08-05-18 |
Thu 17-05-18 |
Quality assessment of the project |
7 days |
Fri 18-05-18 |
Mon 28-05-18 |
Milestone: Completion of implementation phase |
0 days |
Mon 28-05-18 |
Mon 28-05-18 |
Maintenance phase |
20 days |
Tue 29-05-18 |
Mon 25-06-18 |
Database Maintainance |
5 days |
Tue 29-05-18 |
Mon 04-06-18 |
Online application Maintainance |
5 days |
Tue 05-06-18 |
Mon 11-06-18 |
Operation Maintainanace |
5 days |
Tue 12-06-18 |
Mon 18-06-18 |
Training and learning sessions |
5 days |
Tue 19-06-18 |
Mon 25-06-18 |
Milestone: Completion of the maintenance phase |
0 days |
Mon 25-06-18 |
Mon 25-06-18 |
Closure phase of the project |
5 days |
Tue 26-06-18 |
Mon 02-07-18 |
Stakeholder Sign-out |
1 day |
Tue 26-06-18 |
Tue 26-06-18 |
Post implementation review |
2 days |
Wed 27-06-18 |
Thu 28-06-18 |
Closure of Contract |
1 day |
Fri 29-06-18 |
Fri 29-06-18 |
Appraisal of Performance |
1 day |
Mon 02-07-18 |
Mon 02-07-18 |
Milestone: Completion of the closure phase |
0 days |
Mon 02-07-18 |
Mon 02-07-18 |
Figure 1: Gantt chart
Figure 2: Work Breakdown Structure
Any kind of project when proceeded with needs to be assessed with the prospect of risk emergence during the development of the project. Risk can occur at any time during the process of development of the project and should be attended at the very instant it has been found. The process of mitigation of risk has to be prompt and smooth so that minimal amount of resources are damaged by the risk. For the mitigation of risks, two types of methods are followed. The first begin the process of risk management where the team has a set of rules set out before the implementation of the project to follow during the time of risk findings. The second process is the use of risk analysis, which is to be followed when an uncertain risk has surfaced on the project and needs to be removed as soon as possible. The risks of the project are generally based on certain assumptions, which has been discussed below:
- For the risks to be minimized completely the Measurable organizational Value has to be approved from all the higher departments of the project team as well as from the administrative organization of the project.
- The time line, which is to be developed, has to be followed strictly for the timely delivery of the project to the client.
- For a project to be developed a lot of revenue is put in for the project to be delivered within time and within a reasonable cost for the client. Thus, it is important for the developers to follow the budget that has been provided to them for the project to be cost effective and complete it within the budget.
- The final reason for the rising of risk in the development of a project is when the stakeholders and the employees does not follow the system, which has been developed specifically for the project. If the new system is not followed carefully for the project development procedure then the project is surely to run into the problems of risk.
Appropriate Metric
Risk Management Plan: It can be said that a project can be faced with a number of different problems and issues along with challenges, which needs to be overcome with the following of tactics so that there is minimum amount of damage done to the project. The risks has to be mitigated with the help of proper risk mitigation plan, which needs to be developed before the initiation of the project. After thorough evaluation of the project the following list of risks has been identified which might surface during the development of the project:
Budget Risk: It has often been seen that a project over runs its course of working procedures and gets the demand of more money from the client. This is not good for the reputation of the company that has taken up the project. Thus, it is important for the workers to ensure that the project is able to complete within the budget that has been provided to the project. This type of risk has catastrophic severity though the likelihood of this happening is high.
Timeline Risk: It can so often happen that the project timeline to be delayed by one or two days, which at the end of the timeline leads to the fact that the whole project has been delayed and the timeline, was disrupted. This should be kept in check for the project to run smoothly and to provide a good quality project for the following of the timeline. This type of risk has medium severity though the likelihood of this happening is medium.
Training Requirements: The stakeholders of the project along with the employees who will be working for the project RAILS should be made familiarized with the working procedure of the new system. This is the responsibility of the team to make them know about the working of the project or else the project would fall short of men and the project can het delayed. This type of risk has medium severity though the likelihood of this happening is low.
Approval of Measurable Organizational Value: The management of the organization would not easily approve the working of the Measurable Organizational Value because it is often related to the decision of a much higher authority of the organization. Thus, it may become a challenge to meet all the time constraints and the resource constraints for the project if the Measurable Organizational Value is not accepted. This type of risk has certain severity though the likelihood of this happening is low.
Appropriate Timeframe
The process of quality management is prepared for the development of the appropriate ticket booking system on the online basis for the working committee of RAILS. This has been developed for the provision of a proper method of quality sharing and along with this, the functions that are used as a collective foe the analysis of the project before the initiation phase of the project can start.
The process of verification for the activities has been discussed as below:
- To help in the process of taking follow up of the project so that the project is able to follow all the strategies and policies of the organization.
- To help in the checking of the proper automation procedure.
- To help in the process of ensuring proper use of tools for the testing phase.
- To ensure that the test procedures are followed as per the timeline which had been declared during the initiation phase.
The activities of validation have been discussed below:
- To identify about the defects caused due to functionality
- To identify the flaws of the testing bugs and to remove them.
- Markopoulos, J. (2016). Contemporary project management. Hart’s E and P, (June).
This article helps the students to learn about the new project management technologies and methods, which can be implemented in certain, make belief case studies for the course of the study. Once the methods are made known to the students, they would be able to apply them to real life problems in the future. The methods have been developed in accordance to the Project Management Body of Knowledge and has been integrated with the last version of the Microsoft Project 2010.
- Butt, A., Naaranoja, M., & Savolainen, J. (2016). Project change stakeholder communication. International Journal of Project Management, 34(8), 1579–1595. https://doi.org/10.1016/j.ijproman.2016.08.010
This case study has been written for the exploration of the project communication procedures and routines, which will be affecting the stakeholder engagement during the management of changing procedures and the evolving of the culture to follow for the procedures of the project. The result had been found and used to underline the fact that the communication procedure between the stakeholders and the employees of the organization. The theoretical results of the study suggest that the communication process of the project methods requires more attention to let the stakeholders know about the progress of the project.
- Andersen, E. S. (2016). Do project managers have different perspectives on project management? International Journal of Project Management, 34(1), 58–65. https://doi.org/10.1016/j.ijproman.2015.09.007
The report discusses about the perspective of the project management procedures. The paper has the arguing factor of the project management based on the perspective of the project management procedures. The perspective of the task means that the project managers mainly has the focus on the process of delivery of the project on time along with the management of the cost and following the delivery of the quality of the project. The report has a discussion of a conducted survey which revealed that there are different perspective of the project managers which are still prevailing on the minds of managers.
Closure Checklist: The closure checklist has the proper inclusion of all the activities that has been followed during the development of the project with the inclusion of the stakeholder sign off, preparation of the evaluation plan and the contract sigh off. Apart from these, there is the inclusion of the review of the performance of the workers and the project as well as the complete documentation of the working procedure of the project.
Evaluation Plan: The assessment of the evaluation plan has the inclusion of all the criteria’s that were met during the meetings, achievement of the levels of deliverable of the working procedure, meeting of quality of work deliverable and the meeting of the requirements of the project as per the clients wishes.
Andersen, E. S. (2016). Do project managers have different perspectives on project management? International Journal of Project Management, 34(1), 58–65. https://doi.org/10.1016/j.ijproman.2015.09.007
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. https://doi.org/10.1016/j.ijproman.2015.05.005
Badewi, A., & Shehab, E. (2016). The impact of organizational project benefits management governance on ERP project success: Neo-institutional theory perspective. International Journal of Project Management, 34(3), 412–428. https://doi.org/10.1016/j.ijproman.2015.12.002
Butt, A., Naaranoja, M., & Savolainen, J. (2016). Project change stakeholder communication. International Journal of Project Management, 34(8), 1579–1595. https://doi.org/10.1016/j.ijproman.2016.08.010
Chen, H. L., Chen, W. T., & Lin, Y. L. (2016). Earned value project management: Improving the predictive power of planned value. International Journal of Project Management, 34(1), 22–29. https://doi.org/10.1016/j.ijproman.2015.09.008
Flug, J. A., & Nagy, P. (2016). The A3 Quality Improvement Project Management Tool for Radiology. Journal of the American College of Radiology, 13(4), 408–410. https://doi.org/10.1016/j.jacr.2015.12.028
Hyväri, I. (2016). Roles of Top Management and Organizational Project Management in the Effective Company Strategy Implementation. Procedia – Social and Behavioral Sciences, 226, 108–115. https://doi.org/10.1016/j.sbspro.2016.06.168
Type of Resources
Kazan, A. I., & Region, V. (2016). Effective Project Management with Theory of Constraints. Procedia – Social and Behavioral Sciences, 229(March), 96–103. https://doi.org/10.1016/j.sbspro.2016.07.118
Kerzner, H. (2014). Project Management Best Practices: Achieving Global Excellence. Project Management Best Practices: Achieving Global Excellence. https://doi.org/10.1002/9781118835531
Markopoulos, J. (2016). Contemporary project management. Hart’s E and P, (June).
Mir, F. A., & Pinnington, A. H. (2014). Exploring the value of project management: Linking Project Management Performance and Project Success. International Journal of Project Management, 32(2), 202–217. https://doi.org/10.1016/j.ijproman.2013.05.012
Mossalam, A., & Arafa, M. (2016). The role of project manager in benefits realization management as a project constraint/driver. HBRC Journal, 12(3), 305–315. https://doi.org/10.1016/j.hbrcj.2014.12.008
Note, M. (2016). Project Management for Information Professionals. Project Management for Information Professionals. https://doi.org/10.1016/B978-0-08-100127-1.00001-2
Obradovi?, V., Kosti?, S. C., & Mitrovi?, Z. (2016). Rethinking Project Management – Did We Miss Marketing Management? Procedia – Social and Behavioral Sciences, 226, 390–397. https://doi.org/10.1016/j.sbspro.2016.06.203
Padalkar, M., & Gopinath, S. (2016). Six decades of project management research: Thematic trends and future opportunities. International Journal of Project Management, 34(7), 1305–1321. https://doi.org/10.1016/j.ijproman.2016.06.006
Paquin, J. P., Gauthier, C., & Morin, P. P. (2016). The downside risk of project portfolios: The impact of capital investment projects and the value of project efficiency and project risk management programmes. International Journal of Project Management, 34(8), 1460–1470. https://doi.org/10.1016/j.ijproman.2016.07.009
Project Management Institute. (2013). A guide to the project management body of knowledge (PMBOK ® guide). Project Management Institute. https://doi.org/10.1002/pmj.20125
Qazi, A., Quigley, J., Dickson, A., & Kirytopoulos, K. (2016). Project Complexity and Risk Management (ProCRiM): Towards modelling project complexity driven risk paths in construction projects. International Journal of Project Management, 34(7), 1183–1198. https://doi.org/10.1016/j.ijproman.2016.05.008
Rose, K. H. (2016). Project Sponsorship: Achieving Management Commitment for Project Success. Project Management Journal. https://doi.org/10.1002/pmj.21566
Rusare, M., & Jay, C. I. (2015). The project implementation profile: A tool for enhancing management of NGO projects. Progress in Development Studies, 15(3), 240–252. https://doi.org/10.1177/1464993415578976
Salas-Morera, L., Arauzo-Azofra, A., García-Hernández, L., Palomo-Romero, J. M., & Hervás-Martínez, C. (2013). PpcProject: An educational tool for software project management. Computers & Education, 69, 181–188. https://doi.org/10.1016/j.compedu.2013.07.018
Teller, J., & Kock, A. (2013). An empirical investigation on how portfolio risk management influences project portfolio success. International Journal of Project Management, 31(6), 817–829. https://doi.org/10.1016/j.ijproman.2012.11.012
Unger, B. N., Gemünden, H. G., & Aubry, M. (2012). The three roles of a project portfolio management office: Their impact on portfolio management execution and success. International Journal of Project Management, 30(5), 608–620. https://doi.org/10.1016/j.ijproman.2012.01.015
Zwikael, O. (2016). International journal of project management special issue on “project benefit management.” International Journal of Project Management, 34(4), 734–735. https://doi.org/10.1016/j.ijproman.2015.12.007