Iteration 3

###Iteration 3 planning:
###Iteration 3 goals:
*user should call and be in touch the gym
*user should see the list of teachers in the gym
*client will know when his contract is going to expire
*client should renew the contract
*client will know a spare room in gym
###Testing:
optional tests on the main tasks of this iteration:
1.
test: expire contract
expected result:
-The client get a massage that his contract is going to expire.

2.
test: list of teachers.
expected result: The link of the navbar "teachers" will go to the right page
3.
test: encryption password
expected result:
-all user names will not be shown in the data-base
-the code will not be more than 7 digits
4.
test: register to a lesson
expected result: client will get a massage if its ok or not
5.
test: table of teachers
expected result:
-the table will open correctly
-the relevant deatails will be shown in the table
6.
test: table of machines
expected result:
-the table will open correctly
-the relevant deatails will be shown in the table
7.
test: table of rooms
expected result:
-the table will open correctly
-the relevant deatails will be shown in the table
###Information about the tasks: Huboard
Issues
Our gitter

###screenshot of the huboard before of this iteration

###screenshot of the huboard in the end of this iteration ###conclusion of the iteration:
There is still the risk that we won't manage to accomplish the project till the end of the semester (which is really very close...) so all the team must be responsible and care about our project: checking mails twice a day (at least), doing their tasks from the huboard not in the last moment...

###Meeting and discussion summary, feedback of the customer:
*We decided to find a solution to the different kinds of visual studio in order to synchronize all the works to a single project and to be sure that each one know what should she do in the current itaration and to be sure that the tasks clear for every one. ###Iteration 4 planning