Sprint Retrospective

Sprint 2 Retrospective

Introduction

• In this sprint we were focused on scaling up our productivity and getting the UI underway.
• This sprint lasted longer than sprint 1 but ended up feeling very back heavy because we were delayed on working on the front end until we had access to the new template.

Links to Activity on GitLab

• https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/issues/93: This issue covered our meeting with team 2 as and what we planned to accomplish with what they found. We ended up making a meeting notes file with our conclusions and next steps.
• https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem/checkoutguestfrontend/-/issues/45: In this issue we went over our UI design and tried to think of ways to improve it with a consistent color scheme and matching the aesthetic of the rest of the UI.
• https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem/checkoutguestfrontend/-/issues/43: This issue was by far our largest and was very substantial. This issue entailed actually creating and implementing the front end that we had discussed.
• https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem/checkoutguestfrontend/-/issues/39: This Issue was focused around looking through the other projects and determining if there was an existing UI framework. We found none that were working and had to wait on out template

Reflections on the Sprint

What Worked Well?

• Like the last, In this sprint I found that communication as a group was key to our success. Any problems that we faced were made much easier when we tackled them as a group instead of alone. I think that our review process was good and allowed us to effectively tackle our goals.

What Didn’t Work Well?

• I think that the main thing that we struggled with was managing the time of this sprint, considering that we were halted in our efforts to make the front end until we had a working template to base ours off of. In the end we got it done after a busy end of sprint.

---

Improvements for Team Performance

The team’s ability to communicate and tackle problems collectively was a strong point during this sprint. It was an effective carry over from the last sprint and will hopefully be reflected in the next sprint as well with some of the following improvements:

1. Keep a consistent schedule: In hopes to avoid a repeat of the last sprint where everything was stacked at the back of the sprint, It would be beneficial to manage our time better as a group with a more consistent meeting time.
2. Division of Labor: we continue to ensure that one person does not get stacked with to much to do while others get left with little to work on.
3. Streamlined Communication Channels: Same as the last sprint, ensuring that all discussions, especially those related to problem-solving and decision-making, are logged in an accessible and organized manner would help maintain clarity and continuity.

Personal Improvements

Reflecting on my personal challenges during this sprint, specifically around managing merge requests correctly, I see valuable opportunities for growth:

1. Gitlab Use: I still struggle with some aspects of gitlab and hope to improve that for sprint 3.
2. Proactive Communication: To prevent and swiftly address any uncertainties or errors in my work, I commit to being more proactive in seeking feedback and clarifications from team members.