In this Sprint the Biggest take away I had was coming to the realization that every aspect of working in the class either it be doing the research required or diving directly into the code itself it must be recorded and accounted for was time spent working. Being able to properly weigh the tasks that we had to do on the first time around was tricky as we always seemed to spend much more time on issues that we thought would take only a couple of minutes, but the beautify of it was that we could always go back and adjust the weight of the issues afterwards.
The thing that worked the best for us was being able to delegate issues to ourselves and others who had the capacity to solve those issues relatively quickly and with little to no support required from others that would take away from the time that they would spend on their own work. The other big aspect that worked for us was being able to come together and support one another when we had issues in our separate tasks. I can think of many times where kelvin offered his support when I was having Problems with my committing in the backend issue I was working on during the sprint, and I can say that others in the group stumbled at moments when someone else came and gave input that allowed for the issue to be solved.
The biggest change we would need to make as a team would be to definitely work on creating more issues when we are planning our Sprint, when we started this one we were under our target weight at around 28, in order to make sure we hit out goal weight we need to make issues no matter how simple we think the solution to issues may be. When we looked over all the issues, we had on our boards we realized that some of the issues we created could be broken up into more issues and some could even be weighted more.
The change I would make as an individual is to focus more on the smaller issues as well as doing research on the bigger overarching issues that require more attention. Front end was the longest I had spent on issues during the sprint was looking over the front end as it was the one aspect the GuestInfoSystem that I had not touched, even in the previous class. I spent most of one week just doing as much research into VUE as well as how to navigate the front end and it was still difficult to wrap my head around what needed to be done for the issue. While this research was important and necessary I could have also spent time completing issues on other aspects of the System of which I had more experience on, however I was interested in seeing if I would be up to the task of taking on the FrontEnd.
This issue was solved removing any of the Get/guest parameters from the GuestInfoAPI, which was found primarily in the listGuests.yaml
This issue was solved by removing many parts of the guest.js file as well as using the updated API from the other repository and importing it into this backend.
From the blog cs@worcester – Marels Blog by mbeqo and used with permission of the author. All other rights reserved by the author.