Okuzeka
Software Engineering vocabulary · Agile and Team Workflow

Stakeholder

Meaning in software engineering, with examples

/ˈsteɪkhoʊldər/nounCommon term

In software engineering, stakeholder means: Any person or group that is affected by a project or has a say in it, such as customers, managers, other teams, the legal team or support.

In Turkish: paydaş, ilgili taraf

How it is used

Developers keep stakeholders informed, get buy-in from stakeholders and present to them in a sprint review. 'Key stakeholders' are the ones whose approval matters most. It is a business word, so it appears often in emails and planning documents.

Example sentences

  1. We demoed the new search to stakeholders from sales and support on Friday.

  2. Before changing the API, check with every stakeholder who depends on it.

Common collocations

  • key stakeholders
  • keep stakeholders informed
  • stakeholder buy-in
  • stakeholder meeting
  • requirementSomething the software must do, or a condition it must meet, as agreed with users, clients or the product team.
  • prioritizeTo decide which tasks are most important or urgent and should be done first, especially when there is not enough time for everything.
  • user storyA short description of a feature from the user's point of view, often written as 'As a [type of user], I want [goal] so that [reason]'.
  • backlogThe ordered list of work a team has not started yet, such as features, bugs and improvements, with the most important items at the top.

This word in other fields

The same English word can have a different meaning in another field:

More terms: Agile and Team Workflow

Practise with graded reading

Reading at the right level is the fastest way to make new words stick. Pick free English books by level: