As a customer, I want to purchase tickets for an event, so that I can attend the event.

[joaopascoalfariafeup]

Notes

You can add here some details about the user story that do not fit in the short title, associated non-functional requirements, etc.

• one or more tickets
• electronic payment

User interface mockups

Add a draft of the corresponding user interfaces, a simple mockup or draft, if applicable (see also slides of theoretical classes).
TBD

Acceptance tests

For each user story you should write also the acceptance tests (textually in Gherkin), i.e., a description of scenarios (situations) that will help to confirm that the system satisfies the requirements addressed by the user story (see also slides of theoretical classes).
TBD

Scenario: 
Given ...
When  ...
Then ...

Value and effort

Add a rough indication of the value of the user story to the customers (e.g. MoSCoW method) and the team should add an estimation of the effort to implement it, for example, using t-shirt sizes (XS, S, M, L, XL).
TBD

User stories

• As a customer, I want to search and browse events, so that I can select the one to buy a ticket for. #7