Project Management Comparison of Prince2 and Pmbok

5983 Words24 Pages
MSC756 PROJECT MANAGEMENT ASSIGNMENT TWO THE PRINCE2 METHODOLOGY: A DETAILED COMPARISON OF RELATIVE STRENGTHS TO THE PMBOK AND APPLICATION TO PROJECT MANAGEMENT AUTHOR: KANE WRIGHT STUDENT: 400072002 WORD COUNT (LESS TABLE OF CONTENTS, REFERENCES, APPENDICES): 4972 DUE DATE: 28 SEPTEMBER 2009 TABLE OF CONTENTS INTRODUCTION________________________________________________ _____________3 LITERATURE REVIEW______________________________________________________ _3 Background__________________________________________________ ________________3 Methodology_________________________________________________ _________________3 Components__________________________________________________ ________________4…show more content…
Academics agree (Birlouez 2009, Siegelaub 2006) that the business case remains relevant throughout the project lifecycle and ultimately determines whether, through a change to feasibility of the business case at a certain point, the project should be terminated. Organisation PRINCE2 advocates a clear definition of the project organisation structure, to provide the Project Manager with the staff and resources to efficiently and effectively complete the project. Plans Planning is a core concept emphasised within PRINCE2, providing a focus for the outputs and products to be delivered at various stages in the product lifecycle (Wideman 2002) and ensuring that plans are developed and executed not only at the strategic level but also down to the lower (team) levels (ILX Group 2009). Product-based planning is the key PRINCE2 technique with which to achieve this and represents the first of three techniques available to project managers in using PRINCE2 (Birlouez 2009). Controls Siegelaub (2006) has described the ‘controls’ component of PRINCE2 as an area targeted to assist decision making. He identifies that the implementation of project control measures ensures: • products generated meet defined acceptance criteria, • the project is being completed in accordance with time/schedule, cost and resource plans, • throughout the project lifecycle, the project and it’s
Open Document