History of PRINCE2
PRINCE2 (Project in Controlled Environments, Version 2) is a project management methodology that are released in 1996. It was based on combination of two methodology that is PROMPT (Projects Resource Organization Management Planning Technique) and IBM's MITP (Managing the Implementation of the Total Project) methodology. PROMPT that is originally created by former IBM Project Managers in 1975. Central Computer and Telecommunications Agency (CCTA) one of IBM’s client which is responsible for IT support in United Kingdom Government, applied PROMPT methodology and adapted it in 1979 and called it PRINCE (PROMPT in the CCTA Environment) which became Projects in Controlled Environments. PRINCE was widely used in IT project in public sector at that time. Others sectors such as businesses also want to use PRINCE, therefore the PRINCE gain transformation so it can easily adapt for a new users. PRINCE2 was created which can be applying in any project with more flexible and generic unmindful of any complexity.
Description of PRINCE2
PRINCE2 is a structured project management methodology that widely used by organizations and government in the world. It is known as de facto process-based method in project management especially in IT environments. PRINCE2 direct the project management with four integrated elements of principles, themes, processes and environments. To be called PRINCE2 project, the project must follow the principles in PRINCE2. There are seven principles that are followed by seven themes which form the basic characteristic of PRINCE2. It also consists of seven processes that are interconnected to obtain goals, the successfulness of the project and managed the direction of the project. The figure below showed the structure of PRINCE2.
Figure 1. Structure of PRINCE2
1. Business justification
Project developers must understand the benefit that will be achieve in return of it investment compare to it cost and risk of the project.
2. Learn from experience
PRINCE2 encourage the project management team to refer form past project for project improvements.
3. Roles and Responsibilities
Project must define roles and responsibilities of Project Board. Project Board consist business stakeholder, users and suppliers. Project Board makes the big decision about project and delegates authority to Project Managers.
4. Manage by Stages
Project must be must be monitored and controlled in every stage.
5. Manage by exception
Each time the Project Board want to move to next stage, they delegates authority to Project Managers by setting tolerances for cost, time, quality, scope, risk and benefits.
6. Focus on products
Product produced must follow the scope of the project. Changes make for the product or scope must carefully consider the impact of project objectives.
7. Tailor to the project environments
The project must consider the risk, complexity, size and importance. More complex project means it will need more high...