liveBook · Manning

Stakeholder

As explained in Collaborative Software Design: How to facilitate domain modeling decisions

A stakeholder is a person or group affected by, interested in, or able to influence the software and its organizational outcomes.

A stakeholder is anyone whose knowledge, use, purchase, work, or organizational authority can influence the software and its outcomes. Collaborative modeling identifies four overlapping categories: domain experts, users, the development team, and customers. section 2.2.2

Use the categories as prompts rather than rigid labels:

  • Domain experts understand or experience the business problems; they may include executives, product owners, UX designers, or developers. section 2.2.2
  • Users operate the system, customers purchase the product or service, and the development team builds software to solve business problems. section 2.2.2
  • Invite nonrelevant stakeholders when possible: they may contribute different insights and expose assumptions held by the core group. section 2.2.2

BigScreen stakeholder analysis

A marketing researcher can be both user and domain expert; a developer can possess deep domain knowledge; executives can influence strategy and budget without using the system. Mapping these overlaps prevents customer, user, and expert from being treated as synonyms. section 2.2.2

How Collaborative Software Design: How to facilitate domain modeling decisions covers it

How deep it goes
Defines four categories, corrects role misconceptions, and maps overlapping memberships through stakeholder analysis.
Examples
Uses BigScreen roles, executive decision-makers, and an overlapping-category Venn diagram as concrete examples.
What you can do after
Apply stakeholder analysis to identify overlapping roles and include relevant and potentially overlooked perspectives.
How it connects
Connects domain experts, users, development teams, and customers through collaborative modeling.

Also explained in

Compare how 9 books explain stakeholder →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Collaborative Software Design: How to facilitate domain modeling decisions. The section links point to the parts of the book it draws on.