ITC Project Management: Prince2 Methodology

Discuss about the ITC Project Management for Prince2 Methodology.

 

Prince2 Methodology

This PRINCE2 methodology comprises of the organization, control and quality management of the project with the help of review and consistency for aligning the project with its objectives. This PRINCE2 process can be described best as the linear manner which consists of project starting, and then there is project closing. The assumptions are in such a way that this process will prescribe that as per Waterfall method. (Larman, C., 2004)

Role of PrinceE2 Methodology in Relation to the Project Management

This methodology will focus while managing the projects through various stages with the appropriate governance levels. It was clear that this process of PRINCE2 is totally intended for scalable and they should get tailored so that it can suit the specific constraints and needs for the project and their related environment. (Kurian, T., 2006) 

Difference Between Agile and Prince2 Methodologies

Methodology	PRINCE2	Agile
Definition	This PRINCE2 methodology comprises of the organization, control and quality management of the project with the help of review and consistency for aligning the project with its objectives. This PRINCE2 process can be described best as the linear manner which consists of project starting, and then there is project closing.	The Agile methodology will pursue an incremental method. With the help of this, developers of the project can start off the design of the project which is simplistic and can start working on the small modules. (Reid, A., 2013)

 

Advantages	This is similar to the waterfall model. Before going to next step, the developer should complete the current step. After each step completion, customer feedback has to be taken before going to next step.	With the assistance of this system, designers can include new elements and roll out any improvements required in past strides too. Changes can get consolidated once the underlying arranging was settled and the project can get re-composed. The needs of task would get assessed after every sprint. (OGC, 2009)
Disadvantages	The designer can't go to the past stride and roll out fundamental improvements. This technique will thoroughly depend on the prerequisites assembled at first. On the off chance that necessity got changed or the changes are needed, then the venture needs to begin from the underlying. Testing should be possible toward the end as it were. Through the testing, the deferral in the enticement was high. There is requirement of the customer's contribution and if changes need, then it will affect the financial plan.	With having very less fruitful of the undertaking supervisor, there is a progression of code sprints in the item. Because of this, the venture will convey late and this anticipates will be over spending plan moreover. The starting of the undertaking didn't have the complete arrangement, along these lines the item that was conveyed at last can be unique in relation to the one conferred in the beginning. (Nader, R., 2013)
When to use	This strategy is utilized when there is the unmistakable photo of the last result of the undertaking. In this, the customer does not have any alternative adjusting the extent of the item.	This approach is utilized when the item which was made will be utilized for an industry and the models are evolving quickly. At the point when there are designers who are talented can think and adjust autonomously. This ought to be utilized when the last photo of the item is not clear. (Mike, A., 2015)

Prince2 Methodology Related to Project life Cycle

The PRINCE2 methodology is not considered when the project is small or when there is a need for any kind of modification in the project. For building and maintaining the lists, registers, logs and documents there is a workload which is significant.

This methodology is considered as the input to the project life cycle. PRINCE2 expect that the undertaking is keep running inside the setting of an agreement and does exclude this movement inside the technique itself. In any case, it proposes that since contracting and acquisition are master exercises these can be overseen independently utilizing the strategy. (Monief, E., 2010)

References

Larman, C., 2004, Agile and Iterative Development: A Manager's Guide. Addison-Wesley. p. 27

Kurian, T., 2006, Agility Metrics: A Quantitative Fuzzy Based Approach for Measuring Agility of a Software Process, ISAM-Proceedings of International Conference on Agile Manufacturing'06(ICAM-2006)

Reid, A., 2013, "Capita acquires majority stake in ITIL and PRINCE2".Association for project management

OGC, 2009, Managing Successful Projects with PRINCE2, TSO (The Stationery Office) ISBN 978-0-11-331059-3

Nader R., 2013, Planning Lifecycle in PRINCE2, https://www.projectsmart.co.uk/planning-lifecycle-in-prince2.php

Mike A., 2015, What are the differences between Agile and a structured approach to project management? Which is best? https://www.axelos.com/news/differences-agile-structured-project-management

Monief E., 2010, PRINCE2 Methodology, https://www.slideshare.net/moniefeied/prince2-methodology

Yardley, D., 2003, Success IT Project Delivery: Learning the Lessons of Project Failure. Addison Wesley