User Story Statements

by Mar 22, 2023Shorts

As a User I want to push a button So that it is pushed”

I cringe at these kind of user stories. This one is over the top, but I see user stories often looking like this.

This is the template:
As a [type of user/persona], I want [an action] so that [a benefit/a value]

So, a User is not specific enough. Is it the System Administrator or the receptionist? This is an enormous difference in knowledge of the user doing the action.

Push a button is just one implementation to perform an action. Don’t describe the implementation, but the action you want. Like ‘Delete a Contact’ or ‘Send Survey to a Contact’.

The last part of the User Stories is usually the most interesting part, but often neglected. It tells the “Why”. The benefit or value for the company, customer, or user.

Don’t neglect this part and try to write the real reason who is benefiting from this user story.

Remy van Duijkeren

Remy van Duijkeren

The Marketing Developer

I build automation and integrations that remove the annoying stuff—using Power Platform, Dynamics 365 & Azure.

Get My Thoughts on Automation & Development

Join my personal newsletter and get practical insights on building faster, integrating smarter, and removing friction in IT systems — especially on Power Platform and Dynamics 365.

Related

.NET 10: ZIP it. Smarter.

.NET 10: ZIP it. Smarter. Yes, you could already update entries inside ZIP files before... But now you can do it without rewriting the entire...

read more