During the eCommerce Discovery process, we ask our eCommerce clients to invest time developing ‘user-stories’ for the various features and functions they are requesting for their site.
What is a user story?
User stories are short, simple descriptions of a feature told from the perspective of a user or customer of the site who desires that capability.
They typically follow a simple template:
As a < type of user >, I want < some goal > so that < some reason >
This sentence describes something that a user wants to do and why they want to do it.
When encouraging our clients to discuss the requirements they have envisioned for their site using the “who, what and why” formula.
As an <who> I want to <what> so that <why>
A typical eCommerce store owner User story would be:
<Store visitor> <can view lists of items for sale> so they can<search by name> <filter by price>
User stories encourage discussion about the desired functionality and help the design-build team understand which features and functions are most important to the Stakeholder. Although the User Story does not contain any implementation or design details, these user stories can be used to plan sprints. The team can break each user story down into a number of technical tasks, divided into the scheduled sprints. These tasks will contain implementation details and will cover all that is needed to meet the requirements of the client’s user story.