Editing Responsibility assignment matrix (section)

== Alternatives ==
There are a number of alternatives to the RACI participation types:

=== PARIS ===
:This is an early version<ref>{{cite book |title= A Guide to the Project Management Body of Knowledge |publisher= Project Management Institute |year= 2000 |page= [https://archive.org/details/guidetoprojectma00proj_0/page/111 111] |isbn= 1-880410-22-2 |url= https://archive.org/details/guidetoprojectma00proj_0/page/111 }}</ref> of a responsibility assignment matrix, with the roles defined as:

:; ''Participant''
:
:; ''Accountable''
:
:; ''Review required''
:
:; ''Input required''
:
:; ''Sign-off required''

=== PACSI ===
: This is a version very useful to organizations where the output of activities under the accountability of a single person/function can be reviewed and vetoed by multiple stakeholders, due to the collaborative nature of the culture.

:; ''Perform''
:
:: The person/function carrying out the activity.

:; ''Accountable''
:
:: The person/function ultimately answerable for the correct and thorough completion of the deliverable or task, and often the one who delegates the work to the performer.

:; ''Control''
:: The person/function reviewing the result of the activity. They have a right of veto; their advice is binding.

:; ''Suggest''
:
:: The person/function consulted to give advice based upon recognized expertise. The advice is non-binding.

:; ''Informed''
:
:: The person/function who must be informed of the result of the activity.

=== RASIC or RASCI ===
:This is an expanded version<ref>{{cite book |last= Hightower |first= Rose |title= Internal controls policies and procedures |publisher= John Wiley & Sons |year= 2008 |page= 83 | isbn= 978-0-470-28717-0}}</ref> of the standard RACI, less frequently known as ''RASCI'',<ref>{{cite book |last= Baker |first= Dean |title= Multi-Company Project Management: Maximizing Business Results Through Strategic Collaboration |publisher= J Ross | year = 2009 |page= 58 |isbn= 978-1-60427-035-8}}</ref> breaking the ''responsible'' participation into:

:; ''Responsible''
:
::Those responsible for the task, who ensure that it is done as per the ''approver''

:; ''Support''
:: Resources allocated to ''responsible''. Unlike ''consulted'', who may provide input to the task, ''support'' helps complete the task.

=== RASI ===
:This is an alternative version<ref name="LCE Training">{{cite book |last1= Mikes |first1= Joe |last2=Denton |first2=Tara |title= Training Speeds Continuous Improvement |publisher= Life Cycle Engineering |year= 2011 |url = https://www.lce.com/Training-Speeds-Continuous-Improvement-1271.html}}</ref> of the standard RACI, foregoing the ''consulted'' participation and replacing it with:
 
:; ''Support''
:: Resources which play a supporting role in implementation.

===  RACI + F ===

:This is an expanded version of the standard RACI, with an additional participation type: Facilitate. This variation was introduced by Christophe Le Coent in 2012.<ref name="Archived copy">{{cite web |url=https://www.scrumalliance.org/community/articles/2012/june/the-raci-f-matrix |title=The RACI+F Matrix - Scrum Alliance |website=www.scrumalliance.org |access-date=10 August 2022 |archive-url=https://web.archive.org/web/20171016061719/https://www.scrumalliance.org/community/articles/2012/june/the-raci-f-matrix |archive-date=16 October 2017 |url-status=dead}}</ref> Coent argued that the facilitator or coach role is important in agile software development environments and should therefore be explicitly included in the RAM.<ref name="Archived copy"/> The use of RAM in Agile environments is considered contentious because some practitioners believe that everyone working in an agile team should be jointly responsible and accountable.<ref>{{cite web | url=https://www.hotpmo.com/management-models/raci-matrix-definition-and-example-how-to/ | title=RACI Matrix &#124; Definition and Example &#124; How to }}</ref>

:; ''Facilitates'' 
:: Facilitate activities during a Scrum project.

===  RACIQ ===

:This is an expanded version of the standard RACI, with an additional participation type:

:; ''Quality review'' 
:: Those who check whether the product meets the quality requirements.

===  RACI-VS ===
:This is an expanded version<ref name="slaguide"/> of the standard RACI, with two additional participation types:

:; ''Verifier''
:: Those who check whether the [[product breakdown structure product]] meets the [[acceptance testing acceptance criteria]] set forth in the [[product description]].

:; ''Signatory''
:
::Those who approve the ''verify'' decision and authorize the product hand-off. The ''signatory'' should be the party being ''accountable'' for its success.

=== CAIRO ===
:This is an expanded version<ref>{{cite book |last= Bolman |first= Lee |title= Reframing organizations: artistry, choice, and leadership |publisher= John Wiley & Sons |year= 2008 |page= [https://archive.org/details/reframingorganiz00bolm_1/page/112 112] |isbn= 978-0-7879-8799-2 |url= https://archive.org/details/reframingorganiz00bolm_1/page/112 }}</ref> of the standard RACI, also known as ''RACIO''<ref>{{cite book |last= Dickstein |first= Dennis |title = No Excuses: A Business Process Approach to Managing Operational Risk |publisher= John Wiley & Sons | year = 2008 |isbn= 978-0-470-48110-3}}</ref> with one additional participation type.

:; ''Out of the loop'' (or ''omitted'')
:: Designating individuals or groups who are specifically not part of the task. Specifying that a resource does not participate can be as beneficial to a task's completion as specifying those who do participate.

=== DACI ===
:Another version that has been used to centralize decision making, and clarify who can re-open discussions.<ref>{{cite book |last= Kendrick |first= Tom |title= Results without authority: controlling a project when the team doesn't report to you |publisher= AMACOM Books, division of the American Management Association |year= 2006 |page= [https://archive.org/details/resultswithoutau00tomk/page/106 106] |isbn= 0-8144-7343-1 |url= https://archive.org/details/resultswithoutau00tomk/page/106 }}</ref>

:; ''Driver''
:: A single ''driver'' of overall project like the person steering a car.

:; ''Approver''
:: One or more ''approver''s who make most project decisions, and are responsible if it fails.

:; ''Contributors''
:: Are the worker-bees who are responsible for deliverables; and with whom there is two-way communication.

:; ''Informed''
:: Those who are impacted by the project and are provided status and informed of decisions; and with whom there is one-way communication.

=== RAPID ===
:Another tool used to clarify decision roles and thereby improve decision making, is '''RAPID''', which was created by and is a registered trademark of [[Bain & Company]].

:; ''Recommend''
:: The ''recommend'' role typically involves 80 percent of the work in a decision. The recommender gathers relevant input and proposes a course of action—sometimes alternative courses, complete with pros and cons so that the decision maker's choices are as clear, simple and timely as possible.

:; ''Agree''
:: The ''agree'' role represents a formal approval of a recommendation. The 'A' and the 'R' should work together to come to a mutually satisfactory proposal to bring forward to the decider. But not all decisions will need an agree role, as this is typically reserved for those situations where some form of regulatory or compliance sign-off is required.

:; ''Perform''
:: The ''perform'' role defines who is accountable for executing or implementing the decision once it is made. Best-practice companies typically define P's and gather input from them early in the process.

:; ''Input''
:: The ''input'' role provides relevant information and facts so that the recommender and decider can assess all the relevant facts to make the right decision. However, the 'I' role is strictly advisory. Recommenders should consider all input, but they don't have to reflect every point of view in the final recommendation.

:; ''Decide''
:: The ''decide'' role is for the single person who ultimately is accountable for making the final decision, committing the group to action and ensuring the decision gets implemented.

=== RATSI ===
:Another tool used in organization design or roles analysis.

:; ''Responsibility''
:: Identify who is in charge of making sure the work is done.

:; ''Authority''
:: Identify who has final decision power on the work.

:; ''Task''
:: Identify who actually does the work.

:; ''Support''
:: Identify who is involved to provide support to the work.

:; ''Informed''
:: Identify who is informed that the work has been done (or will be started)

=== DRASCI ===
:A variant of RASCI developed by three Whitehall theorists (Kane, Jackson, Gilbert). This scheme is adapted for use in matrix management environments, and differs only from RASCI in having an additional role of ''Driver'' and a narrower definition of ''Support'':

:; ''Driver''
:: An individual or party that assists those who are ''responsible'' for delivering a task by both producing supporting collateral and setting timescales for delivery in line with the overarching aim of the individual or party who is ''accountable'' for the overall accomplishment of the objective. The distinction between ''driver'' and ''support'' lies in that the former reinforces and clarifies the parameters of the task on behalf of those who are ''accountable'', while the latter refers to those who help those who are ''responsible'' in reaching a given goal.

=== PDQA ===
: A version developed at U Tokyo and MIT for model-based project management.  The PDQA set of roles corresponds to demand for capabilities of teams. Roles include those for work on scope, handling of dependencies as coordination, and exception handling through error detection and decisions across a project organization.  PDQA is used in agent-based modeling to simulate the supply of these capabilities by teams in projects.<ref>{{cite book |last1=Moser |first1=B. R. |last2=Wood |first2=R. T. |title=Concurrent Engineering in the 21st Century |chapter=Design of Complex Programs as Sociotechnical Systems |date=2015 |pages=197–220 |publisher= Springer|doi=10.1007/978-3-319-13776-6_8 |isbn=978-3-319-13775-9 }}</ref>

:; ''Primary''
:: Provides skill-based effort within capacity to complete scope and also manages dependencies through coordination.

:; ''Decision''
:: Handles any decision, including scope acceptable and exception handling decisions leading to rework. (Does not generation nominal scope).

:; ''Quality''
:: Reviews scope as it progresses to detect poor quality and escalates to decision-maker as so. (Does not general nominal scope).

:; ''Assist''
:: Provides skill-based effort with the capacity to complete scope, in assistance to the primary. (Does not manage dependencies through coordination).

=== DCI ===
: A minimal set of decision-making categories used in organisation design or roles analysis.

:; ''Decision maker''
:: Individuals who make the decision and is accountable for its impact on the business.

:; ''Consulted''
:: Individuals accountable for providing guidance based on functional expertise and experience, highlighting issues and raising alternatives to support the Decision Maker.

:; ''Informed''
:: Impacted stakeholders are notified after the decision has been made and who will need to support the execution of the decision.

=== RASCEIO ===

To be used when working on governance, risk, compliance (GRC) and outsourcing matters: 
:; ''Responsible''
:
:; ''Accountable''
:
:; ''Support''
:
:; ''Consult''
:
:; ''Execute''
:: Third parties contracted to execute activities in accordance with a service level agreement
:; ''Inform''
:
:; ''Overview''
:: Key GRC roles, such as risk owner, policy owner - where accountability is devolved, but a role is needed to oversee whether accountabilities all fit together

=== LACTI ===
Lead, Accountable, Consult, Tasked, Informed