13.2 Stakeholder and User Needs

Stakeholder and User Needs is the underlying set of problems, goals, and expectations held by the people who fund, influence, or directly use a product, forming the essential foundation from which agile requirements are derived. Distinguishing genuine needs from the specific solutions stakeholders may initially propose is central to effective requirements work, since a stated request often represents one possible way of addressing a deeper need rather than the need itself, and requirements grounded in the underlying need tend to produce more durable, valuable outcomes than those that simply implement an initial suggestion literally.

Distinguishing Needs from Requests

Needs as the Underlying Problem

A need reflects the fundamental problem or goal a stakeholder or user is trying to address, existing independently of any particular solution, and understanding it clearly allows a team to evaluate multiple possible ways of addressing it rather than being locked into the first idea proposed.

Requests as Proposed Solutions

Stakeholders often express their needs in the form of a specific requested feature or capability, which represents their best guess at a solution but may not be the optimal — or even a correct — way to satisfy the actual underlying need.

Categories of Needs

Functional Needs

Functional needs describe what a product or system must actually do to accomplish a practical task, forming the core basis for most feature-oriented requirements.

Experiential and Usability Needs

Beyond pure function, users often have needs related to how a product feels to use, including ease of use, efficiency, and satisfaction, which can significantly affect adoption even when functional requirements are fully met.

Business and Organizational Needs

Stakeholders funding or sponsoring a project often hold needs distinct from those of end users, such as cost control, competitive positioning, or regulatory compliance, which must be understood and balanced alongside user-facing needs.

Constraints Framed as Needs

Some expressed needs are actually constraints, such as compatibility with existing systems or adherence to specific standards, and recognizing these as boundary conditions rather than functional requirements helps clarify what genuine flexibility exists in addressing the underlying problem.

Uncovering Genuine Needs

Asking Why

Persistently exploring the motivation behind a stated request, often through repeated questioning of why a particular capability matters, helps surface the underlying need a proposed solution is meant to address, revealing options the original request did not consider.

Observing Behavior

Direct observation of how stakeholders and users currently address the problem in question often reveals needs more accurately than self-reported description, since people do not always accurately recall or articulate their own behavior and motivations.

Reconciling Conflicting Needs

Different stakeholders and user groups often hold needs that conflict with one another, and effective requirements work involves recognizing these conflicts explicitly and making deliberate, transparent trade-offs rather than allowing unspoken tension to produce an incoherent solution.

Translating Needs into Requirements

Framing Requirements Around Value

Expressing requirements in terms of the value they deliver in satisfying an underlying need, rather than purely in terms of technical specification, keeps the connection between requirements and genuine stakeholder or user benefit visible throughout the delivery process.

Validating That Needs Are Met

Because a delivered feature can satisfy a literal request while failing to address the actual underlying need, validation should assess whether the delivered increment genuinely resolves the problem the stakeholder or user originally faced, not merely whether it matches an initial specification.

Needs as a Foundation for Prioritization

Weighing Relative Significance

Understanding the depth and breadth of a given need — how many people it affects and how significantly it impacts their goals — provides essential input for prioritizing backlog items relative to one another.

Revisiting Needs Over Time

As markets, technology, and organizational context evolve, previously significant needs may diminish in importance while new needs emerge, requiring ongoing attention to whether a product's requirements remain grounded in genuinely current stakeholder and user needs.

Stakeholder and User Needs provides the essential foundation beneath every agile requirement, ensuring that a team's delivered work addresses genuine underlying problems rather than merely implementing initial requests that may only partially or imperfectly reflect what stakeholders and users actually require.