Think about what a user of the system wants to accomplish when using the system, and show that. 

Ensure you explain all of the validation which happens in the login form, e.g. "Here we will try to enter a password with only lower case letters. Now watch as I type all numbers and it tells me I need to have a letter. Now I'll try a password that is only 4 characters long").

Think of their user journey and show that.

Click every little button (e.g. "The first menu item takes you to the home page. The second button takes you to the contact us page. The third...").

Point out every little feature (e.g. "In the top right we have a login button. Next to this is a button for if you forgot your password, and here is a button to sign up").

Does it behave exactly as they expect?

Is it really what they wanted?

Does it add value to their business?

Can they use the software?

Are there any bugs

Does it crash?

just the client or their representatives (e.g product owner)

the team and the client

the mentors and the team

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?