Enter Project Name Here

Enter Project Name Here

Enter Department Name Here

OE-PM RACI Workbook

Status: Published or Draft

Version: X.0 (Published) or 0.X (Draft)

Prepared by:

Date Created:
Date Last Revised:

OE-PM Artifact ID: G03.02 Internal Use Only Page 1 of 41

Project #: XXXXX (If applicable)
Enter Project Name Here

Enter Department Name Here

Guide to the RACI Workbook

Introduction
A key component to building an effective and efficient project team is the early establishment of expectations for
each member of the team. To that end, documents and processes that define roles and responsibilities are critical
project planning deliverables. This worksheet serves to define roles and deliverables, documents which individuals
will play which roles, and describes all the roles who will be involved in each task (doing the work, reviewing the
results, approving the deliverable, etc.).
What is RACI?
Different organizations may use different variations of the acronym; for projects at UC Davis, the standard version is
RACI. Each part of the acronym is described below:
Responsible The person who is assigned to do the work.
Accountable The person who makes the final decision and has ultimate ownership.
Consulted The person who must be consulted before a decision or action is taken.
Informed The person who must be informed that a decision or action has been taken.

RACI Matrix
Accountability: The Project Manager is responsible for reviewing roles and responsibilities with the project team.
The people assigned to each role must review their own assignments and indicate agreement with the role and the
associated responsibilities.
Timing: Roles and Responsibilities should be completed in Planning and updated during Execution: Design. They
typically remain fairly static unless new tasks/activities are added, or resources change.
Reference: Definitions for each role, and background information for each deliverable (activity or work product) are
available on separate tabs within the RACI Workbook.
Instructions:
• Use the UC Davis standard RACI template as a starting point. Values in the matrix should stay fairly static
and serve as a guide.
• Add, modify or eliminate roles and/or activities as appropriate to your project.
• For each role that your project will require, record at least one name in the Role Description tab, unless the
role has not yet been filled. There may be multiple people playing one role, and/or multiple roles assigned to
one person.
• If it is determined that the RACI needs customization for your project -
- On the first pass, assign one and only one A role for each deliverable.
- Assign “highest” level value for each role/task combination: typically the order would be R, A, C, I.
• Review the responsibilities assigned to each role with the person or group assigned to that role, and
obtain their agreement.
• Update the Roles & Responsibilities pages of the Project Management Plan, based on your RACI work, for
review during the project kickoff.
• Publish this workbook on the project site.

Role Description
• Lists all the key project management roles and corresponding responsibilities.
• Identifies who is responsible (R) and accountability (A) for each key work product.
• There is a column to add the actual resource that will fill each role.
• The list can be reduced to reflect only the roles that are key for your project. This list of key project roles will need
to be documented on the Project Management Plan (PMP) as well.

Deliverable Matrix
• Lists all the key artifacts with a description of each artifact.
• Identifies the owner of the artifact. This information does not change.
• Identifies whether the process or artifact is required for the various size projects (High, Medium, Low, Mini).
• Highlight those processes and artifacts that are applicable to your project.
• Deviations to the standards should be documented in the text box at the bottom of the sheet.
• This document does not require input from the user (other than highlighting the applicable processes and artifacts
and/or identifying any exceptions.

PM-COP Artifact ID: G03.02 Internal Use Only Page 2 of 41

SR: XXXXX (If applicable)
 I
C
R

Architect
Project Sponsor

Business Owner

Business Analyst

Product Manager
Technology Owner

OE-PM Artifact ID: G03.02

Overall Project Manager

Business Project Manager

Technical Project Manager
INFORMED
CONSULTED
Ultimate Owner,
RESPONSIBLE

ACCOUNTABLE

Person informed after

Person responsible for

Project Participants
action or decision taken
action or decision taken
Person consulted before
Accountable for final decision
completing the assigned deliverable

R
Project Proposal--Submission Form

I
I
I
A

C
C
C
R
Sizing Matrix
Initiation

I
I

C
C
C
C
R
Initiation Business Case

I
I
I
PM-COP RACI Matrix

C
C
C
C
R
Kickoff

I
I
I
I
I
I

A
R
C
SharePoint Site Set-up

I
I

C
C
C
C
R
C
Project Charter
I

C
C
C
C
C
R
C
Risk Management Workbook

I
I
I
A

C
C
R
SR/ITPL/DPR Project Initiation Requests
A

R
R

Communication Request Form

I
I
A

Business Brief (Marketing Project)

I
I
I

Internal Use Only

Marketing Brief (Marketing Projects)
I
I
I
A

C
C
C
C

Business Workflows/Process Model

A

C
C
R
C
C
C
C

Request for Information (RFI)

I
I
I
A

C
C
R
C

Business Requirements
Requirements Catalog (embedded in Req.
I
I
I
I
A

C
R

Workbook)
A

C
C
R
C
C
C
C

Request for Proposal (RFP)

I
I
I
I
I

R
C

EIS Security Questionnaire

Planning

I
I
I
I
I
I

TAC Review
I
I
I
I
I
A

R
C

Deliverables Matrix
I
I
I
I
I
A

C
R

Communication Plan
I

C
C

TCoE Test Requirements

I
C

TCoE Test Estimation

I
I

Marketing Plan
I
I

Corp & RBG Communication Plan

I

Training Needs Assessment

I

A
A

C
C
C
C
R
R

Project Schedule (thru Execution: Design)

I

C
C
C
C
C
R
C

Project Management Plan

 Technical Writer

Project Reviewer I I I I I I I I I I I I I I I

Test Manager I I I I C I I I I I I I I I R C C

Technical Analyst I I I I C I I I I I I I I C C

Engineer I I I I C I I I I I I I I C I

Test Lead R,A C C

User Acceptance Tester I I I I C I I I I I I I I I

Test Engineer I I I I C I I I I I I I C I

Business Process Analyst I I I I C R I I I I I I I C C

Subject Matter Expert I C I I C C C C C C C C I I I I C C

Project Management Office I I I I I

Project Steering Committee I I I I I I I I

Technical Architecture Committee I

Division Finance Officer C

Enterprise Information Security I

Communications I R

Training Partner I R

Legal

Compliance I I C
A
Marketing R R
R
Vendor C R

Financial Accounting/Controller C I

OE-PM Artifact ID: G03.02 Internal Use Only

 Internal Audit
R R
Contract Admin & Procurement
C C
Risk I C

Artifact Approvers (artifact approvers not limited to those who are highlighted )

OE-PM Artifact ID: G03.02 Internal Use Only

 I

C
C
C
R
C
Planning Bus. Case

I
A

R
Measurement Plan

I
I
I

A
Vendor Design Document (Vendor)

I
I
I
I
I
I

A
System Documentation (Vendor)

I
I
A

OE-PM Artifact ID: G03.02

IT Network & Systems Diagrams

I
I
I
I
I
I

R
IT Tech Specifications

I
I
I
I
I
I

R
IT Operational Guide

C
R
Business Continuity Plan

I
A

C
Policies and Procedures

I
I

R
Procure Hardware/Software

I
I
I
I
I
I

A
R
R
Vendor Contract

I
I
I
I
I

C
C
C
Vendor Statement of Work

I
I
I
I
I
A

C
C
R
NAC Risk Assessment

A
A

C
C
C
C
R
R
Project Schedule (through Completion)
Deliverables by Project Phase

I
I
I

R
Execution Bus. Case

A
A

R
Solution Build (Coding & Unit Testing)

I
I
I
I
I
I

A
A

R
Install Hardware/Software

I
I
I
A

C
C

Training Plan

I
I
I

C
C
C
R
C

Implementation Plan
Execution

I
C

TCoE Test Strategy & Plan

Internal Use Only

I
I

TCoE Test Automation Feasibility

TCoE Test Scenario & Test Case

I

C
C

Design(Test Scenario Details)

TCoE Test Scenario & Test Case
I

C
C

Design(Test Case Details)

I
I

TCoE Test Progress Report

I
I

TCoE Defect Report

I

A
A

TCoE Test Summary Report

I

R
C
R

Escalation Level Agreement

I
I
I
I
I
I
I
I
I

Project Test Status Report

I
I
I
I
I
I
I

Training Materials Finalized

A
R

I
I
I
I
I
I
I

A
R

User Training
I
I
I
I
I
I
I

Execute Communication Plan

I
I
I
I
I
I
I

Execute Marketing Plan

A

C
C
C
C
R

Project Closure Workbook

I

Measurement Plan Execution

A/R

I
I
I
I
I
A
A

Change Management Plan

M
 R I C

I I I I I I I I I C I

I I I I I I C I I A C I I A A A A I I I I C I

I I I I I I C I I I I I I I C I

I I I I I I C R I I I I I I C I

C R R A A R,A C R,A R C

I I I I I I I C I I R I I I I C I

I I I I I I I C I I C C R R C R C R I I I I C I

I I I I I I C I I I I I I I C I

C I I I C R I C C C I C C I R R I I C I

I I I I I I I

R R R

R R R R R R R C

OE-PM Artifact ID: G03.02 Internal Use Only

 R I

I C

OE-PM Artifact ID: G03.02 Internal Use Only

 A
A

C
C
C
C
C
R
Resource Plan

I
I
I
I

C
C
R
C
RACI Workbook

A
A

C
C
C
C
C
R
Issue Management

I
I
I
I
I
I
A

C
R
Financial Management

I
I
I
I
I
A
A

OE-PM Artifact ID: G03.02

Risk Management Plan
Toll Gate Workbook

I
I
I
I
I
I

A
A

R
Monitoring & Control

(Planning, Execution, Closure)

C
C
C
C
C
R
Control Log

I
I

A
A

C
C
C
C
R
Monthly Status Report

Internal Use Only

 I I I I I I I I

C I C I I I C C

I I C I I I I C

I I C I I I I C

I I C I I I I C

I I C I I I I C

I I C I I I I C

I I C I I I C C

I I I I I

I I C I I I I

OE-PM Artifact ID: G03.02 Internal Use Only

OE-PM Artifact ID: G03.02 Internal Use Only
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)

PM-COP Artifact ID: G03.02 Page 12 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Auditor Serves as an independent oversight over bank wide operations,
including project

Business Investigates and analyzes business problems and manages the - Request for Information (R)
Analyst discovery and documentation of business requirements - Request for Proposal (R)
- Investigates and analyzes business problems and manages the - Business Requirements (R)
discovery and documentation of requirements - Requirements Traceability Matrix (R)
- Facilitates communication between the business and technical teams - Functional Spec Workbook (R)
- Ensures traceability from requirements to technical design

Business Usually reports into the Project Sponsor. May delegate some approval - Submission Document (R)
Owner authority, especially to the Business Lead: - Business Case (A)
- Defines project scope, objectives and success criteria - Change Management Plan (A)
- Provides direction and high level business requirements - Resource Plan (A)
- Provides oversight of the integrity of the value proposition throughout - Issue and Risk Management (A)
the project lifecycle - Risk Management Plan (A)
- Provides oversight of project progress and direction through review - Toll Gates (A)
and approval of key work products - Monthly Status Report (A)
- Participates in project-level governance activities - Project Charter (A)
- Resolves escalated business issues - SR/ITPL/DPR Project Initiation Req. (A)
- Accountable for Business Case - Communication Request Form (A)
- Contract Management - Business Brief (A)
- Communicates the needs of the group they represent to the project - Business Workflows (A)
- RFI/RFP (A)
- Project Schedule (A)
- Project Management Plan (A)
- NAC Risk Assessment (R)

PM-COP Artifact ID: G03.02 Page 13 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Business - Deliverables Matrix (A)
Owner - - Project Kickoff (A)
continued - Functional Specs (A)
- Communication Plan (A)
- Training Plan (A)
- Business Case (A)
- Business Requirements (A)
- Business Continuity Plan (A/R)
- Policies and Procedures (A)
- Develop Test Strategy (A)
- UA Test Plan (A)
- Vendor Negotiations (R)
- Sign Vendor Contract (R)
- Escalation Level Agreement (R)
- Implementation Plan (A)
- UAT Signoff (A)
- Post Prod Checkout (A)
- Execute Communication Plan (A)
- Execute Marketing Plan (A)
- User Training (R)

Business Business Process Professional responsible for working with internal - Business Process Flows (R)
Process clients to identify and eliminate duplicate, inefficient and unreliable
Analyst processes in an effort to boost operational efficiency and performance
- Elicits and document existing workflows (Current State)
- Elicits new workflow requirements (Future State)
- Documents business requirements for future state and may include
leveraging technology
- Supports defect impact analysis and assessment
- Supports maintenance of a Business Process Library

PM-COP Artifact ID: G03.02 Page 14 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Business Reports to overall project manager for all assigned project deliverables
Project - Manages business activities of the project
Manager - Provides cost and schedule estimates for business deliverables
- Assigns and monitors the work of business personnel, providing
support and interpretation of instructions/objectives, and ensuring
completion of the business deliverables
- Negotiates with project team regarding business resource constraints
- Coordinates acceptance from business stakeholders for technology
design
- Manages business-specific risks and issues, from identification
through resolution.
- Participates in project level governance
- Supports overall project manager in monitoring and reporting project
health/status
Business Unit - Consults with the project team to ensure the product delivered by the
Compliance project team is within industry rules and regulations
Officer (BUCO) - Responsible for reviewing and approving key project deliverables, as
appropriate
Compliance - Consults with the project team to ensure the product delivered by the
project team is compliant with industry rules and regulations
- Responsible for reviewing and approving key documents, as
appropriate

PM-COP Artifact ID: G03.02 Page 15 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Contract - Process Purchase Requisitions - RFP/RFI's for larger initiatives (R)
Administration - Create Purchase Orders - Vendor Negotiations (R)
and - Administer Vendor Management
Procurement - Administer Vendor Risk Assessment
- Write Request for Proposals and Request for Information (RFP,RFI)

Contract Administration:
- Administer, review, and negotiate contracts; coordinate contract
review process with Legal, EIS, OSG Compliance, Insurance, etc.
- Review executed BOTW standard vendor contracts and SOWs
including Amendments, Addendum or Work Orders
- Centralized contract record retention
- Contract renewal/termination notifications
- Contract compliance & standardization

Engineer - Participates in design of technical solution, in accordance to technical - Solution Build (R)
standards
- Develops and Unit Tests software
Division
Finance Officer - Report quarterly financial data for project.
EIS - Perform Security Reviews of any new or significantly modified system - Information Security Review Findings
- Provide Information Security consultancy (R)
- Develop and/or consult on user access provisioning requirements
Architect - Leads the development of the project’s technical solution - IT Network and Systems Diagram (R)
- Coordinate with critical technical stakeholders to validate project’s - IT Tech Spec (R)
technical design - IT Operational Guide (R)
- Ensures adherence to technical standards across the project - TAC Approval (R)
- Identifies key integration points between domains - EIS Security Review (R)
- Maintains the architectural vision of the solution throughout the - Solution Build (R)
project life - Install Hardware/Software (R)
- Sets up environments - SIT Plan (R)
- Install Production Environment ®

PM-COP Artifact ID: G03.02 Page 16 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Learning and - Consults with project team on training requirements - End User Training (R)
Development - Develops end user training materials
- Delivers training

Legal - Consults with the project team to ensure the product delivered by the - Contract Reviews (R)
project team is within industry rules and regulations
- Responsible for reviewing and approving key project deliverables, as
appropriate
- Responsible for reviewing and approving contracts

PM-COP Artifact ID: G03.02 Page 17 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Overall Project Accountable for the overall execution, management and delivery of a - Business Case (if PM assigned) (R)
Manager project (scope, budget, and schedule). - Change Management Plan (R)
- Accountable for overall execution, management and delivery of a - Resource Plan (R)
project (scope, budget, and schedule) - Risk Management Workbook (R)
- Establishes and facilitates the project level governance team - Risk Management Plan (R)
- Provides leadership of project team - Toll Gate Workbook (R)
- Responsible for project artifacts - Project Charter (R)
- Plans and manages project activities - Project Management Plan (R)
- Manages project schedule and costs - Project Schedule (R)
- Tracks and reports project progress - Project Status Reports (R)
- Manages stakeholders - Project Controls (Risk, Issues, Change
- Manages and resolves issues and risks Requests, Action Items) (R)
- Communication Request Forms (R)
- Marketing Brief (A)
- SharePoint Set Up (R)
- SR/ITPL/DPR Project Initiation Request
(R)
- Deliverables Matrix (R)
- Communication Plan (R)
- Implementation Plan (R)
- Project Closure Workbook (R)
- Training Request Form (A)
- Implementation Communication Plan
(R)
- Request for testing services in the
project(R, A)
- Post Implementation Analysis(R, A)

PM-COP Artifact ID: G03.02 Page 18 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
PMO (Central Projects will be accountable to one or more PMOs, depending on - Portfolio Dashboards (R)
or Business funding and execution model
Unit) - Facilitates the portfolio planning process
- Facilitates the portfolio level governance process
- Produces reporting and analysis on portfolio of projects
- Facilitates resolution of escalated project issues and change requests
- Manages the project initiation process (front door, prioritization,
approvals)
- Creates and maintains project management processes
- Audits project management process quality

Project - Secures organizational support and funding for the project - Submission Document (A)
Sponsor - Defines strategic objective of the project - Financial Management (A)
- Participates in project level governance - Risk Management Workbook (A)
- Makes final, critical project decisions, when needed - Sign Vendor Contracts (A)
- Vendor Negotiation (A)
Product Generally members of Product ownership team, Service Team, etc., - Communication Request Forms (R)
Manager participating in all phases of the project. - Business Brief (Request) (R)
- Proposes new product or service features and updates - Execute Communication and Marketing
- Identifies business stakeholders, including representatives for each Plans (R)
stakeholder group
- Work with the Business Owner to document the project’s vision and
scope, using standard requirements work products
- Act as an SME for the business group

PM-COP Artifact ID: G03.02 Page 19 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Project Should include project executives: PS, BO, TO.
Steering - Represents executive stakeholder interest in the project
Committee - Provides strategic advice to Project Sponsor and Business Owner
regarding trade off decisions and issue resolution
- Acts as Change Control Board for project change requests
- Actively participates in regular assessment of overall project health
discussions and meetings to ensure:
- Project vision is on track
- Approval of Change Requests
- Impact to customer/employee experience
- On track with budget allocation
Project May also be the “resource manager” for the Overall PM, Business PM
Reviewer or Tech PM
- Ensures use of project management best practice, including
adherence to standard methodology
- Reviews key project work products for quality
- Provides perspective and direction on resolution of project issues
Test Manager Accountable for ensuring the Quality standards are being followed. - Test Strategy (R)
- Participates in the project level and technical governance - Test Plan (A)
- Acts as the second escalation point for all testing related issues - Test Cases/Scripts (A)
- Attends weekly meeting of projects to provide a QC perspective - Test Execution (A)
- Manages appropriate measurements and metrics for the project. - Defect Logs (A)
- Participates in sizing effort - Test Signoff (R)
- Accountable overall Test Plan, Test Cases and Test Evaluation - Post Prod Checkout ®
Summary - Provide initial estimation on resources,
- Coordinates obtaining Testing resources effort, schedule and cost for
testing(R, A)
- Test schedule aligned to project
schedule(R, A)
- Test Progress Report
- Test Sumary Report

PM-COP Artifact ID: G03.02 Page 20 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Test Lead Responsible for ensuring the Quality standards are being followed. - Test Plan(R)
- Participates in the project execution level activities - Requirement Ambiguity Report(R)
- Acts as the first escalation point for all testing related issues - Test Effort Estimation(R)
- Implements and manages appropriate measurements and metrics for - Business Scenarios(R)
the project. - Test Cases (A)
- Assigns tasks to Test Team members - Defect Report(A)
- Develops Test Plan, Test Cases and Test Evaluation Summary - Weekly Status Report(R)
- Coordinates the development of Testing scripts - Test Summary Report(R)
- Manages deliverables of the Test engineers - Metrics Dashboard(R)
- Tracks and reports on testing activities - Understanding of the project by test
- Prepares Test Plan team(R)
- Attends weekly project meetings to track activities - Defect Management Plan(R)
- Facilitates Testing meetings - Environment setup for testing(A)
- Test Data and Test script preparation
- Test Execution Results(R)
- Test Progress Report(R, A)
- Test Summary Report(R, A)

Test Engineer - Prepares and updates test cases document to cover various test - Test Execution (R)
types and test scenarios - Test Cases (R)
- Executes test scripts - Defect Logs (R)
- Publishes test execution results - Document Reviews ®
- Logs defects in the defect tracking tool - Test data and test scripts preparation®
- Updated Requirements Traceability
Matrix

PM-COP Artifact ID: G03.02 Page 21 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Stakeholder Any individual or group who has a stake in the outcome of the project: - Various depending on specific role
People or groups whose actions (support, resistance, etc.) can impact
the success of your projects; People or groups who may be impacted,
either positively or negatively, by the project.
- Reviews the project at a high level for impact on their group
- Communicates key information about the project to the group they
represent
- Exerts influence over the project and its deliverables
Subject Matter - Person who is expert in a particular area - Marketing Brief (R)
Expert (SME) - Contributes to specialized requirements - UAT Cases/Scripts (R)
- Reviews project solution in the context of their area of expertise - Policies and Procedures (R)
- May participate in UAT and/or Deployment - User Training (R)
- Writes test scripts
- Updates Policies and Procedures
- May deliver end user training (as appropriate)
Technical Serves as a domain-specific bridge liaison between the functional - Functional Specs (R)
Analyst requirements and the Developer.
- Supports identification of technical stakeholders
- Participates in discovery and documentation of technical requirements
- Ensures traceability from requirements to technical design
- Assists with development of Test Strategy and Test Plan
Technical - Provides technical advice during Execution - TAC Approval (R)
Architecture - Defines and maintains technology standards
Committee - Manages approval process for new technology introduced by a
business unit and project

PM-COP Artifact ID: G03.02 Page 22 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Technical Reports to overall project manager for all assigned project deliverables : - Vendor Design Docs (A)
Project - Manages IT services regarding the development and implementation - System Documentation (A)
Manager of the project - EIS Security Review (A)
- Coordinates departmental or cross-functional technical teams - Procure Hardware/Software (R)
- Ensures completion of the technical deliverables within the triple - Project Schedule (R)
constraints - Solution Build (A)
- Coordinates and aggregates project sizing efforts across IT - Escalation Level Agreement (R)
- Manages IT activities and tasks and updates project schedule
- Supports overall project manager in monitoring and reporting project
health and status
- Responsible for procuring hardware and software

Technical - Produces end-user support material such as user guides, help texts, - Policies and Procedures (R)
Writer etc.

PM-COP Artifact ID: G03.02 Page 23 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

RACI Role Descriptions
Role Name Description Key Work Products (A's and R's)
Technology Usually an officer in technology responsible for the majority of the - Change Management Plan (A)
Owner project’s technology work: - Resource Plan (A)
- Provides oversight of the overall quality of the technology deliverables - Issues and Risk Management (A)
- Ensures adherence to technical governance processes - Risk Management Plan (A)
- Resolves escalated technology issues, including technology resource - Monthly Status Report (A)
contention - Toll Gates (A)
- Leads the development activities from inception through transition, - Project Schedule (A)
including the development of prototype solutions - IT Network and System Diagrams (A)
- Coordinates the production and sign-off of technical artifacts - IT Tech Specs (A)
- Participates in design reviews to ensure proposal is technically - IT Operational Guide (A)
feasible - TAC Approval (A)
- Ensures the development of the code to specifications by scheduling - Procure Hardware/Software (A)
and holding code reviews & code inspections - Install Hardware/Software (A)
- Defines application deployment strategy - SIT Plan (A)
- Documents the technical operation’s guide - Install Production Environment (A)
- Ensures adequate SIT Testing

PM-COP Artifact ID: G03.02 Page 24 of 41

Internal Use Only
SR: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

Deliverables Matrix
Artifact/
Artifact Description Mini Small Medium Large
Process Owner
Initiation
Document completed by the Business Owner
Submission Document PM-COP X X X
that explains the proposal in some detail.
Documents the value proposition for the
project, including the valuation of expected
benefits vs. the cost of development. Serves
Business Case PM-COP X X
as the yardstick against which the project's
Benefits, Costs and Timeline are measured.
Serves as the basis for the Measurement Plan.
Matrix that helps the Project Manager or
Business Owner determine which size the
Sizing Matrix (in BC Workbook) project is going to be (Small, Medium, and PM-COP X X X X
Large projects), which in turn, determines
required artifacts and processes.
Planning
Defines the stakeholders' view of the expected
outcomes to be developed, specified in terms
of the stakeholders' key needs and features. It
contains an outline of the envisioned core
requirements, so it provides a contractual basis
Project Charter PM-COP X X X
for the more detailed technical requirements
(scope of the project). It communicates the
fundamental "why and what" for the project and
is a gauge against which all future decisions
should be validated.

OE PM Artifact ID: G03.02

Internal Use Only Page 25 of 41
Project #: XXXXX (If applicable)
 Enter Project Name Here
Enter Department Name Here
Artifact
Risk Management Workbook Management Workbook should be completed
SR/ITPL/DPR Project Initiation Required if IT or Fidelity data processing
Request
Communication Request Form
Business Brief (Marketing
Projects)
Marketing Brief (Marketing
Projects)
Business Workflows
Request for Information
OE PM Artifact ID: G03.02
Project #: XXXXX (If applicable)
Deliverables Matrix
Artifact/
Description Mini Small Medium Large
Process Owner
Recurring process of evaluating the project's
risks against a standardized set of risk
scenarios, which serves as a foundation for
more detailed risk identification and results in a
risk profile for the project. The Risk
PM-COP X X
during Inception, as soon as details of the
project are discovered, and updated by the end
of Execution: Design, as well as any time the
project experiences significant change in scope
and/or approach.
IT As Applicable
services are needed.
Used to describe the communication needs of a
Communications As Applicable
project.
Used to request marketing support for your
Marketing As Applicable
project.
Marketing responses to the Business Brief and
Marketing As Applicable
outlines their support of the effort.
Documentation of step-by-step activities
(including those of clients and reps) within a
Business As Applicable
specific business process, using a formal
business process notation.
Request for Information, to be supplied to
proposed vendors when performing a vendor
selection for a new service or application. For Procurement As Applicable
further information, refer to the Request for
Proposal Procedures Manual.
Internal Use Only Page 26 of 41
 Enter Project Name Here
Enter Department Name Here
Artifact
Detailed Project Schedule
(though Execution: Design)
Project Management Plan
Deliverable Matrix (Static
Document)
Request for Proposal
TAC Approval
EIS Security Review
Functional Specifications
Marketing Plan
Test Approach - In Pilot
OE PM Artifact ID: G03.02
Project #: XXXXX (If applicable)
Deliverables Matrix
Artifact/
Description Mini Small Medium Large
Process Owner
Detailed schedule of activities necessary to
complete the Execution: Design phase, PM-COP X X X
including timing, duration and resources.
Communicates what the project is and how it
will be managed, including summary of scope, PM-COP X X
roles, risks/issues, process and deliverables.
Matrix that identifies which project artifacts and
processes need to be followed for Small, PM-COP X X X X
Medium,
Request forandProposal,
Large projects.
to be supplied to
proposed vendors. For further information,
refer to the Request for Proposal Procedures Procurement As Applicable
Manual.
Review and approval by IT of the proposed
IT As Applicable
system architecture.
Enterprise Information Security (EIS)
Engineering Security Review. To be completed
EIS As Applicable
when performing a major upgrade of an
application or implementing a new application.
Detailed business requirements document.
The Business Analyst works closely with the
PM-COP X X
business partner to collect and document the
business requirements.
Document produced by Marketing that identifies
the marketing activities required to meet the Marketing As Applicable
needs of the effort.
Defines the approach for how the test effort will
be conducted, inclusive of both technology and
TCOE X
user acceptance test efforts. It includes overall
timing and resource requirements.
Internal Use Only Page 27 of 41
 Enter Project Name Here
Enter Department Name Here
Artifact
Test Plan - In Pilot
Communication Plan
Training Plan
Business Requirements
Measurement Plan
Execution
Vendor Design Docs
System Documentation
Test Case/Defect Workbook
OE PM Artifact ID: G03.02
Project #: XXXXX (If applicable)
Deliverables Matrix
Artifact/
Description Mini Small Medium Large
Process Owner
Defines the type of testing effort to be
conducted (test cases), specifying coordination
points between business testers and
technology support, and including test
environment and test data requirements. This TCOE X X X
plan describes the effort to demonstrate that
the technology team has delivered the system
to the business owner in accordance with the
requirements.
Document that describes the activities that will
occur to satisfy the communication needs of the Communications X X
project at implementation.
Document that describes the activities that will
occur to satisfy the training requirements of the Training As Applicable
effort.
Documentation of the requirements of business
users such as customers, employees, vendors,
etc. early in the development cycle to PM-COP X X
specifically design and develop the future
system, process, or product.
Document that describes how the business is
Business As Applicable
going to define success.
Documents received from the vendor that
Vendor As Applicable
collectively outlines the design of the system.
Misc. documents received from the vendor that
Vendor As Applicable
outline various aspects of the system.
Template to log all test cases needed to be
TCOE X X X
tested during the testing cycles.
Internal Use Only Page 28 of 41
 Enter Project Name Here

Enter Department Name Here

Deliverables Matrix
Artifact/
Artifact Description Mini Small Medium Large
Process Owner
Central repository for all diagrams in
IT System and Network Information Technology. New applications and
IT As Applicable
Diagrams changes to existing network environments (i.e.,
upgrades) must be documented.
Log that tracks all Issues, Risks, Change
Project Control Log Workbook COP-PM X X X X
Controls and Action Items.
Document is used for defining how the team will
IT Technical Specifications IT As Applicable
code for theistransformation.
Document provided for every release. It has
information such as specific database names,
required data elements, etc. It’s really a
IT Operational Guide summary of the various documents listed IT As Applicable
above. It is still TBD if release notes will be
included in this document or a separate
document.
Document that captures how the business unit
Business Continuity Plan Business As Applicable
will maintain business in the event of a disaster.
Effort to define or redefine policies associated
Policies and Procedures (new
with product or service being delivered by the Business As Applicable
or updated)
project.
Document that captures and defines the work
Vendor Statement of Work activities, deliverables and timeline a vendor will Procurement As Applicable
execute against.

OE PM Artifact ID: G03.02

Internal Use Only Page 29 of 41
Project #: XXXXX (If applicable)
 Enter Project Name Here

Enter Department Name Here

Deliverables Matrix
Artifact/
Artifact Description Mini Small Medium Large
Process Owner
Iterative schedule of activities necessary to
complete the entire project, including timing,
duration and resources. By the end of
Inception, the project schedule should be
detailed enough to estimate how the project will
Project Schedule COP-PM X X X
spend money in each quarter of the project's
lifecycle (if this information is not detailed
enough for a monthly breakdown, the quarterly
funds will be spread evenly across the 3
months of the quarter).
Systems Integration Test Plan document. To be
SIT Plan completed by IT Application/Development IT As Applicable
Support Team.
Used to identify activities associated with an
implementation to ensure adequate preparation
Implementation Plan COP-PM X X
has taken place and adequate contingencies
are in place.
Microsoft Project Schedule that identifies all
activities and tasks for the implementation. The
Implementation Schedule Implementation Schedule can be part of the COP-PM X X
Project Schedule or a separate schedule and is
left up to the discretion of the Project Manager.
Escalation Level Agreement Escalation Level Agreement (ELA). required
IT As Applicable
(ELA) depending on type of project.
Document that captures the agreement
between two parties, where one is the customer
Service Level Agreement (SLA) and one is the service provider. e.g. An SLA Business As Applicable
specifically between the business unit and the
Help Desk.
Closure

OE PM Artifact ID: G03.02

Internal Use Only Page 30 of 41
Project #: XXXXX (If applicable)
 Enter Project Name Here
Enter Department Name Here
Artifact
Closure Workbook
Monitoring and Control
Change Management Plan
(Static Document)
Resource Plan
RACI/Roles & Responsibilities the participation of various roles in the activities
Issue Management
Financial Management
OE PM Artifact ID: G03.02
Project #: XXXXX (If applicable)
Deliverables Matrix
Artifact/
Description Mini Small Medium Large
Process Owner
Ongoing process of identifying, analyzing and
communicating the successes and challenges
related to project execution, in an attempt to
continuously improve the process of project Closure
execution. Survey that results in a PM-COP Checklist X X
standardized, statistical measurement of project only
execution. PER results can be a useful basis
for a Lessons Learned discussion with the
project team.
Document that communicates the project
team's approach to identifying, analyzing,
approving and incorporating change to project
PM-COP X X
scope, time, cost or benefits. Includes effective
utilization of an escalation process, when
appropriate.
Resource sheet in Microsoft Project which
communicates resource requirements and the PM-COP X X X
individuals who will fill required roles.
Matrix that documents expectations regarding
PM-COP X X
necessary to successfully complete the project.
Ongoing process of identifying, documenting,
analyzing, monitoring and resolving issues PM-COP X X
impacting the project.
Ongoing process of managing the project
financials. Expectations vary depending on
phase. End of Execution:Design phase the
PM-COP X X
commitment is a +/- 10% range that is no
more than 10% greater or less than the total
number in the baseline.
Internal Use Only Page 31 of 41
 Enter Project Name Here

Enter Department Name Here

Deliverables Matrix
Artifact/
Artifact Description Mini Small Medium Large
Process Owner
Document that communicates the project
Risk Management Plan (Static team's approach to identifying, analyzing,
PM-COP X X
Document) monitoring and responding to risk that may
impact the project.
Review by the Business Owner and Technology
Owner (as appropriate) to evaluate the project
team's successful completion of the previous
Toll Gate Workbook PM-COP X X
phase objectives, their readiness to execute on
the next phase objectives, and the validity of
the value proposition of the project.
Provide a list of different type of risks with their
PM-COP Risk Management
impacts, mitigation actions and tracking PM-COP X X X X
Workbook
mechanism.
Test Guidelines (Static Provides guidelines for Test Authoring, Test
TCOE X X X
Document) - In Pilot Execution, and Test Defect Tracking.
Document that describes metrics that can be
Metrics Handbook (Static
used throughout the test process to capture TCOE X X X
Document) - In Pilot
progress and quality.
Test Status Report Template - Template to be used to report weekly test
TCOE X X
In Pilot status.
Project Status Report Standardized report of the project's health. PM-COP X X

Document Deviations: 1) If artifact is required, but not being used.

2) If artifact is not required, but is being used.
Explanation:

OE PM Artifact ID: G03.02

Internal Use Only Page 32 of 41
Project #: XXXXX (If applicable)
<Enter Project Name on Cover Sheet>

QA-TCoE RACI* Matrix (Project Activity Details are described in the QA Proce

QA

QA-TCoE Project Activities Test Manager

Phase 1: Test Initiation

1. Conduct Testing Activities Initiation R

2. Conduct the Kick off Meeting A

3. Perform review and analysis of requirements for testability A

4. Prepare the High Level Scope & Estimation A

5. Prepare the High Level Test Schedule A

Phase 2: Test Planning

1. Prepare the Detailed Test Estimation A

2. Develop the Test Strategy & Plan for each testing type A

3. Prepare the Defect Management Plan A

 4. Prepare the Test Plan/Schedule A

5. Plan Test Environment(s) A

Phase 3: Test Design & Preparation

1. Test Scenario Preparation & Review I

2. Test Scenario Defect Reporting, Tracking & Closure A

3. Requirement Traceability Matrix Completion A

4. Test Case Preparation & Review I

5. Test Environment Setup I

6. Test Data Setup I

7. PT / PE Requirements Definition A

8. Test Estimation Update A

Phase 4: Test Execution & Monitoring

1. Test Execution I

2. Defect Tracking A

3. Test Progress Reporting A

 4. Test Summary Reporting A

Phase 5: Test Closure & Reporting

1. Test Closure & Reporting A

2. Post Production Defect Analysis A

3. Post Implementation Review C

* - RACI

R
RESPONSIBLE
Person responsible for completing the assigned deliverable

A ACCOUNTABLE
Ultimate Owner, Accountable for final decision

C CONSULTED
Person consulted before action or decision taken

I INFORMED
Person informed after action or decision taken
cribed in the QA Process Manual)

QA-TCoE Project Participants

Business Dev
Project
Test Lead Tester System Technical
Manager
Analyst Lead

I A

R C C

R C C I

R C C C

R C C

R I I C

R I C I

R I I I
R C I C

R I I C

A R C C I

R I C C I

R C C C I

A R C C I

A R I I I

A R I I I

R C C C I

R C I I I

A R C I I

R R C I I

R C C I I
R C C I I

R C C C C

R C C C C

C C C C R
 Output Work Product

Request for testing services in the project

Understanding of project by test team

Test Requirements template

Test Effort Estimation template (initial estimation on

resourcing, effort, schedule and cost for testing)

Test Plan template (initial test schedule aligned to

project schedule)

Test Effort Estimation template(test estimates for

testing activities)

Test Strategy & Plan template

Defect Management Plan template

Detailed Test Plan template (test schedule aligned
to project schedule)

Plan for test environment setup and procurement of

hardware, software, network, and/or tools

Test Scenario & Test Case Design template, Test

Scenario Details tab

Test Scenario & Test Case Design template, Test

Summary Details tab

Test Requirements template update

Test Scenario & Test Case Design template, Test

Case Details tab

Environment setup for testing

Test Data Management Process Workflow

Test Scenario & Test Case Design template, Test

Scenario Details tab

Test Effort Estimation template (update)

Test Execution results

Test Progress Report template

Test Progress Report template

Test Summary Report template

Lessons Learned, Final Test Progress and

Summary Reports

Post production defect analysis

Post Implementation analysis