Project Summary

##Last Iteration Summary Iteration 3 - DUI ##Team spirit We started the project as couple of friends, each one wants to do the best site for the organization. It was a big advantage for us we knew each other before because it helps us to deal with private issues and events more easily. As the project moves on, we understood more the importance of a crew member that can gives you his own point of view on many aspects. That helps to think about better solutions to problems that occured during the project. We are finishing this project with the feeling we accomplished our mission, we are more familiar with modern website application (client-serve) than before, and we finished the project more united than before. Throughout the entire process, all the team members kept in mind to write the code accordingly to our coding conventions which we specified in the beggining.

##Development process In general, the website's development process accomplished its goal. In each iteration we learned how to efficient and maximize our production in the iteration, by reasoning from the previouses iterations. For example, In the ZFR Iteration we had a bad time estimation about the iteration's issues and tasks. Therefore in the next iteration, in the iteration planning, we dedicated more time and effort to estimate the issue's time of work. After all, we succeded to reach our goal in the project and we created the website with all the aspects we planned.

##Project reflection The whole progress taught us which elements in the project's stages were the most meaningfull to us in our work.

1. Requirements - at the first stages of a project, the project's members should meet with the client and highly attention to the client's requirement. To make a good project first of all it have to meet the client's requirement otherwise, as good as the project could be, it will not be usable. Therefore, it's highly important to make sure that you understood well all of the requirement of the client detailed.

2. Implementation - to make a high quality project, after the had a good knowledge about the client's requirements, we need to implement our product on the best shape, using all the knowledge and up to date aspects in the field. In our case it would be the client-server programming method and NodeJS platform.

3. Teamwork - in a big project, apparently you will not work alone, therefore it is important to work as a team and to have a good cooperation between the members. In the case of software product first of all it's important to specify coding conventions like we did, in order to allow other members of our team to read and understand our code. Coding review it's another important element in teamwork, what I can't see - maybe my project mate will.

• In our project, the element that works the best is the teamwork. We treated that element as top value, always helped and advise each other to optimize the quality of our code and product.

• The challenges and risks that we had to deal with along the project is to expose and learn new features and use them in real time. (e.g NodeJS, Google API)

##Wiki updates

• User Manual

###Final Presentation