ICT Project Management and Methodology

Question: Discuss about the ICT Project Management and Methodology. Answer: Project methodology and its role in project management According to Kerzner (2013), a project is defined as a planned set of interrelated tasks that is used to accomplish a common goal over a fixed period and within certain cost and other limitations. However, these projects have to be managed throughout their life cycle from initiation stage to the closing state. Thus, according to Schwalbe (2015) project methodologies are used to manage these projects through the application of knowledge, skills, tools, and techniquesin order to meet theprojectrequirements and are considered as a guiding process for project managers. Image1: Project Life Cycle (Source: Kerzner 2013) A project methodology is a model that is used for design, planning, implementation and achievement of their project objectives. Burke (2013) depicts that selection of an appropriate methodology will benefit the project to accept and resolve the evolved risk with high proficiency. Moreover, Tomanek and Juricek (2015) portrays that project methodologies provide strategic benefits, tactical benefits and operational benefits to the project. Strategic benefits signify the ability to assess the risks that large projects encompass and apply relevant strategies to overcome those risks. Tactical benefits resemble the situation to evaluate the validity of status assessments and ensure early recognition and correction of the risk for a project; whereas, operational benefits allows a project manager to deliver cost-effective, schedule-compressed solutions by empowering the team members to accomplish the project in a correct way (Cooke, 2016). PRINCE2 and Agile project methodology Compare and Contrast Image2: PRINCE2 project methodology for project development cycle (Source: Cooke, 2016) PRINCE2 concentrates on controlling the delivery of products and not emphasize on the quality of the project while agile project methodology provides a flexible approach for building the projects with required quality for every phase of the project life cycle. Moreover, Tomanek and Juricek (2015) portrays that the PRINCE2 is a project methodology for designing a project and Agile is the development tools for making the software better. Image3: Agile project methodology for project development cycle (Source: Thiemich and Puhlmann, 2013) Thiemich and Puhlmann (2013) illustrated that Agile project methodology focuses on collaboration for developing software along with the client and this is done by defining and prioritizing requirements, developing, evaluating and considering feedback from customers for every cycle of iterations. On the other hand, PRINCE2 defines the interface between the project and skilled team members project manager, team manager and project board. Similarities and differences PRINCE2 and Agile project methodology that is used for developing software for accomplishing certain business objective or purpose. These project methodologies have the similarity to provide significant flexibility and speed that result in increased customer satisfaction, effective cost control, improved communication and efficient decision-making (Antunes et al., 2015). PRINCE2 project methodology Agile project methodology Principle The business case for the project has to be present during the life cycle of the project. Revisiting of the project owner for assessing the backlog of the project Learning aspect The development of software using PRINCE2 needs previous experience of the project manager. The entire project is developed in modules and after accomplishments of each module; the team members revised the sprint for making it better (Antunes et al., 2015). Documentation PRINCE2 is documented in product based planning and focussed on products and their quality The team member notes the project requirements and criteria and these criteria are used for developing projects whose quality will be judged on the quality of each sprint. Requirement Change The project have to be tightly controlled The project does not have to be tightly schedule and can be changed according to the client's requirements at any time. Scope PRINCE2 accurately predicts the project requirements and the future demands Agile methodology is used for formulating perfect software to capture as much as efficiency in giving time and budget. Used techniques PRINCE2 uses business case; change control, quality review and product based planning (Tomanek Juricek, 2015). The agile methodology uses Timeboxing, prototyping, agile modeling, prioritize requirement list and MoSCoW prioritization (Cooke, 2016). Table 1: Difference between PRINCE2 and Agile project methodology (Source: Created by Author) Relation of PRINCE2 and Agile project methodology with project life cycle (PLC) Saad et al. (2014) portrays that PRINCE2 (PRojects IN Controlled Environments) offers guidelines, recommendations, and processes for planning the formulation of the software. PRINCE2 helps the project managers to reach project goals with an optimal use of resources. During the project life cycle, PRINCE2 helps the formulation of the software manage by stages and majorly emphasizes on three processes of the project life cycle- "initiating a project", "managing a stage boundary", and "starting up a project". In project life cycle, there are four stages- initiation, planning, execution/monitoring and termination of a project. Agile project methodology provides flexibility to make changes in the module of a software development and the testing of each module can be integrated from initiation point to termination point at the end of developing the entire software (Thiemich Puhlmann, 2013). This methodology also emphasizes more on the regular communicationapproach with the customers so that they can evaluate whether all their criteria will be fulfilled or not. Reference List Antunes, B., Santos, D., Lopes, E., Fidalgo, F., Alves, P. (2015). Blisstrail: An Agile Project Business Case Study.Procedia Computer Science,64, 529-536. Burke, R. (2013). Project management: planning and control techniques.New Jersey, USA. Cooke, J. L. (2016). PRINCE2 Agile. Kerzner, H. R. (2013).Project management: a systems approach to planning, scheduling, and controlling. John Wiley Sons. Saad, S., Ibrahim, A., Asma, O., Khan, M. S., Akhter, J. (2014). PRINCE2 MEthodology: AN INNovAtIvE WAy foR IMPRovINg PERfoRMANCE of MAlAysIAN AutoMotIvE INdustRy.The Journal of Technology Management and Technopreneurship (JTMT),1(1). Schwalbe, K. (2015).Information technology project management. Cengage Learning. Thiemich, C., Puhlmann, F. (2013). An agile BPM project methodology. InBusiness Process Management(pp. 291-306). Springer Berlin Heidelberg. Tomanek, M., Juricek, J. (2015). Project risk management model based on PRINCE2 and SCRUM frameworks.arXiv preprint arXiv:1502.03595.