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

Popular posts from this blog

What are Important Roles in Scrum-Agile Teams?

The Primary Team roles in scrum are named as • Product Owner  • Scrum Master • Development Team Scrum Master, Product Owner, and Team are considered as people who are committed to the project while customers and executive management are considered as involved but not committed to the project. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team.  Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity. Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of “Done” product ensure a potentially useful version of working product is always available. All the roles are based on the concept of “S...

What is Definition of Done?

Done Criteria are a set of rules that are applicable to all User Stories. A clear definition of done is critical because it removes ambiguity from requirements and helps the team adhere to mandatory quality norms. This clear definition is used to create the Done Criteria when a Prioritized Product Backlog is prepared. Definition of done is crucial to a highly functioning Scrum team. The following are characteristics that you should look for in your team’s definition of done. Verifying that your team’s DoD meets these criteria will ensure that you are delivering features that are truly done, not only in terms of functionality but in terms of quality as well. DoD is a checklist of valuable activities required to produce software. Definition of done is a simple list of activities (writing code, coding comments, unit testing, integration testing, release notes, design documents, etc.) that add verifiable/demonstrable value to the product. Focusing on value-added step...

Five Phases of Agile Project

There are FIVE phases that an Agile project goes thru. The FIVE phases are ·         Envision ·         Speculate ·         Explore ·         Adapt ·         Close Envision Phase : – This phase is to determine the product vision and project scope, the project community, and how the team will work together. The term ‘envision’ is a clear departure from traditional phase names such as initiate and plan, which while subtle, is also significant. This is because when envisioning you inadvertently accept a level of mishap and are therefore ready to make any necessary adjustments, in contrast to a set plan which has more rigorous connotations. The envision phase covers the ‘Who? What? And how?’ Speculation Phase:  Unlike planning, speculating esta...