-A +A

Prince II

Printervriendelijke versiePrintervriendelijke versieVerstuur naar een vriendVerstuur naar een vriend
Projectplan (PID)
 
Achtergrond
 
Projectdefinitie
 
Project doel
 
Projectscope (projectinhoud)
 
Projectuitsluitingen
 
Verwachte projectresultaten
 
Raakvlakken
 
Businesscase
 
Hoe past plan in strategie van het kantoor
 
Hoe past plan in strategie van de cliënt
 
Waarom is het project nodig
 
Projecttoleranties
 
Verwachtingen over de kwaliteit
 
Acceptatiecriteria
 
Bekende risico’s
 
Opsomming risico’s
 
Worst case scenario
 
Risico controle en indekking
 
Beheersinstrumenten
 
Concept businessplan
Concept deadlines
Concept projectplan en aanpak
Concept projectorganisatie
Concept taakomschrijvingen
Communicatieplan
 
 
Bijlagen:
 
Recources
 
Veiligheid
 
Juridische beperkingen
 
Bestaande oplossingen
 
Technologie
 
Kennis
 
Opstart van het project
Opzetten va de projectorganisatie (stuurgroep)
 
De opdrachtgever = project manager
De bewaker van de organistatie
De bewaker van de klant
 
Uitwerken van het projectvoorstel
Opzetten dagelijks logboek
Fase plan
Risicobeheer en analyse
Versie beheer
Projectcommunicatiesysteem
Wie
Wat
Door wie
Aan wie
Hoe
Wanneer
 
Opstarten of niet
Kritische evaluatie aan de hand van het PID
Alternatieven
Engagement van het team door formele ondertekening
 
 
MF proces Managing van faseovergang
 
Actualiseren
 
Vastgestelde problemen in de vorige fase
 
Controle van de toegestane tolerantie
 
Evaluatie van het PID
Bijsturen
 
Klopt de uitgangsstelling nog
 
Gewijzigde omstandigheden, nieuwe feiten
 
Beoordeling
 
Afwijkingsbeoordeling en plan.
 
Risicoplan
 
            Welke risico’s hebben zich (niet) gerealiseerd
                              
            Respons op gewijzigde risicoanalyse
                              
 
Rollen beheersing: welke rollen zijn gewijzigd
 
Fase eindrapport
                Waar staan we
                Kosten-tijd-realisatie-tijd-middelen
                Nodige bijstiring
                Leerrapport :
                               Wat hebben we geleerd
                               Wat werkt /werkt niet en waarom
 
Volgend faseplan opstellen
Handtekening volgende fase
 
Toepassingen
 
Personal plan
Private plan
Relation plan
Cliënt plan
ICT plan
Web plan
PR plan
Media plan
Productplan
Productoptimalisationplan
HRM plan
Financial plan
Conclusionplan
Contractplan

PRINCE2

 

PRojects IN Controlled Environments (PRINCE) is a project managementmethod. It covers the management, control and organisation of a project. "PRINCE2" refers to the second major version of this method and is a registered trademark of the Office of Government Commerce (OGC), an independent office of HM Treasury of the .

History

PRINCE2 is derived from an earlier method called PROMPTII[1], and from PRINCE project management method, which was initially developed in 1989 by the Central Computer and Telecommunications Agency (CCTA) as a UK Government standard for information systems (IT) project management; however, it soon became regularly applied outside the purely IT environment.[2] PRINCE2 was released in 1996 as a generic project management method.[3] PRINCE2 has become increasingly popular and is now a de facto standard for project management in the UK.[4] Its use has spread beyond the UK to more than 50 other countries.[citation needed]

The most current revision was released in 2009 as part of the Prince2:2009 refresh project [5] by the Office of Government Commerce.

PRINCE2:2009 Refresh: Since 2006, the method has been revised and launched as "PRINCE2:2009 Refresh" on June 16th, 2009. The name "PRINCE2" (instead of "PRINCE3" or similar) is kept to demonstrate that the method remains faithful to its principles. Nevertheless, it is a fundamental revision of the method from 1996 to adapt it to the changed business environment, to make the method simpler and "lighter", to address current weaknesses or misunderstandings, and to better integrate it with other OGC methods (ITIL, P3O, P3M3, MSP, M_o_R etc.). The main difference between the 2009 version and earlier versions is that there will be two manuals: 'Managing Successful Projects with PRINCE2 - 2009 Edition' and 'Directing Successful Projects with PRINCE2 - 2009 Edition'. Both the Foundation and Practitioner Examinations will be based on the new 'Managing Projects' manual and will not include material from the new 'Directing Successful Projects' book. The pass mark for the Foundation exam will remain unchanged but the pass mark for the Practitioner exam will increase from the current 50% to 55%. The Practitioner exam will also shorten in length from 3 hours to 2.5 hours. Further info about the refresh is available here.[6]

Advantages

PRINCE2 is a structured approach to project management. It provides a method for managing projects within a clearly defined framework. PRINCE2 describes procedures to coordinate people and activities in a project, how to design and supervise the project, and what to do if the project has to be adjusted if it doesn’t develop as planned. In the method each process is specified with its key inputs and outputs and with specific goals and activities to be carried out, which gives an automatic control of any deviations from the plan. Divided into manageable stages, the method enables an efficient control of resources. On the basis of close monitoring the project can be carried out in a controlled and organised way. Being a structured method widely recognised and understood[citation needed], PRINCE2 provides a common language for all participants in the project. The various management roles and responsibilities involved in a project are fully described and are adaptable to suit the complexity of the project and skills of the organisation.

Pitfalls

PRINCE2 is sometimes incorrectly considered inappropriate for very small projects, due to the work required in creating and maintaining documents, logs and lists. However, this may often be because of a misunderstanding about which parts of PRINCE2 to apply: PRINCE2 is fully scalable.[7]

Overview of the method

Prince2 diagram.png
Diagram showing PRINCE2 processes. The arrows represent flows of information.

PRINCE2 is a process-driven project management method[8] which contrasts with reactive/adaptive methods such as Scrum. PRINCE2 2009 defines 40 separate activities and organizes these into seven processes:

Starting up a project

In this process the project team is appointed and a project brief (describing, in outline, what the project is attempting to achieve and the business justification for doing so) is prepared. In addition the overall approach to be taken is decided and the next stage of the project is planned. Once this work is done, the project board is asked to authorize the next stage, that of initiating the project.

Key activities include: appointing an executive and a project manager; designing and appointing a project management team; preparing a project brief; defining the project approach; and planning the next stage (initiation).

Initiating a project

This process builds on the work of the start up process, and the project brief is augmented to form a Business case. The approach taken to ensure quality on the project is agreed together with the overall approach to controlling the project itself (project controls). Project files are also created as is an overall plan for the project. A plan for the next stage of the project is also created. The resultant information can be put before the project board for them to authorize the project itself.

Key activities include: planning quality; planning a project; refining the business case and risks; setting up project controls; setting up project files; and assembling a Project Initiation Document.

Directing a project

This process dictates how the Project Board (which comprises such roles as the executive sponsor or project sponsor) should control the overall project. As mentioned above, the project board can authorise an initiation stage and can also authorize a project. Directing a Project also dictates how the project board should authorize a stage plan, including any stage plan that replaces an existing stage plan due to slippage or other unforeseen circumstances. Also covered is the way in which the board can give ad hoc direction to a project and the way in which a project should be closed down.

Key activities include: authorising initiation; authorising a project; authorising a stage or exception plan; giving ad-hoc direction; and confirming project closure.

Controlling a stage

PRINCE2 suggests that projects should be broken down into stages and these sub-processes dictate how each individual stage should be controlled. Most fundamentally this includes the way in which work packages are authorised and received. It also specifies the way in which progress should be monitored and how the highlights of the progress should be reported to the project board. A means for capturing and assessing project issues is suggested together with the way in which corrective action should be taken. It also lays down the method by which certain project issues should be escalated to the project board.

Key activities include: authorising work package; assessing progress; capturing and examining project issues; reviewing stage status; reporting highlights; taking corrective action; escalating project issues; and receiving a completed work package.

Managing stage boundaries

The Controlling a Stage process dictates what should be done within a stage, Managing Stage Boundaries (SB) dictates what should be done towards the end of a stage. Most obviously, the next stage should be planned and the overall project plan, risk log and business case amended as necessary. The process also covers what should be done for a stage that has gone outside its tolerance levels. Finally, the process dictates how the end of the stage should be reported.

Key activities include: planning a stage; updating a project plan; updating a project business case; updating the risk log; reporting stage end; and producing an exception plan.

Closing a project

This covers the things that should be done at the end of a project. The project should be formally de-commissioned (and resources freed up for allocation to other activities), follow on actions should be identified and the project itself be formally evaluated.

Key activities include: decommissioning a project; identifying follow-on actions; and project evaluation review.

Techniques

The PRINCE2 method works with most project management techniques but specifically describes the following:

Quality Review Technique

The quality review technique ensures a project's products are of the required standard (i.e. meet defined quality criteria). This takes place in a quality review meeting, which identifies errors in the product. The quality review meeting will not attempt to solve the problems it identifies. The meeting brings together people who have an interest in the project's outputs (or products) and people on the project team able to address issues identified.

There are defined roles including a Producer and Scribe.

More about Quality Assurance.

Exams, accreditation and training

Accreditation is governed by the passing of two exams – the Foundation and the Practitioner. The Foundation exam is a one-hour, multiple choice exam. The Practitioner exam lasts for 2.5 hours, and is an objective-testing multiple-choice exam. Around the world, exams are administered by the APM Group. The successful candidate register can be searched on the web.[9]

It is possible for individuals with project management experience to self-study for the exams but a number of training organisations offer courses, many of which also include exam entry in the fee. There is a mandatory accreditation scheme for training providers, run by the APM Group, which provides them with access to the official PRINCE2 examinations.

PRINCE2 Practitioners must retake the Practitioner exam every 5 years to remain accredited. This re-registration comprises a 1-hour examination set at the same standard as the Practitioner examination.[10] Trainers must be re-accredited every 3 years and undergo a surveillance check (either in the form of a visit by an assessor to a training course or a telephone interview of their professional knowledge by an assessor) every 12 months[citation needed].

Scalability

Project management is a complex discipline and it would be wrong to assume that blind application of PRINCE2 will result in a successful project. By the same token, it would be wrong to assume that every aspect of PRINCE2 will be applicable to every project. For this reason every process has a note on scalability. This provides guidance to the project manager (and others involved in the project) as to how much of the process to apply. The positive aspect of this is that PRINCE2 can be tailored to the needs of a particular project. The negative aspect is that many of the essential elements of PRINCE2 can be omitted sometimes resulting in a PINO project – Prince in Name Only. In order to counter this, APM Group have defined the concept of a PRINCE2 Maturity Model[11].

Adoption

PRINCE2, as a method and a certification, is adopted in most of Western Europe and Australia. The PMI and its certification, the PMP, are highly dominant in the US.[citation needed]

[edit] See also

List of project management topics

References

[edit] External links

 

Gerelateerd
0
Uw beoordeling Geen
Aangemaakt op: vr, 16/04/2010 - 05:38
Laatst aangepast op: vr, 27/04/2012 - 11:16

Hebt u nog een vraag?

Hebt u nog een vraag in dit verband, klik dan hier om uw vraag aan ons te stellen, of meteen een afspraak te maken voor een consultatie.

Aanvulling

Heeft u een suggestie, aanvulling of voorstel tot correctie met betrekking tot deze pagina? Gebruik dit adres om het te melden.