One-line User Stories

by Mar 23, 2023

One-line user stories, like As a User I want to push a button So that it is pushed”

I cringe when this is the only statement in a user story. Why? Because someone once told them User Stories needs to be short and concise.

This doesn’t mean it needs to be a one liner.

To make a User Story better, add on the following sections:

✅ A background story, describe the current situation. Describe issues in the current situation: Why is it hurting us?

✅ Describe the persona, the type or role of the user (or link to it)

✅ Describe the desired new situation and how it would help and who it would help. Describe the benefit or value. Also try to describe the cost when not executing this User Story.

✅ Add acceptance criteria. What means “done” for this User Story.

Adding these sections will make your User Stories so much better and easier to implement.

Remy van Duijkeren

Remy van Duijkeren

Power Platform Advisor

Microsoft Power Platform Advisor with over 25 years of experience in IT with a focus on (marketing) automation and integration.

Helping organizations with scaling their business by automating processes on the Power Platform (Dynamics 365).

Expert in Power Platform, Dynamics 365 (Marketing & Sales) and Azure Integration Services. Giving advice and strategy consultancy.

Services:
– Strategy and tactics advise
– Automating and integrating

Subscribe to
The Daily Friction

A daily newsletter on automation and eliminating friction

Related Content

Backlog: The Black Hole of ideas

Backlog: The Black Hole of ideas Is your backlog turning into an ever-expanding universe of forgotten dreams? We all know that mix—a jumble of big ideas and tiny tasks waiting for their day in the sun. Some items linger for years. Why do backlogs grow? Because we...

read more

The Trade-off Between Budgets and Quality ⚖️

The Trade-off Between Budgets and Quality ⚖️ In my previous post, I talked about shifting from Estimates to Budgets for feature development 💡. Let's dive deeper. Using a Budget instead of an Estimate introduces a trade-off: Scope and Quality adjust to fit the time...

read more

Budgets instead of Estimates

Budgets instead of Estimates Estimating a feature is difficult and is often a guess (or even a lie). An Estimate is for a fixed scope. So, you need to think deeply how to implement the feature, before giving an Estimate. The business can then use the Estimate to...

read more