Project Team Roles and Responsibilities

From apppm
(Difference between revisions)
Jump to: navigation, search
(Background)
(Background)
Line 21: Line 21:
  
 
==Background==
 
==Background==
 
''Big idea: describe the tool, concept or theory and explain its purpose. The section should reflect the current state of the art on the topic''
 
''Is the argument clear? Is there a logical flow to the article? Does one part build upon the other? Is the article consistent in its argument and free of ''contradictions?''
 
  
 
Before approaching a process of assigning roles and responsibilities to the Project Team, it is essential to correctly define a project size.
 
Before approaching a process of assigning roles and responsibilities to the Project Team, it is essential to correctly define a project size.

Revision as of 10:16, 19 February 2018

Contents

Abstract

Without a doubt the human role is an inseparable part of the Project Management. Hiring and involving the right people who will be committed throughout the whole Project Life Cycle [glossary 1] is of critical importance.[1] Thus Organizational Planning plays an important role within Project Human Resources Management [glossary 2] as its final output significantly effects project overall performance.[2] The output consists of, among others:

  • Assigning roles and responsibilities to everyone involved, which is a process of defining who does what (roles) and who decides what (responsibilities) and it is considered to be a solid foundation of every project and therefore - to be successfully executed. [3]
  • Selecting a Project Team[glossary 3] and staffing management plan
  • Creating an organizational chart

It should always link to the Project Scope, defined as "work required to output a project’s deliverable", [4] hence nothing is omitted as well as just value adding deliverables are performed. This is why it is essential to clearly allocate roles and define responsibilities for everyone within Project Team already from the very beginning of the Project Life Cycle, namely the Initial Phase (?).

This article focuses on the method of assigning roles and responsibilities to the Project Team members and applying adequate tools to ensure it is preserved and maintained properly during the Project Life Cycle. The objective of the article is to provide project managers with instructions and application-ready templates. For superior understanding, methodology described in the article applies to a medium size projects and refers to the leading pharmaceutical industry best practices.

Motivation

It is project managers' role to build a Project Team, adequately assign roles and responsibilities to its members and make sure everything established is clear for everyone throughout the Project Life Cycle. There are multiple reasons why project managers should have a careful approach to those processes.

First of all, it is essential to define a project size beforehand to support effective project execution. The more people are needed on board, the more roles and responsibilities need to be allocated among them. There are a certain roles which should be performed in medium and large projects but not necessarily in a small ones. This is also explained in detail further in the article.

Secondly, it happens that roles and responsibilities are assigned to people who do not have neither an interest nor a required knowledge or an experience to perform successfully. As a result, the project scope might become unsettled, deliverables might not be valueable as expected and in the end - a project might run behind a schedule.

Thirdly, transparency is a key for the Project Team to be effective. Once roles and responsibilities are assigned, project manager should make sure everything is documented as well as transparent and clear for everyone involved, otherwise there is a risk of not delivering what intended. Examples of tools and methods that support project managers in performing this processes are described further in the article.

Background

Before approaching a process of assigning roles and responsibilities to the Project Team, it is essential to correctly define a project size. Taking under consideration the pharmaceutical company best practices, a project size is defined mostly based on the Total Project Cost (TPC) [glossary 4] and distributes as followed:

  • Low-complexity projects (below 10 million DKK)
  • Medium-complexity projects (more than 10 but less than 100 million DKK)
  • Large-complexity projects (above 100 million DKK)

The article focuses on the Medium-complexity projects to cover the steps that do not necessarily appear in the Low-complexity projects but are relevant for project managers to be similar with.

Figure 1: Project Human Resource Management Overview, inspired by the PMBOK® Guide

Introduction to Human Resource Management

Big idea: describe the tool, concept or theory and explain its purpose. The section should reflect the current state of the art on the topic Is the argument clear? Is there a logical flow to the article? Does one part build upon the other? Is the article consistent in its argument and free of contradictions?

Project Team roles and responsibilities

Based on Harvard Business Review, when project manager is managing a project, the right people need to be on board to meet project objectives. Moreover, those people need to have a clear understanding of what their roles and responsibilities are.[5] When it comes to a medium and large size projects, where more people need to be involved, therefore Project Team is respectively more extensive rather than in small projects where some roles can be omitted. Regarding to the pharmaceutical best practices terminology, Project Organization is an equivalent of Project Team and consists of:

  • Project owner
  • Steering committee
  • Reference group - optional
  • Project manager
  • Project members

Tools Application

Application: provide guidance on how to use the tool, concept or theory and when it is applicable

Belbin Team Roles

Responsibility Assignment Matrix

Responsibility Assignment Matrix is a tool which visualizes assigned roles and responsibilities and as a result, makes it being transparent for everyone engaged. Its layout depends on a project size. In lower-level projects roles and responsibilities are assigned individually to each of the Project Team members. Nevertheless, the larger a project is the more people need to be involved. Thus, in larger-level projects roles and responsibilities are assessed to groups of people rather than to the individuals.

Organizational Chart

Organizational Breakdown Structure (OSB)

How to ensure responsibilities compliance

- Feedback template

Limitations

Limitations: critically reflect on the tool/concept/theory and its application context. What can it do, what can it not do? Under what circumstances should it be used, and when not? How does it compare to the “status quo” of the standards – is it part of it, or does it extent them? Discuss your article in the context of key readings / resources provided in class. Substantiate your claims with literature

- Roles and Responsibilities need to be strongly link to the Project Scope - Roles and Responsibilities change over the Project Life Cycle - how to keep on track so resources are not wasted if there is no need for them anymore (how should they be released - reduces cost and eliminates uncertainty)

Discussion

Summary

Quality of the summary: Does the summary make the key focus, insights and/or contribution of the article clear?

Glossary

  1. Project Life Cycle: A time slot within a project phases are performed. In case of Project Management it has defined start and end dates.
  2. Project Human Resources Management: A set of processes within a project which ensure the most effective use of human resources.
  3. Project Team: A group of people created for a sole purpose of performing a certain project within its life cycle. The team is disbanded once the project is completed.
  4. Total Project Cost (TPC): A sum of Operational Expense (OPEX) and investment (CAPEX) including contingency sums.

Annotated bibliography

Provide key references (3-10), where a reader can find additional information on the subject. The article MUST make appropriate references to the reference material provided in class – either incorporating it as a source, or critically discussing aspects that are missing from it but covered by this article. Summarize and outline the relevance of each reference to the topic (around 100 words per reference). The bibliography is not counted in the suggested 3000 word target length of the article.

  • Project Management Institute. "A Guide to the Project Management Body of Knowledge (PMBOK® guide)". 1996 Edition.

This book includes a relevant theory, concepts, and terminology within Project Management.


References

  1. https://www.pmi.org/learning/featured-topics/resource Project Management Institute. Retrieved 12 February 2018.
  2. Page 31, 1996 ed. PMBOK® Guide
  3. Page 96, 1996 ed. PMBOK® Guide
  4. https://www.pmi.org/learning/featured-topics/scope Project Management Institute. Retrieved 15 February 2018.
  5. https://hbr.org/2016/11/five-critical-roles-in-project-management Five Critical Roles in Project Management by Harvard Business Review Staff. Retrieved 13 February 2018.
Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox