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

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...
1 comment
Read more

Agile Administration in Tooling and Tool Integration

Tools are inherent to our jobs, inherent to how we solve the problems we face each day. Our comfort level with the set of tools that are available to us, and our ability to adapt to new tools as they evolve and shape our thoughts and ideas. The availability of collective knowledge within the palm of your hand combined with the collaboration across organization and company boundaries through open source software is dramatically disrupting the status quo of work. Companies mired in managing infrastructure configuration management by hand with unknown numbers of divergent systems, unable to quickly change and respond to market demands will struggle against their counterparts who have managed to contain their complexity on one axis through infrastructure automation. While it is possible to manage servers by hand, or even artisinally crafted shell scripts, a proper configuration management tool is invaluable especially as your environment and team changes. Even the best software developers ...
Read more

Tracking and Communicating Progress in Agile

Information radiators are meant to display information at a public place so that the information can be noticed by as many people as possible without making a conscious effort to do so. The idea of information radiator was invented by Alister Cockburn, who was a big believer in effective and timely communication. Information Radiators should display the current information about the project whatever is critical for the team to learn. It could include Schedule, tasks, issues, progress etc. The Most common forms of Information Radiators are ·         TaskBoards or Kanban Boards ·         Big Visible Charts such as BurnDown Charts ·         Street Lights and Lava Lamps Characteristics of Information Radiators which make the Information Radiators work ·         Simplicity : The information Radi...
Read more