This project is read-only.



All methodologies and processes discus roles, their relations and responsibilities. Every methodology has it’s own preferred way of organizing teams, CMM hierarchy and Agile open. To be methodology independed he TMap process template talks about roles in it’s most pure form, a roll does something that needs to be done, if it’s organized in a formal CMM way with a lot of documents or its done in an Agile way together with the team. In this guidance rolls contain a set of tasks logical grouped by knowledge area. The introduction of a roll starts with an overview of preferred knowledge to fulfill the tasks described.

During the creation of the master test plan the organization is defined. Required roles are determined and tasks, authorisations and responsibilities are allocated.

The execution of test activities in a project or in the line requires that the tasks are defined and that the executor of the tasks has the right knowledge and competencies. Roles and positions can be distinguished in this respect. A role is the description of one or more tasks with the required knowledge and competencies. There are roles that match positions one-on-one. There are also roles that do not exist as a position.
Differences and similarities between roles and positions:
  • A role aims at fulfilling tasks for the test project or permanent test organisation.
  • A position focuses on the employee and his place in the career cube.
  • They share the tasks to be executed and the required knowledge competencies.

Specific Test Roles

Test manager
Test coordinator
Test infrastructure coordinator

Last edited Nov 6, 2009 at 2:39 PM by ClemensReijnen, version 6


No comments yet.