Factors responsible for the successful development of the project

Managing the team and members of the team in the management of project is a crucial process  during the development  of the project. There are certain factors those  are responsible for the successful development of the project like the choosing of the right methodology for  managing the project and maintaining the project life cycle. However, managing the project management team is important for the development of project. To manage the project management team , certain attributes are needed to be maintained. In the project management team the presence of the team leaders  is needed along with team members of project.  In order to develop the project in a proper way, the mutual understanding between the project team members  and project  team leaders  is needed. Objective of this paper is to evaluate the behavior of the team members along with the team leaders on different situation is the project team. The relevance of this the discussion is that it helps to identify the factors responsible for the situational analysis in an organization. The discussion emphasis on the three situations those can be happened in the project management team. The analysis of the behavior of the team members along with the team leader have been evaluated on the basis of the situation.

It can be said that that the good project management behavior and practices can lead to the delivery o the proper outcome meeting all the requirements f the clients and the stakeholders of the project. Managing of the project is dependent on the proper management of the team members in project management team. Implementation of the different functionalities in the project can be done properly, if the flow of communication between the team members is present. Apart from that the communication between the team leader and other project team member is needed to be maintained for keeping track of the project. It has been seen that the behavior of the team members and team leader may change with respect to the managerial skills and the environmental factors.  In the discussion the behavior of the project team lead and project team members have been evaluated on different situation.

Context of the case: the good practice  and  behavior in the project management can be said to implemented if  all the steps in the project management  are followed properly.  In this context an example of the implementation of artificial intelligence driven system in Amazon can be mentioned. At the initial stage the requirement for the deployment of the cloud is analyzed. The implementation plan is made by the experts. During the course of execution, the project managers and the team leaders were cooperative to each other. The implementation of the artificial intelligence driven system at Amazon is successful and it is helping  Amazon by providing better customer supports.

Attributes needed to manage the project management team

Critical reflection: The above mentioned project situation is can be described as an example of the project where good project management behavior has been observed. The reason for mentioning the example as the good example of the project management behavior is that, in this case, the analysis of the requirement is done in a proper way. In the other hand the project management methodology has been selected on the basis of the requirement and the type of the project. In this case, it can be assumed that the implementation of the methodology has been done in proper way. Apart from that the outcome of the project has met all the requirements of the client.  During the implementation of the functionality of the project, the sharing of knowledge has been done by the project team members.  Overall execution of the project has been monitored by the project leader. All these attributes  indicates that the implementation of the project has been done on the basis of the rules and procedures for the proper implementation of the project and this can be considered as the good behavior in context of project management.

Observation of behavior of project team members and the project team lead:  In the context of the above mentioned project management environment , the behavior of the project team lead and the project team members has been observed. It has been seen that in this project management environment, proper knowledge sharing between the project team members  has been maintained. Apart from that the project team leader has assigned the different modules of the  project to different members of the project. The monitoring of the compilation of the project is monitored by the project team leader. Team leader took the responsibility of proper implementation of the project through methodology and the project governance practices. The behavior of the leader is democratic,  which means the team leader is open to any opinion  of the project team members.  The final decisions are taken by the project team leader after reviewing the opinion of the  team members  and the situation of the project. In this context it can be said the formation of the team has been done in a proper way. The  team lead along with the project team members took the responsibility and completed their task in a proper way during the development of the project.

Bad project management behavior indicates the mismanagement during the course of development of project. The behavior of the bad project management along with the approach of the project team towards the development has been done in this section.

Evaluation of project team behavior on different situations

Context of the case:  Queensland Health Payroll system can be regarded as the bad implementation of the project management. The primary  objective of the Queensland Health Payroll system was to replace the existing system by the advanced technology. However, the project has seen bad management of time and communication between different stakeholders. The manual process of entering data had to be done in a faster way which caused errors in the data entry. Moreover due to the mismanagement the project was not delivered in right time and the budget was more than the estimated one. The main objective of the project was not delivered and this project is regarded as one of the significant example of failed projects.

Critical reflection:  There were certain attributes those indicate that the project was not managed in a proper way. For the proper development of the project, analysis of the requirement is required at the initial stage. In this situation, the documentation of the analysis has not been done in a proper way. The scope creep was present during the development of the project. The presence of the scope creep in the project is not desirable as it increase the budget of the project and the time of the delivery. The delivery of the outcome of the project was not done in at time , which indicates the mismanagement of the project. Apart from that the members of the tem were clueless at the middle of the development process regarding the possible outcome. In this case, the project team lead failed to show the focused direction regarding the project to the team members. Apart from that the lack of shared knowledge and communication between team members and team leaders were constraints for the proper implementation of the functionality of the project. All these attributes indicates that the project was not managed in a proper way and the delivery of the outcome of the project did not meet all the required qualities. Moreover, the team members along with leaders of the team were not dedicated towards the compilation of the tasks for the project.

Observation of behavior of project team members and the project team lead: The behavior and approach of the team members towards the development does not meet the desired level of the  involvement. Apart from that the team members were not cooperative while the development of the project.  Proper sharing of the knowledge was not present during the development phase. Apart from that the monitoring and governing of the project was not done by the project team lead. The mismanagement of the project was started at the initial stage of the project as the proper documentation of the requirement has not been done.  All these attributes indicate that the project was not managed properly and the project management team along with  the team lead was not involved in the development phase  and they did not take required level of responsibility for the proper delivery of the project.

Examples of good, bad, and unacceptable project management behavior

The unacceptable project management behavior indicates that that the  outcome of the  project is not according to the requirements of the client and the project has failed to deliver the required functionalities. In this situation the behavior and approach of the project team members  and project management team  are needed to be evaluated.

Context of the case: in this context the disaster at the Deepwater Horizon can be mentioned. Deepwater Horizon is oil refinery owned by the BP. During the functioning of the process at Deepwater Horizon, fire caught and led to the disaster. The disaster happened during the mismanagement and miscommunication happened in the project. There was a leak in the cement base. The engineers were aware about the leak in the cement base; however, they did not informed this to the higher management which led to the disaster. This is an example of the project management which has been failed due to the negligence in the communication process and the unacceptable management of the entire project. It has been found out that the project was lack of disaster management and risk management which is not acceptable.

Critical refection: There are certain attributes those indicate that the project mentioned in the context is managed in unaccepted way. The life cycle for the development of the project was not followed. Apart from that there was no designation for the project team lead and the project team members were clueless about the development of the project. Moreover,  no proper methodology was selected to develop the project. The team members were not cooperative to each other. This led to the improper implementation of the functionality. Apart from that there was no communication between project team members along with stakeholders of the project. All these attributes indicate that the project was not managed in a proper way. Apart from that the outcome of the project was not matched with the desired requirements. This indicates that the project is the big failure.

Observation of the behavior of project team members and the project team lead:  In the project management situation mentioned above, there was not proper formation of the team present. Moreover, in the team , there was no project manager or team leader present for guiding the members of the team. The team members did not indulge themselves in the development of the project. Apart from that the project lacked of proper methodology and project management principals along with the project governance.

Conclusion:

The above discussion is regarding the analysis of the project management in different situations. Three situations have been described in this context. In one situation the project is managed in a proper way. In the second situation the project is not managed properly and in the third situation the management of the project is misguided in an unacceptable way. The analysis of the behavior of the project  team lead and the project team members  have been analyzed in a proper way for all of three situations. It can be concluded that the proper formation of the project team is important along with following the development methodology and project life cycle. The analysis if the requirement is the most important part during the initial stage of the development as it mitigates the chances of the scope creep. Apart from that the sharing of knowledge among the  project team members  along with the concern of the team lead for  regarding the development will help  a project to deliver the right outcome.

Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.

Binder, J., 2016. Global project management: communication, collaboration and management across borders. Routledge.

Bjorvatn, T. and Wald, A., 2018. Project complexity and team-level absorptive capacity as drivers of project management performance. International Journal of Project Management, 36(6), pp.876-888.

Chen, J., Neubaum, D.O., Reilly, R.R. and Lynn, G.S., 2015. The relationship between team autonomy and new product development performance under different levels of technological turbulence. Journal of Operations Management, 33, pp.83-96.

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

Dingsøyr, T., Moe, N.B. and Seim, E.A., 2018. Coordinating Knowledge Work in Multi-Team Programs: Findings from a Large-Scale Agile Development Program. arXiv preprint arXiv:1801.08764.

Donnelly, H., Alemayehu, D., Botgros, R., Comic-Savic, S., Eisenstein, B., Lorenz, B., Merchant, K., Pelfrene, E., Reith, C., Santiago, J. and Tiernan, R., 2016. Streamlining safety data collection in hospital-acquired bacterial pneumonia and ventilator-associated bacterial pneumonia trials: recommendations of the Clinical Trials Transformation Initiative antibacterial drug development project team. Clinical Infectious Diseases, 63(suppl_2), pp.S39-S45.

Ennabih, A., Van Riel, A.C. and Sasovova, Z., 2016. Leadership And New Product Development Project Performance: A Team Cognition Perspective. In Academy of Management Proceedings (Vol. 2016, No. 1, p. 16920). Briarcliff Manor, NY 10510: Academy of Management.

Griffin, P. and Care, E. eds., 2014. Assessment and teaching of 21st century skills: Methods and approach. Springer.

Hoda, R. and Murugesan, L.K., 2016. Multi-level agile project management challenges: A self-organizing team perspective. Journal of Systems and Software, 117, pp.245-257.

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.

Howard, K., Clifford, S., Powers, J.H., Saretsky, T., Hoffmann, S.C., Llorens, L., Talbot, G.H. and Cimms, T.A., 2015. Community-Acquired Bacterial Pneumonia (Cabp): Development of A New Patient-Reported Outcome (Pro) FNIH Biomarkers Consortium CABP ABSSSI Project Team ‘3. Value in Health, 18(3), p.A242.

Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning, scheduling, and controlling. John Wiley & Sons.

Kolesnikov, O., Gogunskii, V., Kolesnikova, K., Lukianov, D. and Olekh, T., 2016. Development of the model of interaction among the project, team of project and project environment in project system [SCOPUS]. Eastern-European Journal of Enterprise Technologies.-2016, 83(5/9), pp.12-21.

Lynn, G.S., Polat, V. and Reilly, R.R., 2016. Team Trust and Team Learning in New Product Development Projects. In Let’s Get Engaged! Crossing the Threshold of Marketing’s Engagement Era (pp. 639-640). Springer, Cham.

Medina, A. and Francis, A.J., 2015. What are the characteristics that software development project team members associate with a good project manager?. Project Management Journal, 46(5), pp.81-93.

Moe, N.B., Dingsøyr, T. and Rolland, K., 2018. To schedule or not to schedule? An investigation of meetings as an inter-team coordination mechanism in large-scale agile software development.

Natvig, D. and Stark, N.L., 2016. A Project Team Analysis Using Tuckman’s Model of Small-Group Development. Journal of Nursing Education, 55(12), pp.675-681.

Serrador, P. and Pinto, J.K., 2015. Does Agile work?—A quantitative analysis of agile project success. International Journal of Project Management, 33(5), pp.1040-1051.

Sherstyuk, O., Olekh, ?. and Kolesnikova, K., 2016. The research on role differentiation as a method of forming the project team. ????????-??????????? ?????? ????????? ??????????, (2 (3)), pp.63-68.