The product backlog comprises an ordered list of requirements that a scrum team maintains for a product. It consists of features, bug fixes, non-functional requirements, etc.—whatever must be done to successfully deliver a viable product. The product owner orders the product backlog items (PBIs) based on considerations such as risk, business value, dependencies, and date needed.
Items added to a backlog are commonly written in story format. The product backlog is what will be delivered, ordered into the sequence in which it should be delivered. It is visible to everyone but may only be changed with the consent of the product owner, who is ultimately responsible for ordering product backlog items for the development team to choose. [Wikipedia-Scrum](https://en.wikipedia.org/wiki/Scrum_(software_development)#Product_backlog)
In this section you will find some information about the use of the echOpen device and the technical constrains that come with it. It is divided into three subsections:
Main characteristics: information about the use of the device, the expected characteristics of the displayed image and the main technical requirements.
Technical constrains: here you will find more detailed technical constraints.
Functionnal specifications: here is a description of the functionalities that the system must perform.