Mimir - The Professional Project Guide

Project Roles

Project roles are templates describing the major activities of all project members. Every team member inside a project is assigned to a certain role. This ensures a clear assignment of tasks inside the team as well as fitting interfaces between all team members.


Role Overview

 

Roles

Click on the boxes to get more information on the individual roles.


Role Types

Project Team

The project core team is a project organization. The team members are responsible for a dedicated project or product line of projects. Once the project is finished, the team members are assigned to new projects. The team members are usually paid directly by the project. The team members (except the QA-Engineer) report directly to the project manager.

Supporting Roles

Supporting roles are organizational roles. The persons fulfilling these roles are usually highly specialized and provide services to all projects of the organization.


Recommendations for Staffing

Allocating the right roles to the right persons is one of the most challenging task in a project. Depending on the project characteristics, different aspects have to be considered. In complex projects where the development is spread over several locations different staffing aspects have to be considered compared to a small single site project. To support the project manager in the role assignment, every role has a section with recommendations for different company and project categories. There are three predefined categories:

  • Category A - Small Projects
  • Category B - Medium Projects
  • Category C - Large Projects

The category depends on organizational, technical and functional parameters. The following cube of complexity maps the presented categories to these parameters:

Cube of Complexity

The following criteria catalogue provides a guidance for deciding the class of the project. These categories are used in the role descriptions within the section "Recommendations for Staffing".

Project Category A Small Projects

Organization

  • The company and the project team is located at one location.
  • All or most development work is done inside the company.
  • The project team consists of up to 5 persons.
  • The project is scheduled for up to 6 month.
  • The project budget is comparable small.
  • The business importance is low.

Technology

  • The technology used for the project is of proven stability and quality (e.g. exiting microcontroller which has been used in prior projects).
  • The team has experience with the technology used for the project.

Functionality

  • Products with similar functionalities have been developed before.
  • The requirements at project start have a high maturity.
  • The customer is well known to the project team, communication chains are established.
Project Category B Medium Projects

Organization

  • The company and project team is located at more than one location but inside the same country or region.
  • Development work is outsourced or distributed between the development sites but the subcontractors are located in the same country or region.
  • The project team consists of up to 25 persons.
  • The project is scheduled for up to 18 month.
  • The project budget is average.
  • The business importance is medium.

Technology

  • The technology used for the project is new to the team (e.g. a newly developed ASIC).

Functionality

  • The functionality is new to the team (e.g. a new product).
  • The requirements at project start are vague.
  • Many change requests are expected during project runtime.
  • The customer is well known to the project team, communication chains are established.
Project Category C  Large Projects
  • The company and project team is spread over several worldwide locations.
  • Major parts of the development work are outsourced or spread over the worldwide locations.
  • The project team consists of more than 25 developer.
  • The project takes longer than 18 month.
  • The project budget is significantly above average.
  • The strategic importance of the project is high.

Technology

  • The technology used for the project is new to the team (e.g. a newly developed ASIC).

Functionality

  • The functionality is new to the team (e.g. a new product).
  • The requirements at project start are vague.
  • Many change requests are expected during project runtime.
  • The customer is new to the team.

 

 

Mimir v01.20rel © H-DA / HOOD / Windhoff / Bär, Pfitzer & Partner 2011. All rights reserved. $Revision: 903 $