Improve communications

Improve the Trello Board

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

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?

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?

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

Your user requirements

The developer who built that part of the system

Acceptance criteria on your user stories

how data is recovered in a systems failure

response time

valid data sets

invalid data set

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

screen design

using different browsers

security of the site

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

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

using no data or blank or default data

using invalid data such as negative values

illegal data such as numbers in an alphanumeric field

response time - whether an application responds quickly enough.

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

using valid data

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

security of the site, can it it be hacked