Yes we can, come on! 👌💪

Hello 🙌

On Friday we had a visit in the classroom, teacher Maria invited Professor Sodel Vásquez, the goal was for each team to expose again, but time only the problem, the solution and the prototype would be exposed, this in just 2 minutes; with the intention of being more concise and not talking so much because in the long term it only ends up being boring people, then Sodel would give his opinion about our exhibition, we honestly never imagined that he would say what he said since he concentrated more about the way the team representatives presented, since they told us that, in general, we did not take advantage of the time because some teams that do not exceed 2 minutes made it very fast and nervous. Something that he also told us is that if in the future the application we cultivate we had to learn to sell things, make commercial requirements known to be able to get the attention of entrepreneurs and be able to sell the idea, also something he told us and that other teachers always tell us is that we should not read the slides since that is only a guide, also the way to stand and their movements were important and reflected nerves. At the end of her comments, teacher Maria gave us her own comments, reinforcing a little what Sodel had told us, told us that for the following exhibitions she would invite more people locked up to come to evaluate our exhibition.

In general we felt good about the work and the decisions we made, even if they told us that they still did not see the prototype since we were inspired to do it as a comic strip, but in reality what they wanted to see were mockups (what we already solved). We believe that the decision to send Jorge Alfonso on behalf of the team was correct, because he is one of the best expressed and we feel that he is not so shy, but we have decided that in the following presentation the representative will be another person of the team.

On Monday we saw the requirements phase and all the documentation necessary to have proof that it was done as it should, in general we realized that we had to interact with stakeholders through interviews, surveys and other type of methodology to collect requirements We opted for interviews, we also reviewed what documents were required and which ones we could omit. In the end we realized that we are a little late since we had not yet started with iteration 1 but we began to separate the activities by making the most atomic and putting a tentative date. The end of the first iteration we left for October 31, 2019 but the teacher told us that the iteration was very large, that we tried to cut it, we decided to separate the general requirements with their respective activities to be able to atomize things and thus be able to be a little more accurate with the time we would put in each activity, ☹ curiously the sum of the time resulting from the sum of all the activities threw us as a result that we would finish the iteration the October 31, 2019, with this result we felt a little bad since for us all the activities we had for the first interaction were essential to be able to give value to the application.

On Wednesday the teacher started the class taking up the requirements phase, she mentioned that the whole team should participate in this, this did not worry us since we have all been involved in the requirements and we all understand the problem, she also mentioned that the technical leader is responsible for the design, but the rest of the team should help.

That same day, a team that hadn't presented on Friday, presented with the same dynamics of 2 minutes and its feedback at the end, also the teacher went with each team to review in particular the defined goals and the definition of value 😊 we explained our qualitative and quantitative objectives, in general the professor was worried about knowing how we would demonstrate that the goal of respect for colleagues was met, at this point he gave us an example of what we could establish, "no team member came out crying", "They don't talk rudely." The quantitative objectives had that "70% of the defects would be eliminated before the first compilation", this was solved by putting "70% of the defects found before the first execution".

In the part of the duration of the activities he told us that the end of the the iteration would last a long time, that we could remove all the activities related to canceling the trip by the passenger and driver since if we omitted this we would not be taking away the value of the application, which we went through for the second iteration but these two activities only took 2 days off from work, so we decided to give another review of the activities to see which were essential and which we could go to the second iteration, but without losing the essential for the first iteration.

Finally, the end date of the iteration is October 28, 2019, for us it is a short time and we are a little worried that for some reason the dates established for each activity will be delayed; But we know that we have to embark on the adventure to be satisfied with our work.

"Everything seems impossible until it is done" - Nelson Mandela.

Happy weekend and remember friends on October 9, 2019, there is a national strike!😆

Goodbye!!