27
IDENTIFYING & ANALYSING

Analyzing stakeholders sahil chawla

Embed Size (px)

Citation preview

Page 1: Analyzing stakeholders sahil chawla

IDENTIFYING & ANALYSING

Page 2: Analyzing stakeholders sahil chawla

DEMO OBJECTIVE1.Introductions 2.Stakeholder Management Overview 3.Identify Stakeholders 4.Analyze Stakeholders 5.Prioritize Stakeholders 6.Engage Stakeholders 7.Communicating

Page 3: Analyzing stakeholders sahil chawla

WHO IS A STAKEHOLDER???

• Generally speaking, they are those who have the interest and influence to impact your product, program, team, or project.

Page 4: Analyzing stakeholders sahil chawla

WHO IS A STAKEHOLDER???

• In terms of Business: Stakeholders are the

people or groups with an interest in success or failure of an organization.

Supplier

Investor

Rivals

Govt.

Manager

Owners

Customer

Employee

Business

Page 5: Analyzing stakeholders sahil chawla

WHO IS A STAKEHOLDER???

• Stakeholders can affect or be affected by the objectives and polices of an organization.

Page 6: Analyzing stakeholders sahil chawla

WHO IS A STAKEHOLDER???

• They contribute, either voluntarily or involuntarily, to a company’s wealth-creating capacity and activities.

• Therefore are its potential beneficiaries and / or risk bearers.

Page 7: Analyzing stakeholders sahil chawla

STAKEHOLDER CLASSIFICATION

Primary(Internal)

• Primary (Internal):People or groups seen by the business to be vital to the organization's success or failure.

• Secondary (External): People or group who feel involved in the organization's success or failure, whether or not the management agree.

Secondary(Secondary)

Partners Suppliers

Customer

Competitors

Shareholders

Management

Employees

Page 8: Analyzing stakeholders sahil chawla

STAKEHOLDER MANAGEMENT

Other PMs

Contractors

Teams

Functional Managers

Finance

Executives

Sponsor

PM

Stakeholders

ClientsClient employeesInternal employeesInterested orgGovernmentsMedia

1. STAKEHOLDER MANAGEMENT especially from a project manager’s(PM) point of view is instrumental to the success of every project in an organization.

2. Simply speaking it involves engaging right people in the right way in the project.

$

Page 9: Analyzing stakeholders sahil chawla

STAKEHOLDER MANAGEMENT

Other PMs

Contractors

Teams

Functional Managers

Finance

Executives

Sponsor

PM

Stakeholders

ClientsClient employeesInternal employeesInterested orgGovernmentsMedia

1. STAKEHOLDER MANAGEMENT especially from a project manager’s(PM) point of view is instrumental to the success of every project in an organization.

2. Simply speaking it involves engaging right people in the right way in the project.

3. It is the SUCCESS MANTRA of Successful people and also enables them to win support from others.

$

Page 10: Analyzing stakeholders sahil chawla

STAKEHOLDER MANAGEMENT PROCESS

Identify Stakeholders

Analyze Stakeholders

Communicate Often!

Engage Stakeholders

PrioritizeStakeholders

Stakeholders

Page 11: Analyzing stakeholders sahil chawla

STAKEHOLDER MANAGEMENT PROCESS

Identify Stakeholders

Analyze Stakeholders

Communicate Often!

Engage Stakeholders

PrioritizeStakeholders

Stakeholders

Identify Stakeholders

Page 12: Analyzing stakeholders sahil chawla

IDENTIFY STAKEHOLDERS• Our ultimate motive in this

entire activity is to decide who our KEY STAKEHOLDERS are.

• So, you need to drill down.• Begin by setting stakeholders

against a backdrop of interest and influence.

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

Page 13: Analyzing stakeholders sahil chawla

IDENTIFY STAKEHOLDERS• This helps in

determining which groups and individuals require the most effort.

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

MONITOR

KEEP HAPPY

KEEP INFORMED

ACTIVELY ENGAGE

Page 14: Analyzing stakeholders sahil chawla

STAKEHOLDER MANAGEMENT PROCESS

Identify Stakeholders

Analyze Stakeholders

Communicate Often!

Engage Stakeholders

PrioritizeStakeholders

Stakeholders

Analyze Stakeholders

Page 15: Analyzing stakeholders sahil chawla

PURPOSE OF STAKEHOLDER ANALYSIS

• To access which individuals or groups are likely to support, resist, remain neutral during project implementation.

• Defining Stakeholder’s strategic importance i.e their power to influence the fate of a project.

• Clarifying stakeholder’s goals/ needs.• Developing stakeholder strategy.

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

MONITOR

KEEP HAPPY

KEEP INFORMED

ACTIVELY ENGAGE

Page 16: Analyzing stakeholders sahil chawla

Let’s Get Started

Page 17: Analyzing stakeholders sahil chawla

LOW INFLUENCELOW INTEREST

• They aren’t significantly involved.

• May not even be aware of your project.

• Just monitor them and be aware as to who they are.

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

MONITOR

Page 18: Analyzing stakeholders sahil chawla

HIGH INFLUENCE LOW INTEREST

• Those with significantly decision-making authority .

• Lacks the availability or interest to be actively engaged.

• Do whatever is needed to keep them satisfied.

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

KEEP HAPPY

Page 19: Analyzing stakeholders sahil chawla

LOW INFLUENCEHIGH INTEREST

• May be impacted by the project but have little influence

• May want more of your time than you can give • Find efficient ways to communicate and keep

them informed via • –Email updates • –Presentations • –Publicity campaigns

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

KEEP INFORMED

Page 20: Analyzing stakeholders sahil chawla

HIGH INFLUENCE HIGH INTEREST • Business owners and others with

significant decision-making authority. • Typically easy to identify. • Can kill, sustain, or nurture the project • They’re typically easy to engage actively. • Set up consistent touch points.

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

ACTIVELY ENGAGE

Page 21: Analyzing stakeholders sahil chawla

ANALYZING KEY STAKEHOLDERS

• Now try and map these stakeholders against their actual roles .

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

MONITOR

KEEP HAPPY

KEEP INFORMED

ACTIVELY ENGAGE

Page 22: Analyzing stakeholders sahil chawla

HERE ARE SOME KEY STAKEHOLDERS

Business Owner • Business owners must participate in Release Planning and the PSI Inspect

to review planned vs. actual progress.

• Major Stakeholder • Major stakeholders should also be involved in the System Sprint Demos .

• Minor Stakeholder • Minor Stakeholders are engaged as required in order to keep them

informed.

Subject Matter Expert Are engaged as required for input.

LEVEL OF INTEREST

LEVE

L O

F IN

FLU

ENC

E

Page 23: Analyzing stakeholders sahil chawla

STAKEHOLDER MANAGEMENT PROCESS

Identify Stakeholders

Analyze Stakeholders

Communicate Often!

Engage Stakeholders

PrioritizeStakeholders

Stakeholders

PrioritizeStakeholders

Page 24: Analyzing stakeholders sahil chawla

Priority Level

Attitude Influence Interest

Supportive Decision Maker YesHigh

Indifferent Policy Maker

Opposed Access Gatekeeper

Yes

No

Medium

Low

PRIORITIZING STAKEHOLDERS

• Prioritize your stakeholders on the basis of parameters like Attitude, Influence,Interest.

Page 25: Analyzing stakeholders sahil chawla

STAKEHOLDER MANAGEMENT PROCESS

Identify Stakeholders

Analyze Stakeholders

Communicate Often!

Engage Stakeholders

PrioritizeStakeholders

Stakeholders

Engage Stakeholders

Page 26: Analyzing stakeholders sahil chawla

ENGAGE STAKEHOLDERS• Develop key messages to set the stage and tell the story. - Show benefits to the stakeholders on how you are increasing profitability.

- Ensure clarity, honestyand transparency.

• Plan activities andalign your engagementtimeline with theproject timeline.

• Ask specific questions.

• Collect feedback.

Page 27: Analyzing stakeholders sahil chawla

Stakeholders not only have rights but responsibilities as well

Rights

• Have an engaged team • Be informed of the team’s

progress • Receive good-faith estimates • Be educated on technical

and architectural factors that impact estimates

• Receive training and coaching

Responsibilities

• Remain engaged from the definition to the completion of the project

• Provide ongoing feedback and support

• Define and clarify requirements • Collaborate with the Product

Owner • Contribute to the growth of the

environment