RACI DIAGRAM

A 'RACI' diagram is used to describe the roles and responsibilities of various teams or people in delivering a project. It is especially useful in clarifying roles and responsibilities in cross-functional/departmental projects and initiatives.

Contents
Methodology
Example
Variations
See also

Methodology


The RACI diagram splits project tasks into four participatory responsibility types, which are then assigned to different roles in the project. These responsibilities types make up the acronym ''RACI''.

★ 'R'esponsible - Those who do work to achieve the task. There can be multiple resources responsible.

★ 'A'ccountable - The resource ultimately accountable for the completion of the task. There must be exactly one 'A' specified for each task.

★ 'C'onsulted - Those whose opinions are sought. Two-way communication.

★ 'I'nformed - Those who are kept up-to-date on progress. One-way communication.
It is generally recommended that each role in the project for each task receive at most one of the participatory role types. Although some companies and organizations do allow, for example, double participatory types, this generally implies that the roles have not yet been truly resolved and so impedes the value of the RACI approach in clarifing each role on each task.
There are a number of variations to this scheme, some adding additional roles, another changing the 'R' and 'A' definitions; see below under ''Variations''.

Example


The following is an example of a RACI Diagram, showing how individual tasks are assigned to different roles.
Example of a RACI Diagram

In the example, the Business Owner is Accountable in communicating Business Policy and must inform the Business Program Manager and Business Process Manager.

Variations


' RACI-VS' or 'VARISC'
This is an expanded version which adds two additional roles:

★ 'V'erifies - Those who check whether the product meets the acceptance criteria set forth in the product description.

★ 'S'igns off - Those who approve the 'V' decision and authorize the product hand-off. It seems to make sense that the 'S' for each terminal element should be the party with 'A' for its successor.
'CAIRO' or 'RACIO'
This is an expanded version which uses the same basic designations (reordered, in the case of CAIRO) with the addition of 'O' (Out of the Loop, or omitted), designating individuals or groups who are specifically not part of the task. Specifying that a resource has no role or responsibility can be as beneficial to a task's completion as specifying those who do have a role.
'RASCI'
This breaks the Responsible role into:

★ 'R'esponsible - Those who are responsible for the task, ensuring that it is done as per the approver.

★ 'S'upport - Resources allocated to Responsible. Unlike Consult, who may aid in the task, Support may be tasked with work.
'RACI' (alternative scheme)
There is an alternative coding, less widely published but used by some practitioners and process mapping software, which modifies the application of the 'R' and 'A' codes of the original scheme. The overall methodology remains the same but this alternative avoids potential confusion of the terms ''accountable'' and ''responsible'' — understood by management professionals but not always so clearly differentiated by others:

★ 'R'esponsible - Those responsible for the performance of the task. There should be exactly one person with this assignment for each task.

★ 'A'ssists - Those who assist the responsible person in conducting the task, and may do the bulk of the work.

★ 'C'onsulted - Those whose opinions are sought. Two-way communication.

★ 'I'nformed - Those who are kept up-to-date on progress. One-way communication.

See also



Responsibility assignment matrix

This article provided by Wikipedia. To edit the contents of this article, click here for original source.

psst.. try this: add to faves
Featured Companies
Vacation By VVacation By V