Ubiquitous Language and User Stories

User Stories follow specific characteristics that make them reusable. For instance, When defining User Stories is preferable to use a declarative style over the imperative one.

The imperative style is too concrete and specific, reducing flexibility and expression. Making them declarative, the language to describe them becomes abstract, making user stories experimental.

By approaching stories as survivable experiments, we can shift the focus from technical complexity to expected outcomes and learning.[¹]

Survivable experiments prevent small technical stories and stories that business sponsors don’t care about going live.

User Stories Template

Behavior change: This is the behavior the team wants to influence a user. User stories describe the higher-level behavior of a user.

Role: Which Role will the user play in the context of the Behavior change? Defining roles is essential to split and group functionality based on users.