Explore user requirements

Why

Get a detailed view of how users will be using your solution and what their requirements are.

How

Talk to your clients about their expectations and describe how the different users (or stakeholders) will interact with the system under development. It is highly recommended that you directly involve end users, rather than just the client.

Practice

Users and stakeholders often find it difficult to describe the expected behaviour of the system from scratch. Therefore, most companies take an iterative approach to defining user requirements (e.g. by updating the scenarios after each demo with stakeholders).

Ingredients

• The involvement of a group of stakeholders that includes people beyond the client.
• Tools to capture the scenarios described, like use cases and user stories.
• A focus on expected system behaviour, not its realisation.
• Use the stakeholders’ ‘language’ so they can review the described scenarios.

Phases

• Analysis

Trade-offs

Read more about the trade-offs: Inspiration or Data / Expertise or Fit / Overview or Certainty.