Customer and User Context

Customer and User Context is the surrounding set of conditions, characteristics, and circumstances that describe the people an agile project is ultimately building for, providing the situational backdrop against which stakeholder engagement, user stories, and value definitions are all interpreted. Where earlier foundations define concepts such as customer, end user, and user persona in the abstract, customer and user context addresses the specific, concrete circumstances of a given project's actual audience: who they are, what environment they operate in, and what constraints and expectations shape how they will actually experience a delivered product.

Understanding this context matters because the same feature or capability can mean something entirely different depending on who is using it and under what circumstances. A team that treats its customers and users as an undifferentiated, generic audience risks building work that technically satisfies a written requirement while missing the actual situational needs that requirement was meant to capture.

Who the Audience Actually Is

Audience Composition

Audience composition describes the specific mix of customer and user types a project serves, recognizing that a single product frequently serves more than one distinct group with different needs, technical familiarity, and expectations.

Relationship to the Product

The relationship a customer or user holds to a product varies meaningfully, from someone making a purchasing decision on behalf of others, to someone interacting with the product directly and repeatedly, to someone affected by the product's output without directly operating it themselves.

The Situation Users Operate Within

Environmental Circumstances

Environmental circumstances describe the physical, technical, or organizational setting a customer or user is situated in while interacting with a product, such as the equipment available to them, the pace at which they must work, or the broader system their activity fits into.

Constraints on Use

Constraints on use describe the specific limitations affecting how a customer or user can actually engage with a product, including time pressure, restricted access, or limits on the technical skill they can be expected to bring to the interaction.

What This Context Shapes

Expectations Shaped by Context

Expectations shaped by context are the standards a customer or user implicitly holds for a product based on their situation, such as expecting a certain level of responsiveness in a time-sensitive environment or a certain simplicity in a setting where extended training is not realistic.

Context Sensitivity in Requirements

Context sensitivity in requirements is the practice of ensuring that stated needs and acceptance criteria are interpreted in light of the actual customer and user context they arose from, preventing a technically correct implementation from still failing to serve the situation it was meant to address.