Following Agile methodologies, let's write two user stories that describe the functionality of our project. User stories shouldn't be comprehensive documents describing the entire set of features of an application; rather small cards are perfect for not only describing what the user is trying to do, but why. Also, we should do this without trying to design the whole system up front or delve too deep into implementation details.
First we need a story about seeing the different journey types from which our users may select:
|
As a |
traveler |
|
I want |
to see the different types of journeys I can get recommendations for |
|
So that |
I can decide what kind of evening to take my partner on |
Secondly, we need a story about providing random recommendations for a selected journey type:
|
As a |
traveler |
|
I want |
to see a random recommendation for my selected journey type |
|
So that |
I know where to go, and what the evening will entail |
These two stories represent the two core capabilities that...