How to write Better User Stories

User Stories

In Scrum, features are usually written in the form of User Stories.

There are 3 parts (the 3 Cs) to a User Story. Card, Conversations and Confirmations. However what's commonly missing are the set of Confirmations that should be appended to each user story.

The Card

User stories are typically written in this format:

As a [Administrator], I want the system to [allow me to administer user access], so that [I can approve and reject user access requests].

The Confirmations

Confirmations are written during the discussions between the Product Owner and the Dev Team. They are akin to a set of Acceptance Criteria.

Using the example above, we can create the following confirmations.

1. Email notification to be sent out to users holding onto the "Administrator" role whenever a new user request is submitted.
2. Only users holding onto the "Administrator" role can approve and reject users.
3. Email notification to be sent out to approved and rejected users.

With the set of confirmations, developers are now clearer on the requirements. There will be less ambiguity and we get closer to our ideal product at a faster rate.

Try it today🥳