During the week, we were reviewing some aspects of our work, such as documents and how we should update them as we go through the iterations. In addition, we have worked on our second iteration; 1) validating, 2) making-updating documents and 3) coding the new features. 1) In the validations we find correction points only. Our product is going in the right direction because in all the validations we verify that the application begins to take the real form that we expected. 2) The documentation has been carried out efficiently and it has become faster, also, the teacher explains us that some documents are important and we didnt have them or didn't was updated. So we have to make and update them. 3) In the same way, coding has been carried out efficiently and faster, because now we know better the artifacts and tools. Well, in fact the codification was normally done, but the problems of knowledge or the time lose in search new methods now was insignificant. ...

We are already in the second sprint! Friday was a day of many emotions, after almost a month with the first iteration, we finally delivered the functionalities for this sprint, although of the 6 user stories we said we would build, we could only do 5; it was satisfactory since each member of the team made a user story. Being able to deliver the minimum viable product excited us a lot since the first sprint seemed endless, but thanks to the effort of the whole team we were able to finish it. After the teacher evaluated our work, we took time to live with the classmates sharing a delicious "pan de muerto" made in the bakery of our partner Raúl and a delicious chocolate made by José Luis Zorrilla, this relaxed us a bit and we also began to reflect on this beautiful tradition of the "día de muertos". On Monday we began to see the plan for the second iteration, the teacher presented us a table where the tasks were shared, he suggested that. We do somethin...

The clear evidence that two members were not working 😂 It's a team joke  😆😂😜. This week we were learning the issue of sprint review where we analyze what was done and what is pending as well as the positive and negative things. In addition to that we review with the team what was learned either with tools, people, relationships and most importantly what each team member learned. In this phase, it is verify  the goals established for the team, product, roles, quality and personnel were met. Once this is done, the next step is postmortem phase, where improvements are proposed for the new sprint, of preference small changes so that they can be fulfilled. After this you have to go to validate the product with different people to have a feedback and know what we should work to improve our product. We put all our effort  in the development of our application we face complicated situations because we must have a fast learning because they are technol...

Hello again! 👋 We are very happy to have you back here. This week was very interesting,  hope you enjoy reading. 📖   On Thursday, we had a talk about how the ISO / IEC 29110 standard was applied in the systems development department of the UAZ. This talk helped us to understand the importance of documenting our development process, and the advantages of being certified under a standard. It is important to emphasize that the objective of a certification should not only be to obtain a paper to be recognized, the important thing is that in reality the activities of the process are carried out in the correct way and quality products are developed, it would be of no use to be certificate, but do things without an order or following a process. Among the advantages mentioned to us about attaching our process to a standard, it mainly has to do with order; in addition, there is more control over the projects that are being carried out; you know what your status ...