Specification

In order to be able to produce the high-quality work that we want to be able to produce, it is very important to fully understand the context of the changes we’re trying to make, for whom they are, and the value they provide to the user and thus the business.

In addition, we need to be able to write down summaries of requirements in issues that help us pick-up the conversation at a later point, when we actually get to implementing features.

We, the engineers, write these requirements down when we do a design walkthrough, with the designer that worked on a feature, in the form of user-stories.

Examples are:

• As a collector, I want to be able to filter artworks by for-sale only, so that I can easily find works I can buy.
• As a guide, I want to only show for-sale artworks, so that I can grow our GMV.

These stories do not necessarily have to contain all the implementation information, for that you would create a list of acceptance criteria, which would typically be a list of TODOs on the issue you create for a story.

Role definitions

• Guide An entity that helps collectors find the works they want to collect, which is Eigen in our case.
• Collector Somebody who buys artworks.

Resources

• Short practical explanation of User Stories https://www.youtube.com/watch?v=LGeDZmrWwsw
• Long talk on User Stories https://www.youtube.com/watch?v=6q5-cVeNjCE

Visual Design

During the same design walkthrough, the engineer will tell the design how they would like the visual design to be split up so that it can properly be divided over various issues. See Design Process.