ICT Project Management The Project Implementation

Question: Describe about the ICT Project Management for The Project Implementation. Answer: Introduction The project management is the most vital part of the project implementation. The project management decides the goals and the path of the project (Kerzner 2013). Hence it can be seen that, in the absence of proper project management and manager the project goes haywire. This report aims to discuss the various project management techniques that are used for management of the project. Various theoretical concepts will be discussed in this report in the context of IT projects. Project management concepts Each project is unique, as the various parameters that are needed for the project vary. In the case of the IT projects, the most important resource is the expertise which is followed by the components for implementation. The project implantation can be divided into seven stages which are the identification of the objectives, timeline, complexity, nature of the project, resources, structure of the organization, and the control system (Burke 2013). For the management of these components, two major techniques are available, which are predictive project management technique and adaptive project management techniques. Predictive project management technique The predictive project management technique is the method in which the various process parameters are taken into account according to the specifications that have been proposed by the client. In this method all the resources contributing to the development is taken and then the project is started with all the risks and the contingencies in mind. This technique helps in understanding the project contingencies and the requirements of the project, which in turn results in successful completion of the project (Schwalbe 2015). Since the foresight is available for the project the timeline strictly adheres and modifications are very difficult to accommodate. The following five steps are followed while managing a project: Risk assessment In this phase a detailed review in done on the problem. The review helps in determination of the complexity of the project which in turn helps in determination of the level of control of the parameters of the project that will help in the successful delivery of the project to the client. Structured review This phase is the continuity of the previous phase but instead of the clients the project development stakeholders are interviewed, and their feedbacks are taken into account (Hwang and Ng 2013). This review helps in further bolstering the stand of the project manager who is responsible for deciding the course of action of the project implementation. Predictive analytics The predictive analysis helps in understanding the output of the software that will be developed by the project team. In this stage, the key project attribute is shared with the stakeholders with the help of the business analysts and the project manager. This stage can also be termed as the architectural development stage. Prototyping After the development of the architectural stages, the prototype is developed according to the architecture of the software. Since the architecture of the software is developed only one taking all the requirements of the software to be developed this technique is not adaptive. After the project is developed, the software is ready to be tested and review. Testing and report generation The testing of the software is a very important stage as the bugs of the software plays a very vital role in the failure. After the bugs of the software are found the final tweak is done in the software which is followed by the review and the delivery (Bryman and Bell 2015). The documentation is done in detail for delivery of the software and keeping a record of the development. The famous predictive model is the waterfall model. Fig 1: represents the famous waterfall model (As created by author) Adaptive project management techniques The adaptive project management technique is the one in which the continuous development is given the prime importance. The planning of the project is done in the initial phases, but the implementation is done in different phases that are an iteration of the process that can be seen in the diagram below. The internal loop indicates the product development and the outer loop indicates the product planning and documentation. After the planning has been done, the project is implemented in phases and iterations (Gomez-Exposito Conejo and Canizares 2016). In case a change is proposed in the system the planning is done accordingly and is implemented in the next iteration. Since the software development is prone to changes this process model better than the other models. Fig 2: Represents the famous agile development model (As created by author) The development of the project is done in following six phases (Highsmith 2013): Planning phase The initial planning is done in this phase, and the layout of the software architecture is done that will be implemented in decided iterations. Analysis phase According to the division of the requirements, the analysis of the requirements is done that helps in understanding the requirement according to which the programming has to be done. Design phase In the design phase, the architectural design of the project is created according to which the project has to be implemented this layout helps the programmers to do the programming of the system. Coding phase The coding of the project is done with the help of the architectural design as per the requirements. Testing phase The software is tested in this phase for the detection of the bugs which is eliminated in the iteration. Deployment phase The deployment phase is the final phase where the software is presented to the client, and the feedback is given regarding the software (Conforto et al. 2014). In case more requirements pop-up during this phase the implementation time and the cost increases, but the requirements can be accommodated in the system. Conclusion IT project management is more tedious compared to the PMBOK (Project Management Book of Knowledge) methods. The traditional methods lay more emphasis on the timeline but for the implementation of the IT projects the most adaptive processes are being proposed which offers more flexibility to the software development which is more people intensive compared to the traditional methods which are more resource and time-centric. Both the methods the predictive and the adaptive methods and been explained in detail in the report which has helped in understanding the basic difference between them. References Kerzner, H.R., 2013.Project management: a systems approach to planning, scheduling, and controlling. John Wiley Sons. Burke, R., 2013. Project management: planning and control techniques.New Jersey, USA. Schwalbe, K., 2015.Information technology project management. Cengage Learning. Hwang, B.G. and Ng, W.J., 2013. Project management knowledge and skills for green construction: Overcoming challenges.International Journal of Project Management,31(2), pp.272-284. Bryman, A. and Bell, E., 2015.Business research methods. Oxford University Press, USA. Gmez-Expsito, A., Conejo, A.J. and Caizares, C. eds., 2016.Electric energy systems: analysis and operation. CRC Press. Highsmith, J., 2013.Adaptive software development: a collaborative approach to managing complex systems. Addison-Wesley. 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.