Skip to main content

PRINCE2's Project Organisation


PRINCE2's organisation theme defines the Project Team or organisation. It establishes the project's structure of accountability and responsibilities.

As PRINCE2 is based on a customer/supplier environment, it assumes that there will be a customer who will specify the desired result and probably pay for the project, and a supplier who will provide the resources and skills to deliver that result.


A successful project management team should have business, user and supplier stakeholder representation.


Business

  • The products of the project should meet a business need which will justify the investment in the project.
  • Should also provide value for money.
  • The Executive looks after business interests

User


The user viewpoint should represent those individuals or groups for whom some or all of the following will apply:

  • They will use the outputs of the project to realize the benefits after the project is complete
  • They will operate, maintain or support the project’s outputs
  • The outputs of the project will impact them
  • The Senior User(s) will represent this stakeholder interest on the Project Board

Supplier

  • The creation of the project’s outputs will need resources with certain skills. The supplier viewpoint should represent those who will provide the necessary skills and produce the project product or Specialist Product.
  • The Senior Supplier(s) will represent this stakeholder interest on the Project Board.
  • ’Customer’ can usually be interpreted as a collective term for business and user interests

Labels:

Popular posts from this blog

Scrum Timebox

Scrum relies heavily on the concept of Timebox. Timebox is setting a fixed time limit to any activity and letting other characteristics such as Scope vary. A time box could be ·           A Meeting ·           A Sprint ·           A Test activity ·           Development Activity ·           Or Practically anything such as you chatting with your friend on social networking site. The fact about timebox is that the time is limited. You can adjust other parameters such as ·           How much you can get done ·           Which item you must prioritize ·           However, deadlines cannot be moved. In Scrum, all the project iterations, meetings must be timeboxed and time limits be respected. This is very important and non-negotiable aspect of Scrum. Lets look at how a timebox actually works. ·           Timebox can be of any duration  - hours, months, years ·           It is essentially a control mechanism to ensure how much time you wish to devote
Post a Comment
Read more

The Service Value System - Continual improvement | ITIL V4 Certification

Continual Improvement Continual improvement takes place in all areas of the organization and at all levels, from strategic to operational. When provisioning a service we should always keep continual improvement in mind, and should always be looking for opportunities to improve. To support continual improvement at all levels, the ITIL® SVS includes: ITIL® Continual Improvement Model provides organizations with a structured approach to implementing improvements Improve Service Value Chain Activity Continual Improvement Practice Continual Improvement Model Continual Improvement Model can be used as a high-level guide to support improvement initiatives.  The model supports an iterative approach to improvement, dividing work into manageable pieces with separate goals that can be achieved incrementally. The scope and details of each step of the model will vary significantly based on the subject and the type of improvement The steps of this model do not need to be carried out in a linear fash
Read more