Article Sphere Logo

A Procedural Worksheet On PRINCE2 Project Management

By Expert Author: Shaun Watling | Article Abstract
Word Count: 597 words | Views: 96 view(s)
PRINCE2, the abbreviation for Projects In Controlled Environment, is a process based method, derived from the initial PRINCE project management methodology. It is a recognised international standard, a registered trademark of OGC, deployed extensively by the UK government. PRINCE2 crucially assists with the optimal usage of resources and project risk management initiatives, thus securing for itself an eminent position in the overall relevance graph.

PRINCE2 is an enhanced version of the initial PRINCE methodology, which in turn was based on PROMPT, a project management method, introduced by the CCTA (Central Computer and Telecommunications Agency). PRINCE was developed in 1989, as a UK government standard for IT project management, and later published as PRINCE2 in 1996. While the initial model had a restricted adaptability, PRINCE2 is suitable for all types of management projects.

Methodological Overview

PRINCE2 as a method entails forty five sub processes, categorised into eight headings i.e. Starting Up a Project (SU), Planning (PL), Initiating a Project (IP), Directing a Project (DP), Controlling a Stage (CS), Managing Product Delivery (MP), Managing Stage Boundaries (SB) and Closing a Project (CP). As evident from the stated classification, PRINCE2 as a process driven methodology, focuses on a project’s organised start, continuation and completion. It renders the much desired standardised approach to the project, thus drafting a common platform for all concerned to proceed.

Moving over to the stage description, the SU stage undertakes the vital tasks relevant to appointing the project team, preparing the outline and thus defining the aim of the exercise. This also logically results in preparing a business justification case. The second stage i.e. PL begins with product identification and analysis. Successful completion of this task prepares grounds for a closer estimation of the overall effort required for goal achievement. The stage ends with finally deciding upon the relevant plan formats.

IP is the third stage of PRINCE2 methodology, which is an augmented level of the earlier SU level. This stage aims at preparing a substantial business case. Another key focus at this stage is planning the quality aspect and thus setting up the requisite project controls. Once this is accomplished, the stage also prepares the project files and assembles the initiation documents. The fourth stage, i.e. the DP level, dedicates attention towards the pertinent controlling aspect. This stage defines the authorisation process and more importantly provides scope for an additional plan, in case of a misfit. All relevant board guidance terms are covered at this level of PRINCE2.

Next is the CS step which defines the procedures to control individual stages. Work progress is assessed at this level to capture and examine the key project issues. Other tasks at this level include, reviewing stage status, reporting, planning corrective actions, escalating the experienced issues and receiving the completed work. CS is followed by the MP stage which accomplishes the acceptance, execution and delivery aspects of the work package.

The last two stages of PRINCE2 are the SB and CP. The former precisely defines the tasks which should be contained within various stages and includes defining the end of a stage, next stage planning, maintenance of log files and amendment tools. The CP stage is responsible for the final decommissioning of a project. The evaluation exercise and follow up action steps are included at this level.

Successful application of the PRINCE2 and thus the above elucidate stages, imparts a structured approach to an intricate project. Coordination becomes simpler and adjustment nuances are much better handled. With the PRINCE2 methodology appropriately executed, a project can be reasonably divided into various sub tasks and therefore successfully completed.
Shaun Watling

About the Author/Author Bio

Shaun Watling wrote the Article 'A Procedural Worksheet On PRINCE2 Project Management' and recommends you visit http://www.afaprojects.com/training_prince2_venues.asp for more information on PRINCE2 training courses in Norwich.

Article Source: http://www.articlesphere.com/Article/A-Procedural--Worksheet-On-PRINCE2-Project-Management/140090

Article Submitted: 2008-05-14 | This Article has been viewed 96 times.

Rate Article

Related Videos

Learn Business English Vocabulary for Project Management
Learn Business English Vocabulary for Project Management
How to Build Small Business IT Consensus for Major Projects
Project Collaboration
How to Manage a Home Improvement Project
 

More "Project Management" Related Articles

 
 

Listed below are more articles related to the above article from the "Project Management" article category.

People interested in the above article "A Procedural Worksheet On PRINCE2 Project Management" are also interested in the related articles listed below:

 
This article deals with the sixth of the OGC's eight causes of project failure: evaluation of the Business Case is driven by initial price rather than by value for money.
Scrum, both general and flexible, can be used in any application that encompasses multiple parts or projects. Because the Scrum methodology includes meeting constantly changing needs, it is ideal for integration into a company's processes. Discover how to keep teams and departments working in harmony while solving a common goal more effectively.
This article deals with the third of the OGC's eight causes of project failure: insufficient or ineffective engagement with project stakeholders. Individuals and groups who are not part of the project management team, but who need to interact with the project or may be affected by the project's outcome, are known as stakeholders. Stakeholders can potentially gain or lost as a result of project delivery, and as a consequence may support or oppose the project.
This post deals with the second of the OGC's eight causes of project failure: the lack of effective or clear senior management, ownership or leadership at higher levels within the organisation.
In April 2009 the National Audit Office published a report that declared the failure of the original C-NOMIS and described how the project had demonstrated seven out of the eight primary causes of project failure. C-NOMIS has now been re-scoped and is earmarked for delivery in 2011. However, important questions remain regarding the way in which the project was managed, the length of time for which mis-management of the project was tolerated, and the value-for-money that can be expected from vast government programmes of this kind.
India’s two important cities Mumbai and Bangalore have arrived on the world map as the hub of some of the key businesses. Mumbai being the commercial and financial capital of India is home to the all the major financial institutions, banks and stock exchanges whereas Bangalore is better known as the Silicon Valley of India, as the answer to the silicon valley of USA. These two cities have witnessed large scale development and are today thriving Indian cities, with numerous software and financial establishments coming up.
A Project Manager is the person responsible for the overall success of the project. Having received the Project Mandate (detailing the reason for the project and the expected outcome) from Corporate/Programme Management, it is the Project Manager’s job to...
 
Article Directory Home All Categories Business Project Management
 

Can't find what you're looking for? Try Google Search!
 
Copyright © 2005 - by Larry Lim, Singapore - Article Search Engine Directory at ArticleSphere.com™
All Rights Reserved Worldwide. All Trademarks and Servicemarks are the property of the respective owners.

Afrikaans Albanian Arabic Belarusian Bulgarian Catalan Chinese (Simplified) Chinese (Traditional) Croatian Czech Danish German English Estonian Filipino Finnish French Galician Greek Hebrew Hindi Hungarian Icelandic Indonesian Irish Italiano Japanese Korean Latvian Lithuanian Macedonian Malay Maltese Dutch Norwegian Persian Polish Portuguese Romanian Russian Serbian Slovak Slovenian Spanish Swahili Swedish Thai Turkish Ukrainian Vietnamese Welsh Yiddish