Projects in Controlled Environments, a process-based approach for project management

From apppm
Revision as of 20:33, 9 September 2015 by S150905 (Talk | contribs)

Jump to: navigation, search

Project Management is a field based on a conspicuous level of uncertainty, the use of appropriate methods and tools influences the risk reduction of project failures. In this article we are going to illustrate the so-called PRINCE2 method, focused on process and expenditure control

Contents

Overviews

PRINCE2 possesses all the necessary element to keep all these aspect under control It is owned by a stable public authority, the Office of Government Commerce (OGC), and is available free of charge in the public domain. PRINCE2, apart from allow more efficient control of development resources, it gives controlled management of change by the business (its investment and ROI) and an active involvement of the final product's users throughout its development. This to ensure that the output of the project will meet the functional, service and management requirements of final users.


[1] [2] [3] [4] [5] [6] [7]


The seven Principles

The method is grounded over seven principles. Everyone of them can be apply to every kind of project, they are also self-validating and they are empowering, so the are able to give at users the capacity to to shape the management of the project. These are[8]:

  1. Continued business justification;
  2. Learn from experience;
  3. Defined roles and responsibilities;
  4. Manage by stages;
  5. Manage by exception;
  6. Focus on products;
  7. Tailored to suit the project environment.

Continued business justification

Learn from experience

Defined roles and responsibilities

Manage by stages

Manage by exception

Focus on products

Tailored to suit the project environment

The Structure

Process

Directing a Project

Starting Up a Project

Initiating a Project

Controlling Stage

Managing Product Delivery

Managing a Stage Boundary

Closing a Project

Themes

Business Case

Organization

Plans

Progress

Risk

Quality

Change

Techniques

PRINCE2 techniques are not mandatory. A company may already have, e.g., a quality checking technique, which it wishes to use in preference to the PRINCE2 quality review.


References

  1. PRINCE2™ A Pratical Handboob (Third Edition), 2010, Colin Bentler, Elsevier Ltd.
  2. Pratical PRINCE2, 2005, Colin Bentler, TSO.
  3. Prince2 100 Success Secrets - The Missing Foundation and Practitioner Exam Training, Certification and Project Management Guide, 2008, Gerard Blokdijk, Emereo Pty Limited.
  4. Managing Successful Project with PRINCE2™, 2009, Office of Government Commerce, TSO.
  5. Agile project management: running PRINCE2™ projects with DSDM™ Atern™, 2007, Keith Richards, ‎OGC - Office of Government Commerce, ‎Eksempelvisning.
  6. Directing successful projects with PRINCE2, 2009, Office of Government Commerce, ‎Stationery Office (Great Britain), ‎Eksempelvisning.
  7. Improving project performance using the PRINCE2 maturity model, 2007, Andy Murray, ‎Mike Ward, ‎Eksempelvisning.
  8. PRINCE2™ Revealed (Second Edition), 2010, Colin Bentler, Elsevier Ltd.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox