The stakeholder analysis
Download
1 / 20

The Stakeholder Analysis - PowerPoint PPT Presentation


  • 117 Views
  • Uploaded on

The Stakeholder Analysis. Who cares about this system I’m developing and how do I make sure they: Support the work, don’t cut the funding, don’t demand the funding be cut, don’t take the funding, and want to hire us again?. Stakeholder Analysis. Who When Why How. Who?.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' The Stakeholder Analysis' - eydie


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
The stakeholder analysis

The Stakeholder Analysis

Who cares about this system I’m developing and how do I make sure they:

Support the work,

don’t cut the funding,

don’t demand the funding be cut,

don’t take the funding, and

want to hire us again?


Stakeholder analysis
Stakeholder Analysis

  • Who

  • When

  • Why

  • How


Who?

  • Who’s paying you?

  • Who do they answer to?

  • Who are their critics and competitors?

  • Who wants the opportunity they’re giving you?

  • Who will use what you’re designing?

  • Who will be affected by what you design?

  • Who will be affected by the physical, cultural, procedural, etc. by-products of what you design?


Who?

  • Client/Program manager

  • Client’s funding source

  • Down-stream benefactors

  • Competitors

  • Users

  • Users’ co-workers, neighbors, technology vendors, etc.

  • Your company/organization

  • Your partners

  • Your team/teammates


When?

All the time.

  • Myth: System development is a linear process—e.g., analyzedesignbuildtest.


Why?

  • Client/Program manager

  • Client’s funding source

  • Down-stream benefactors

  • Competitors

  • Users

  • Users’ co-workers, neighbors, technology vendors, etc.

  • Your company/organization

  • Your partners

  • Your team/teammates

Fosters Systems Thinking!

Allows you to adapt your design to the broader environment.


Why what happens if it s not done
Why? What happens if it’s not done?

  • Assuming the Customer Knows What He/She Wants

  • Assuming the Client Doesn’t Know

    • “Client doesn’t know what he/she wants”

    • “Users don’t know what they want”

  • User Rebellion

  • Team Rebellion

  • The Sergeant’s Second Job

  • The New PM

  • Power Struggles and Agenda

  • Six Months of Doing the Wrong Thing


A balancing act
A Balancing Act

Users

  • Your company’s:

  • Profit

  • Legal Dept.

  • Growth priorities

  • Partner organizations

  • Regulators

  • Competitors

  • Your team/teammates

  • Down-stream users

  • Client


How?

  • Client/Program manager

  • Client’s funding source

  • Down-stream benefactors

  • Competitors

  • Users

  • Users’ co-workers, neighbors, technology vendors, etc.

  • Your company/organization

  • Your partners

  • Your team/teammates

Communi-cation,

Feedback& Adaptation

Risk

Management



How?

  • Semi-structured interviews to identify stakeholders and find out their general interests:

    • Client’s funding source

    • Down-stream benefactors

    • Competitors

    • Users

    • Users’ co-workers, neighbors, technology vendors, etc.

    • Your company/organization

    • Your partners

    • Your team/teammates


How?

  • Frequent check-ins to obtain feedback

  • “What-if” sessions with stakeholders

    • What if we don’t add X to the system? How will that affect you?

      • Best if grounded in specific scenarios (Scenario-based what-iffing)

  • Human factors methods for obtaining effective feedback from users

    • Verbal protocol analysis

    • Observation

    • Behavioral checklists, etc.


The stakeholder analysis is not a static thing it s never complete
The stakeholder analysis is not a static thing. It’s never complete.

  • Stakeholders may not be able to tell you they like or don’t like your product until you’re halfway done.

  • Complex information is not easily verbalized.

    • Complex political landscape

    • Complex technological needs

    • Complex culture


How? complete.

  • Develop a plan for detecting and responding to changes in stakeholder position and influence.



How? complete.

There is no one right way. Look around for ideas.

Your Thesis Advisors

Prez

Chair

SMEs

You Guys

FAA Comp.

http://www.projectshrink.com/stakeholder-adventure-maps-drawing-smileys-and-walls-3560.html


Eyeport stakeholder interest areas
EyePort complete.: Stakeholder Interest Areas


Eyeport stakeholder participation across lifecycle stages
EyePort complete.: Stakeholder Participation Across Lifecycle Stages


Your turn blackboard
Your complete.Turn: Blackboard

Stakeholders:

How to proceed with each?


ad