Process of Implementation ICT Report

Question: Discuss about the Process of Implementation for ICT Report. Answer: Definition of Project Methodology According to Van Eck et al., (2015), the Project Methodology in Project Management is defined strictly as the combination of the logically related processes, methods as well as practices that can establish how best for developing, planning as well as delivering and controlling a project over the constant process of implementation until the successful termination and completion. The project methodology is very effective in project management in terms of using language, the evaluation of the sources as well as the detailed judgement required in order to manage a particular project. As per Pemsel and Wiewiora (2013), the project methodology is a disciplined, systematic as well as a scientifically-proven approach for designing, completing and executing a project. Role of Project Methodology and the Relationship to Project Management According to Kannan, Fish and Willett (2016), the role of the project methodology in project management is to permit to control the entire process of management with the help of the effective problem solving and decision making while assuring the success of particular technologies, methods, techniques, approaches as well as processes. A project methodology typically gives a skeleton in order to demonstrate each step in depth, so that a project manager would know what to do in terms of implementing and delivering the work as per the budget, schedule and client application. Project Management and Project Methodology are interrelated with each other (Van Eck et al., 2015). The project Methodologies contains the processes of guiding for the people who are responsible in project management. Comparison and Contrast between Waterfall and Agile Methodology Waterfall Model Agile Methodology In case of Waterfall Model, the requirements are clear and concise before the beginning of development. In case of this methodology, customer satisfaction is obtained with the help of the rapid delivery of useful software. In every single phase, exact documentation is followed for the development quality (Patel Jain, 2013). No guesswork is there between the team of development as well as the customer because there is face-to-face interaction and continuous inputs from the client-side (Kannan, Fish Willett, 2016). It is easy to implement as it is a linear model It is bit difficult as it is not a linear model. If a project is larger and requirement is clear, then Waterfall Model should be selected (Balaji Murugaiyan, 2012). For the smaller project, if requirements change randomly, then Agile Model should be selected. The entire products are tested only at the end of the process. If the bugs are discovered late but are written early, their presence can be impacted how other code was written. The testing at the end of every sprint assures that the bugs are taken care of as well as caught in the cycle of development. Similarities between Waterfall and Agile Models There are few similarities between the two models. These are as follows: Both of the models plan the work out totally before the starting. Waterfall and Agile models can early lock down These two models can also institute various reviews Both the models move forward in sequential and step-by-step manner (Balaji Murugaiyan, 2012). These two models only move forward while all the parts of the previous steps were completed Both of the models can capture all the information with the extensive documentation. On the other hand, both of the models analyze the requirement as well as implement a potential for satisfying the requirement. Evaluation of the Methodologies Related to the Project Life Cycle (PLC) Waterfall Model According to Patel and Jain (2013), the Waterfall Model is the most important model for describing a project life cycle. According to this model, the total project development is divided into several parts and each of the parts should be completed sequentially by marinating the order. Another important fact of using this model is that each of the parts of the PLC can not be left without completing it fully. Once the previous part is 100% done, then only the development work is able to start the next phase of PLC (Chong Hopkins, 2016). Agile Model According to Kannan, Fish and Willett (2016), the agile model uses an alternative approach of the traditional waterfall model of PLC. This model uses the iterative testing of the developed parts of the whole project. Based on the results of the iterative testing, the developers can change the previous section of PLC to get the desired results. This model gives the ability of assessing the right direction of a project throughout the PLC (Patel Jain, 2013). Reference List Balaji, S., Murugaiyan, M. S. (2012). Waterfall vs. V-Model vs. Agile: A comparative study on SDLC.International Journal of Information Technology and Business Management,2(1), 26-30. Chong, U., Hopkins, O. (2016). An international experience on the evolution of road costs during the project life cycle.Transport Policy,48, 60-66. Kannan, V., Fish, J. C., Willett, D. L. (2016, February). Agile model driven development of electronic health record-based specialty population registries. In2016 IEEE-EMBS International Conference on Biomedical and Health Informatics (BHI)(pp. 465-468). IEEE. Patel, U. A., Jain, N. K. (2013). New Idea In Waterfall Model For Real Time Software Development. InInternational Journal of Engineering Research and Technology(Vol. 2, No. 4 (April-2013)). ESRSA Publications. Pemsel, S., Wiewiora, A. (2013). Project management office a knowledge broker in project-based organisations.International Journal of Project Management,31(1), 31-42. Van Eck, M. L., Lu, X., Leemans, S. J., van der Aalst, W. M. (2015). PM^ 2: A Process Mining Project Methodology. InInternational Conference on Advanced Information Systems Engineering(pp. 297-313). Springer International Publishing.