The first sprint was a productive as well as eye-opening experience. This is the first sprint and set of work that we completed as a team during this capstone. The first sprint was able to teach us how to effectively and efficiently spread out the work, ask questions between each other for collaboration as well as knowing when to go to outside sources such as other teams or the professor. In our first sprint, the work revolved mainly around creating a new field for the guest object that would be able to store the value of the date of first entry. This one task was able to be split up into different working portions. These included adding this field to the API, the back end and the front end. Besides the main task we also completed the tasks of mounting a volume to the docker container allowing data to persist even after rebuilding as well as working on a CORS issue prohibiting the back end from communicating with the front end.
This is where things started with working well. Sean was working on the back end while Hiercine was working on the API, since they shared the same subsystem they were able to collaborate to solve the problem together. This was also scene with Lynn working on the front end and Winston fixing the CORS issue they both had experience with the front end so they were also able to collaborate. This is one of our biggest strength is our team working abilities and being able to collaborate to make the work flow more effectively and efficiently. Next, are the things that didn’t work well. I believe that everything we did was to the best of our abilities. The only things that could be commented on as not working well is our lack of knowledge in certain areas. For example, not knowing exactly how certain systems worked within the code since it was our first experience with it. In addition, when it came to linting issues, one linter was for commit messages which we recently learned how to make proper messages so we had to learn how to make them after causing the linter to fail.
I believe as a team we are in a very good spot that cam only go up. I think as a team we can work at continuing to learn more about the systems and tools being used. In addition, I believe when it comes to merge requests we can be more efficient in making sure all work gets merged in a timely manner and we all collaboratively spread out the merging work. As a individual, I believe I can improve on learning more about the code so I understand more what is happening so I can make better solutions for the issues at hand. I also believe I can work more at improving how I collaborate within the team.
The pattern I selected was “Rubbing Elbows”, I chose this because I felt it related very well to how we worked as a team. Even though we all had our own assigned issues, we were able to find commonalities between them allowing us to work together to increase efficiency and find solutions that we would not be able to find on our own. The “Rubbing Elbows” pattern is knowing when to seek collaboration and being able to learn from those you are working with. I don’t think reading this prior to the sprint would change anything since we already were collaborating.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfobackend/-/issues/139
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/issues/107
https://gitlab.com/groups/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/-/epics/56
From the blog CS@Worcester – Giovanni Casiano – Software Development by Giovanni Casiano and used with permission of the author. All other rights reserved by the author.