Process Automation

Power and Influence matrix:

Project Manager: Mr. Uday

Prepared By: Sneha

Influence
• Business Analyst
• Executive
Leadership Team • Project Manager
(Client) • Project Lead (Technical)

r
we
Po

• Developer
• Tester

Stakeholder Engagement Strategies:

Stakeholder Engagement Information needs Frequency Medium

Level
Executive Keep  Scope of Daily  Email
Leadership Satisfied the project  Virtual Meeting
Team (Client)  System
Architecture and
Design
 Problems
and proposed
solutions
 Project
progress and
updates
 Cost
impact due to

1 of 5
Process Automation

change request
Project Manage  Detailed Daily  Written Reports
Manager Closely cost  Meetings including
 Schedule project team
 Project meetings
Status
 Problems
 Proposed
Actions
Project Lead Manage  Technical Daily  Written Reports
(Technical) Closely Leads  Meeting with
 Layout project team and
Designs and the technical team
formats
Business Manage  Requireme Daily  Written Reports,
Analyst Closely nts of the Documents,
project. meeting with
 Project stakeholders
progress and
updates

RACI Matrix:
Project Manager: Mr. Uday

Prepared by: Sneha

This matrix describes the level of participation and authority for project stakeholders on
major project activities.
R Execution responsibility. Stakeholder responsible for getting the work done. Not necessarily a
decision maker but drives the group to make decisions in a timely manner.

2 of 5
Process Automation

A Approval authority. Final approval on accepting the outcome of this activity. Makes decisions.

C Must be consulted. As work is performed this stakeholder contributes information. Does not make
decisions, but is asked for input prior to decisions.

I Informed after a decision is made. Wants to stay updated on progress of this activity.

Mr. Rahman CEO

Project ManagerMr. Uday

Project Lead and TeamMr. Akhil

Business AnalystMs. Sneha
Raza CTOMr. Faisal
Activity

INITIATION PHASE

Scoping questionnaire document to procure more R/I A R

information about their business.

Analysis based on the questionnaire and other I R R

documents.

Scheduling requirement gathering workshop to define A/I I I R

project objectives, scope and understand the business in
detail.

Organizing remote workshop to review business R/A I/A R/I R

processes, use-cases, integration requirements and
migration needs.

Business case development A/I I C R

PLANNING PHASE

Detailed project documentation (BRD)/scope document A/I A/I C R

that typically includes an overview of business,
stakeholders, requirements, process flow diagrams, pain
points in the process.

Solution architecture of the solution A/I A/I R/C R

3 of 5
Process Automation

Invitation to client for solution presentation and

discussion. I I I R I

Solution discussion meeting A/C A/I R I I

Scope documentation - sign-off A A

Schedule planning for the project - plan the project A/I I R C/I I
Phases, timelines, and deliverables in each phase
according to the scope

Communication Plan - To ensure the project is on track A/I I I R I

by sharing status updates/review meetings and addressing
any issues or project risks/blockers.

Configuration and Development phase

System configuration sessions to ensure alignment of C/I R R

functional/technical requirements according to the scope

Bi-Weekly defined sprints I R/C I

Integration Development C R

Change management control and analysis A/I I R I R

Testing Phase

Testing by project team C I R

User acceptance testing A/I A/I R I R

Training Phase

Create Manuals and Release Notes C R

4 of 5
Process Automation

Planning Training Sessions A/I I R I

Training A R I R

This matrix describes the level of participation and authority for project stakeholders on
major project activities.
R Execution responsibility. Stakeholder responsible for getting the work done. Not necessarily a
decision maker but drives the group to make decisions in a timely manner.

A Approval authority. Final approval on accepting the outcome of this activity. Makes decisions.

C Must be consulted. As work is performed this stakeholder contributes information. Does not make
decisions, but is asked for input prior to decisions.

I Informed after a decision is made. Wants to stay updated on progress of this activity.

5 of 5