You are on page 1of 8

ROLES AND RESPONSIBILITIES

Project /
[name]
Department

Phase /
[phase]
Procedure

Status
(Choose [status - Completed, In Progress, Behind Schedule, On Hold, Discontinued]
one)

WBS Code TASKS / DELIVERABLES

[code] [activity name]


[code] [activity name]
[code] [activity name]
[code] [activity name]
[code] [activity name]
[code] [activity name]
[code] [activity name]
[code] [activity name]
[code] [activity name]
[code] [activity name]

GUIDE TO ABBREVIATIONS

Responsible - the person who actually owns the project, task, or work. An example would be the
R Project Manager. There should only be one "R" for each activity, but no activity should be missing an
"R". More than one "R" is called an overlap. A missing "R"

Accountable - the person who will sign off on the work and judging its completion and how it meets
A quality standards. This could be the Project Sponsor or whomever has final sign-of authority.

Consulted - the person who has the ability of knowledge needed to complete the work. These can be
C Stakeholders, Subject matter experts, or anyone else who is key to completing the work.

I Informed - people who must be kept informed of the work, but not necessarily consulted.

Note, some groups include a category entitled "S" for "Supports", in a variation called RASCI Chart.
S Supporting personnel or groups provide resources for a task to be performed.
INSTRUCTIONS

Identify all of the processes, activities involved and list them down the left side of the chart. So each
1 row is a separate activity.

Identify all of the roles on the project (mapping them to people if appropriate) and list them along the
2 top of the chart. So each column is a different role/person.

3 Identify who is responsible, accountable, consulted, and informed by filling in the cells for each activity.

Identify issues with the current roles. There should only be one "R" for each activity, but no activity
4 should be missing an "R". More than one "R" is called an overlap. A missing "R" is considered a gap in
responsibility.

Resolve issues with gaps and overlaps. Overlaps are typically resolved by taking a closer look at the
5 process or activity itself and selecting a logical high-level owner. Often one of the "R"s is someone
responsible for a subprocess or just a part of the
6 Perform a final cross-check to ensure that changes did not impact other RACI assignments.
D RESPONSIBILITIES MATRIX (RACI)

Date Updated [date]

[Name, Contact
Prepared by
Number]

[Name, Contact
Approved by
Number]

[role name] [role name] [role name] [role name] [role name] [role name]
[role name]
ROLES AND RESPONSIBILITIES

Project /
Headway / IT
Department

Phase /
Development / Create New User Account
Procedure

Status
(Choose In Progress
one)

WBS Code TASKS / DELIVERABLES

HW_D_1 Complete New User Access Form


HW_D_2 Review and Approve Request
HW_D_3 Create User Profile on System
HW_D_4 Final Alpha User Interface Prototype Ready
HW_D_5 Documentation--User Manual, Help, etc.
HW_D_6 System Test Plan and System Test Cases
HW_D_7 System Testing and System Test Report
HW_D_8 Final and Post-Mortem Reviews
HW_D_10 Beta Exit
HW_D_11 Notify Requester for GM Endorsement and Sign-off

GUIDE TO ABBREVIATIONS

Responsible - the person who actually owns the project, task, or work. An example would be the
R Project Manager. There should only be one "R" for each activity, but no activity should be missing an
"R". More than one "R" is called an overlap. A missing "R" is considered a gap in responsibility.

Accountable - the person who will sign off on the work and judging its completion and how it meets
A quality standards. This could be the Project Sponsor or whomever has final sign-of authority.

Consulted - the person who has the ability of knowledge needed to complete the work. These can be
C Stakeholders, Subject matter experts, or anyone else who is key to completing the work.

I Informed - people who must be kept informed of the work, but not necessarily consulted.

Note, some groups include a category entitled "S" for "Supports", in a variation called RASCI Chart.
S Supporting personnel or groups provide resources for a task to be performed.
INSTRUCTIONS

Identify all of the processes, activities involved and list them down the left side of the chart. So each
1 row is a separate activity.

Identify all of the roles on the project (mapping them to people if appropriate) and list them along the
2 top of the chart. So each column is a different role/person.

3 Identify who is responsible, accountable, consulted, and informed by filling in the cells for each activity.

Identify issues with the current roles. There should only be one "R" for each activity, but no activity
4 should be missing an "R". More than one "R" is called an overlap. A missing "R" is considered a gap in
responsibility.

Resolve issues with gaps and overlaps. Overlaps are typically resolved by taking a closer look at the
process or activity itself and selecting a logical high-level owner. Often one of the "R"s is someone
5 responsible for a subprocess or just a part of the overall activity. Gaps are usually less difficult to
resolve. You just select the appropriate person to be responsible for the process or task.

6 Perform a final cross-check to ensure that changes did not impact other RACI assignments.
D RESPONSIBILITIES MATRIX (RACI)

Date Updated 11/21/2006

John Smith
Prepared by
(555)555-5555

John Smith
Approved by
(555)555-5555

Project Project Quality Communication


Project Team System Owner
Manager Sponsor Manager Manager

R A C C I

C R, A I I R, A
C A I I I I
R C C I C
C C A R I
C I C R I
R I C I C
C C R C C
R C I C
C I I I R
Security
Manager

C
R
C
I
C
C
C
C
I

You might also like