User Stories — One Story To Rule Them All

One User Story, Multiple Roles

When creating users stories, you might find on occasion they can become quite complicated, especially when you are dealing with multiple use cases; for example back office admins, customer functionality, different clients.

One User Story

Ok, so this is a basic example; but you get the idea. In this example there are two user stories explaining the same requirement — just from different roles.

How to Know When to Merge?

As a basic rule, when creating user stories, remember that a user story should be a usable piece of functionality, and represent all the work that needs to be done. If no additional development is needed (like the example above), then they should be merged, since in this case both customers will access the online store in the same way.

About the Author

Ashley-Christian Hardy
theproducthub.io

Product leader. A strong advocate in innovation, experimentation and building great products with the use of qualitative and quantitative research.

Product leader. A strong advocate in innovation, experimentation and building great products with the use of qualitative and quantitative research.