Cycle 1 User Stories

The Product Backlog is the master list of all functionality desired in the product. The customer owns the product backlog: he can add/remove/edit/prioritize requirements as he wishes.

During each iteration, the customer and the team agree on a set of requirements that will be delivered with the planning game.

The team owns the technical decisions and can organizes the work into work items. The team members can add/remove/edit/prioritize work items as they wish.

Beware the following:

• Requirements here are vague on purpose.
  

• Not all requirements will be implemented.
  

• The number of points per requirement is discussed with the customer as well as the exact requirement.
  

• The team must estimate the effort required to implement requirements and commit to work that can be delivered next week. 
  

Requirements are expressed as short user stories, usually of the form As a [role] I can [function] so that [rationale]. They are associated with acceptance criteria.

---

User Management

• As a visitor, I can register in the system with username/password, picture, and list of interests.
  • Acceptance criteria: password validatation must ensure password is strong
• As a non-authenticated user, I can authenticate to access restricted pages.
• As a non-authenticated user, I can reset my password in case I forgot it.
• As an authenticated user, I can change my password
  • Acceptance criteria: password validatation must ensure password is strong
• As a user, I can create an organization (with picture, list of interests) so that multiple users can work on behalf of each others.
  • Acceptance criteria: the user is the admin of the newly created organization
• As an admin of an organization, I can add and remove users to/from the organization.
• As an admin of the an organization, I can promote or revoke admin right to members
  • Acceptance criteria: I can revoke my own admin right only if there's a second admin
• As a user, I can delete my account
  • Acceptance criteria: I can delete my account only if there's a second admin
• As a user, I can suspend my account so that it is as-if it had been deleted but I can register later again and obtain my previous information
  • Acceptance criteria: I can delete my account only if there's a second admin

Buy and Sell

• As a user belonging to at least one organization, I can select which organization I'm currently working for.
• As a buyer, I can charge my account or the account of an organization with credits using a credit card
• As a seller, I can enter and edit items that are "inactive"
  • Acceptance criteria: items can have a title, a picture, a price, and a description
• As a seller, I can turn "inactive" items into "active" items to sell
• As a seller, I can turn "active" items into "inactive" items to edit them
  • Acceptance criteria: it is possible only if nobobdy bought the item
• As a buyer, I can buy an active item at the fixed priced indicated.
  • Acceptance criteria: transaction succeeds if I have enough credit, and if nobody bought the item in the meantime
• As a seller, I can indicate the number of available copies I have of an item so that I don't need to enter one digital item per physical item, but can instead keep track easily of my inventory.
  • Acceptance criteria: the number of copies shown to other users must be consistent with ongoing transactions
• As a seller, I can indicate the maximal time an offer is valid, to give incentive for other users to buy it.
• As a buyer or seller, I can comment on an item, or previous comments, possibly to ask a question and provide guidance to other users.
  • Acceptance criteria: only active items can be commented

Activity Monitoring

• As a member of an organization, I can see the activity of all organization's members (temporal list)
  • Acceptance criteria: the activity log includes addition of items, edits of items, active/inactive status change, comments by users, failed and successful purchase of organization's items by other users, failed and successful purchase by organization's members
• As a member of an organization, I can filter the activity log to show only specific types of activities (e.g. purchase, comments)
• As a seller, I can revert to a previous description of the item since the system keeps track of the changes
• As a seller, when one of my item is bought, I receive an email.
• As buyer or seller, I can watch a user, organization or item so that I can easily track activity related to them.
• As a buyer, I can add an item to my wish list.

Browse and Search

• As an authenticated user, I can see the profile of a user or an organization.
  • Acceptance criteria: the profile lists all active item from the user / organization
• As an authenticated user, I can search with free text for items that interest me.
  • Acceptance criteria: the display must be compact to list many items, and a quick view expand an item "in place" without redirecting to another page.