This template is to describe the user story for a desired feature. It intends to explain the user role in a system, the desired activity, and what is intended to be accomplished by successfully completing the user story. For our Agile dev team, user stories are the primary method of understanding user needs, so they can build it right.

Overview of the feature

Feature: tea and food pairing - expands pairing model not only for wine and food

...

Business motivation

• Expands pairing model to tea and foods pairing
• Having alternative beverage recommendation
• Attract more customers

...

User stories / Jobs To Be Done

As an employee at PairAnything , I want to expand the pairing model so that we can recommend pairing of other beverages, not limited to wine. When my clients access the PairAnything App for pairing recommendations, I want to introduce them our unique pairing recommender that can pair tea and dishes ad well.

When < situation> I want to < Motivation > so that < Expected outcome >.

• When our business partners are trying to work with PairAnything, I want them to also see that we have other pairing options, we can work with teahouse and tea company to pair tea with dishes as well and enhance their dinning experiences, so that we can attract more customers and develop more clients

...

###Acceptance criteria Specify the requirement(s) by which the user story can be accepted as completed correctly and meet the user need. List the goal and metrics to judge its success.

Goal: (e.g., Simplify the user experience) Metric: (e.g., Customer Satisfaction score increases)

...