Third client meeting reactions

Last Friday, we had our third client meeting, this time with professor Ackley. As in the previous sessions, the first part of the meeting was addressed to review the assigned tasks made by each member of the team. During the third week of the project, I was working with Natalie on the current challenge progress bar. We decided to meet together last Wednesday (two days before the client meeting) and we spent four hours trying to find a way to update the bar dynamically using jQuery when a user clicks on the "Success" button. We also made some tests to try the avatar uploading system, because we wanted that the picture was cropped if it was bigger than certain resolution. Despite having several problems, we finally got it, and we were able to obtain something that worked properly with random values, enough to be shown in the client meeting if it was needed.

In the next part of the meeting, our team needed to prove somehow that the key technology choice for Demigod project by using the Goldilocks method. In this case, we justified that Ruby on Rails was the best option to develop our website. Fortunately, it was quick and clear. Too much: Java or PHP (Great flexibility but would have taken too long to build up an entire), too little: Open Source Content Management Systems such as Wordpress, Joomla! or Drupal (easy to use, but the platform would not have been useful for creating a customized website), just right: Ruby on Rails (nice middle ground between customization and automatic generation).

Furthermore, we provide explanations about how certain parts of the application worked (progress bar, challenge selection and follow up, etc.). From my point of view, we made a mistake when professor Ackley wanted to see some of the parts of the website that was already working. We tried to run the website, but the time was limited and we finally were not able to show the model properly because of lack of preparation for this part of the meeting. Next time, we have to bring a laptop with the rails server running and all ready to be shown. Time is very important in a meeting, and we (and mostly our client) cannot afford to waste such a valuable time trying to set up the website. I hope we do not make this kind of mistakes any more.

Additionally, it seemed we were lack of confidence when Ackley asked us questions such as "What happens if you are doing a challenge and you forgot to check in?" We also turned in the final version of the timeline, as well as a list with possible challenges and the Goldilocks method outlines. Finally, following the timeline, we reported the tasks appointed to each member due the fourth week.