Agile Modeling Logo

Stakeholders of Software Teams

Let's start with some definitions:

A stakeholder could be:

From this definition you can see that business people, such as direct users and their managers, aren't the only stakeholders of an initiative. As you know there is a wide range of people potentially affected by a new solution, therefore to succeed you must understand and then synthesize their requirements into a cohesive vision. This is one of the things that makes software development hard: each stakeholder will have their own requirements, their own vision, and their own priorities. But it also makes software development fun.

Agile Modeling (AM)'s definition of project stakeholder and developer may be different than yours, or perhaps you prefer different terms. For example, XP discusses the concepts of customer and programmer, not stakeholder and team member, and has slightly different definitions because they use the terms differently than AM does.


Categories of Stakeholder

AM distinguishes between four types of stakeholder:
  1. Business stakeholders. This includes end users, their managers, and the decision makers who pay for and oversee your initiative. Business stakeholders are also known as domain stakeholders.
  2. Supporting stakeholders. These are people who oversee, guide, or collaborate with the team to help them successfully produce their solution. This includes enterprise architects, database administrators, security experts, network experts, and toolsmiths to name a few.
  3. Downstream stakeholders. These are the people who operate your solution in production, who market and sell your solution to customers, who support your customers using your solution, and the people who evolve your solution (this may be the original team) after it has been deployed.
  4. The team. The team clearly has an important stake in what they do.

A Team and Their Stakeholders

For ease of discussion, AM talks in terms of the team and their stakeholders. Yes, as indicated above, the team is definitely a type of stakeholder. But, for ease of conversation, AM separates the two concepts.