Course contentsShow
← Software Engineering
Lesson 133 of 1,9334. Requirements EngineeringFree lesson

Stakeholder Identification and Analysis

Learn to identify all relevant stakeholders and analyze their interests, influence, and importance to the project.

Stakeholder Identification and Analysis

What You'll Learn

You'll learn how to find everyone who cares about your software project and understand what they need, how much power they have, and how important they are to your success.

Who Are Stakeholders?

A stakeholder is anyone affected by your software or who can affect its success. This includes obvious people like users and managers, but also less obvious ones like IT support staff, legal teams, or even competing teams whose systems interact with yours.

Think of it like planning a wedding: the couple are key stakeholders, but so are parents (who might pay), the venue (constraints), guests (users), and the caterer (vendor). Miss any group, and you might face surprises.

Why Identification Matters

Before you can gather good requirements, you need to know who to ask. Missing a stakeholder means missing requirements—like building a login system without consulting the security team, only to discover it violates company policy.

Analyzing Stakeholders

Once identified, analyze each stakeholder by:

  • Interest: How much do they care? (High/Low)
  • Influence: How much power do they have? (High/Low)
  • Impact: How does the project affect them?
  • Needs: What requirements will they contribute?

For example, your CEO has high influence but might have low day-to-day interest. Your end users have high interest but often low influence. Your project sponsor typically has both high interest and influence—making them critical.

This analysis helps you prioritize: spend more time with high-influence, high-interest stakeholders when gathering requirements (lesson 127 and beyond).

Key Takeaway: Successful requirements engineering starts with finding all stakeholders and understanding their power, interest, and needs—because the people you miss become the requirements you miss.