Misplaced Pages

Responsibility Assignment Matrix: Difference between revisions

Article snapshot taken from Wikipedia with creative commons attribution-sharealike license. Give it a read and then ask your questions in the chat. We can research this topic together.
Browse history interactively← Previous editContent deleted Content addedVisualWikitext
Revision as of 11:40, 14 February 2009 editJeepday (talk | contribs)Administrators28,700 edits Misplaced Pages:Unreferenced articles; you can help!← Previous edit Latest revision as of 16:28, 10 June 2017 edit undoTom.Reding (talk | contribs)Autopatrolled, Extended confirmed users, Page movers, Template editors3,879,760 editsm +{{Redirect category shell}} for multiple-{{R}} #Rs using AWB 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
#REDIRECT ]
{{citationstyle}}
{{onesource}}


{{Redirect category shell|1=
'''Responsibility assignment matrix''' (RAM) is typically used to link activities to resources to ensure that the scope's components are each assigned to an individual or team ( Source: ""). One type of RAM is based on the RACI format (Responsible, Accountable, Consult and Inform). This type of RAM is called a RACI chart, because it assigns the role that the resource is to play for each given activity. These charts can be constructed at a high level (general areas) or at a detailed level (low level tasks). A table is drawn, usually with Activities on the vertical edge (] or WBS) and Resources on the horizontal edge (Organization Breakdown Structure). Not every resource will have an entry for every activity. As an illustration, please consider this simple chart:
{{R with history}}

{{R from other capitalisation}}
{| border="1" cellspacing="0" cellpadding="5" align="center"
⚫ }}
! ACTIVITIES
! George
! Glenda
! Tom
! Susan
! Mary
! Craig
|-
| Investigate
| R
| A
| I
| C
| C
|
|-
| Design SW
| I
| A
| C
|  
|  
| R
|-
| UAT Plan
| R
| A
| I
|  
|  
| C
|-
| Phase Signoff
| R
| A
| I
| C
| C
| C
|-
⚫ |}
Two other RAM versions are the RACI-VS format, adding the additional roles of Verifies and Signs, and the RASCI version, adding the additional Supportive role. The definition of each role is listed below:

{| border="1" cellspacing="0" cellpadding="5" align="center"
! Role
! Definition
|-
| Responsible
| This role conducts the actual work/owns the problem. There should be at least one R (otherwise the work is not performed) and there can be multiple Rs (this is called teamworking)
|-
| Accountable
| This role approves the completed work and is held fully accountable for it. There should be one and only one A.
|-
| Supportive
| This role provides additional resources to conduct the work or plays a supportive role in implementation. Optional.
|-
| Consulted
| This role has the information and/or capability to complete the work. Two-way communication (typically between R and C). Optional.
|-
| Informed
| This role is to be informed of progress and results. One-way communication (typically from R to I). Optional.
|-
| Verifies
| This role checks the work to ensure that it meets all defined criteria and standards. Optional.
|-
| Signs
| This role signs off on the completed work. Optional.
|}

A responsibility matrix can also be known as a linear responsibility chart and can be used to show who is responsible and at what level. For example each row could represent a task and each column a person, the boxes could then be completed with the letters P (Prime support), S (Support) and N (Notify).

LRC is often referred as the responsibility assignment matrix (RAM). It identifies the participants, and to which degree each activity will be performed and/or decisions will be made.

== See also ==

* ]
* For more information on RAM, visit http://www.pmi.org

]


{{business-stub}}

]
]
]

Latest revision as of 16:28, 10 June 2017

Redirect to:

This page is a redirect. The following categories are used to track and monitor this redirect:
  • With history: This is a redirect from a page containing substantive page history. This page is kept as a redirect to preserve its former content and attributions. Please do not remove the tag that generates this text (unless the need to recreate content on this page has been demonstrated), nor delete this page.
    • This template should not be used for redirects having some edit history but no meaningful content in their previous versions, nor for redirects created as a result of a page merge (use {{R from merge}} instead), nor for redirects from a title that forms a historic part of Misplaced Pages (use {{R with old history}} instead).
  • From other capitalisation: This is a redirect from a title with another method of capitalisation. It leads to the title in accordance with the Misplaced Pages naming conventions for capitalisation, or it leads to a title that is associated in some way with the conventional capitalisation of this redirect title. This may help writing, searching and international language issues.
    • If this redirect is an incorrect capitalisation, then {{R from miscapitalisation}} should be used instead, and pages that use this link should be updated to link directly to the target. Miscapitalisations can be tagged in any namespace.
    • Use this rcat to tag only mainspace redirects; when other capitalisations are in other namespaces, use {{R from modification}} instead.
When appropriate, protection levels are automatically sensed, described and categorized.