Check acceptance criteria is complete and validate  with client on any user stories before moving them to the to do lane.

Improve the Trello Board

Improve communications

You need to find out  about additional statuses and rules dictating how entities are joined together. for example, if a customer is deleted, what happens to any orders they have?

It doesn't matter, In our table we will just create an add, edit and delete function for each entity. 

You need to find out  about additional statuses and rules dictating how entities are joined together. for example, if an order is deleted, what happens if the products on that order?

You need to find out  about additional statuses and rules dictating how entities are joined together. for example, if product is deleted, what happens if that product is on an order?

Your user requirements

Acceptance criteria on your user stories

The developer who built that part of the system

valid data sets

security of the site

how data is recovered in a systems failure

screen design

response time

invalid data set

boundary conditions of input data (eg entry of dates earlier than that day, that do not make sense for your application)

running the system in different environments (mobile devices, desktops etc.)

using different browsers

valid data such as customer name but is too long for you to store

security of the site, can it it be hacked

whether the application will run in different environments, eg. mobile devices and desk tops.

using valid data but including problematic expressions such as O'Toole as a family name.

using no data or blank or default data

response time - whether an application responds quickly enough.

using valid data

using invalid data such as negative values

illegal data such as numbers in an alphanumeric field