The third and final sprint of our semester was eventful and successful for our team. We made great progress on many of our major tasks. It was a relatively smooth sprint with only a few resolvable issues. Our communication was on point, and we remained entirely transparent about our goals for the sprint. The focus of this sprint was finishing the guest info system’s installation and setting up subsystems as we went forward. We successfully worked with another team to fix the formatting on the guest info system and we now have a stable build. Our team also completed port mapping, and created a table for our ports. We also have a working landing page (missing Keycloak) and the beginning of a working weight-based inventory system. We set fair and manageable goals throughout this sprint, and prepared the next teem excellently for the tasks to come. We are fully pushed to gitlab with all our important information, and we have documentation to guide future teams. I spent my time doing three major tasks; getting the guest info system working fully, researching different ways to handle multiple docker compose files, and beginning work on the weight-based inventory sub-system.
What I thought didn’t work well in the sprint was the time crunch on our issues. While we made great progress, due to the upcoming presentations and end of the class we did not finish as much as we’d have liked. We left some tasks incomplete to a minor degree, although we are proud and happy with the work we made. I would personally have liked to finish the inventory sub-system. I was unable to do that due to time constraints at the end of the semester. We were working on getting the guest info system working up until that point.
As a team our biggest weakness is our shared lack of knowledge in the subject, requiring us to pool our brains for certain tasks. While we worked independently to a great degree in this Sprint (an improvement from the last two sprints), I feel that due to the complexity of our tasks, we did not adequately work independently where we could have. A lot of time in my opinion was lost to this communal working, although we did get farther than expected with the sprint. As an individual I could improve better at communicating my work. During team work class I am not immediately vocal with what I am working on, and although I am making progress I am not being entirely transparent with my team. Going into future work I will be more transparent with my work, having learned from this experience.
The apprenticeship pattern that best describes my work in this sprint is Walking The Long Road. I felt that this fit because of the work I was doing throughout this sprint. While I could have stopped coding and cleaned up with more clerical work, I continued to remain persistent with adding features and improving our server. This led me to research merging docker compose files and adding the inventory system, which became an excellent end-of-sprint addition. Teams in the future will benefit from this addition, as they will have an easy portion to implement into the server to get their feet wet. By remaining consistent at improving my abilities, I avoided resting on my laurels and considering the job done before it had been completed.
My tasks:
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/25
This was my earliest task, involving fixing the disconnecting backend. Working with Professor Wurst and Cameron, this was completed.
This was my major task for this Sprint. I spent time making sure the guest info system was running smoothly, as well as adding new subsystems to test towards the end of the sprint.
From the blog CS@Worcester – WSU CS Blog: Ben Gelineau by Ben Gelineau and used with permission of the author. All other rights reserved by the author.