What worked well this sprint was our division of roles and tasks as well as the planning for tasks and the sprint as a whole. Each member had a specific section of our project that we worked on, some even taking part  in more or most of the project, as well as connecting the pieces of the project. I think we spent a lot of time planning and working out what we need to do, the path we want to take, and the many decisions along the way. This hopefully led to less confusion while working through the sprint. 

What didn’t work so well this sprint was the communication. Communication during certain moments in the sprint was lackluster and thus other members didn’t know what certain members were up to or working on. This also led to those other members having to pick up work had the certain member not done their work within a specific time.

To improve as a team, I think we should communicate more. Specifically, what we’re working on, what we can and can’t do, if we need help, and to complete tasks that require more than one member. As we move towards a complete product, I think the work may become more complicated and the communication will be necessary to connect and join respective pieces of the project.

To improve as an individual, I need to communicate more and stay on top of my work. Putting in more effort to communicate with my teammates and completing my tasks should be my number one priority. Personal issues, lack of effort, or lack of understanding led to me not being able to complete my tasks. Not only is that quite the issue, but I didn’t communicate any of that to my team at all, and thus they have no idea what I’m up to and have to pick up the work that I didn’t do. 

The apprenticeship pattern I felt was most relevant to my experiences was “Expose Your Ignorance” from Chapter 2. This pattern states that there are people depending on you to know what you are doing and need confidence that you can deliver. The solution to this pattern says to “Show the people who are depending on you that the learning process is part of delivering software [… and that the …] most obvious way to expose your ignorance is to ask questions.” I felt that this pattern partly describes what I experienced during this sprint. There are people relying on me to do my part but I don’t have the confidence in my ability and am unfamiliar with a lot of the processes that we will work through. My teammates, on the other hand, are very familiar with the processes or are very willing to learn. 

Although I did expose my ignorance and ask questions of some of my teammates who were much more experienced than I am, I could have done so much earlier. Not only that, but I still feel hesitant to ask questions because there are plenty of things I should already know but don’t. Reading this pattern may have encouraged me to ask questions more often and much earlier in the sprint, increasing communication from myself and between teammates, and would hopefully lead to me knowing what I need to know to tackle my tasks.

From the blog CS@Worcester – Kyler's Blog by kylerlai and used with permission of the author. All other rights reserved by the author.

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.

Retro

This first sprint was a deep dive into new territory. Our team focused on understanding our project, setting up the proper tools and environment, and managing challenges as they arose. We have created a working agreement, completed multiple issues on GitLab as individuals and as a team, and we have ensured collaboration was a priority throughout each task.

GitLab Activity:

• README.md – Updated the README document for our GitLab group to detail the major goals of our project.
• Docker Compose Watch Documentation – Drafted documentation for Docker Compose Watch for possible use for CI/CD later on

Our team dynamic has been great from the beginning with a strong working agreement in place from day one being we were able to focus on the work getting done without worrying about team cohesion. We were able to complete a lot of research during this sprint to gather information about Docker and its many variants, NGINX, and CI/CD options. This research was turned into details documentation within our GitLab group. We worked successfully toward solving problems like issues with debugging Docker Containers, using SSL certificates properly, and scheduling our tasks based on priority. Overall, flexibility in our team has been vital and we have adapted to any challenges that we have faced.

I believe we have already learned a lot through our research and time spent of digging around in the server for answers, but we can still work toward improving our outcome by approaching our research differently and ensuring we have a clear focus on what we want to accomplish. Personally, I plan to improve my work by improving my time management regarding troubleshooting/research because sometimes I can find myself down a rabbit hole and working to ensure that all of my teammates and I are on the same page through clear communications.

Apprenticeship Pattern: Retreat into Confidence

“Retreat into Competence” is a strategy for regaining confidence when feeling overwhelmed by complex challenges. It involves stepping back into an area of expertise before pushing forward again. The key is to avoid staying in the comfort zone for too long and instead use the retreat as a way to launch forward with renewed energy. During this sprint, there were moments of troubleshooting that felt a bit discouraging, particularly with Docker and SSL certificates, where progress seemed a little slow and confusing. The feeling of being stuck highlighted the need to step back into something familiar—whether it was revisiting basic Docker configurations or focusing on smaller, more manageable tasks like completing documentation on GitLab—before tackling the larger issues again. Had I known about this pattern sooner, I would have structured my work differently to maximize results. Moving forward, I plan to:

• Time box troubleshooting sessions to avoid going down the rabbit hole
• Focus in my research to ensure that the resulting information is useful to our project
• Seek help from teammates during moments of need
• Ensure that I am still completing the smaller tasks that can be completed while working on larger issues

This sprint was a valuable learning experience in both technical and team collaboration aspects. While challenges arose, the team adapted, and I gained insight into how to manage difficult situations more effectively. By refining research strategies, improving troubleshooting workflows, and applying patterns like “Retreat into Competence,” I can optimize future sprints for even greater success.

From the blog cameronbaron.wordpress.com by cameronbaron and used with permission of the author. All other rights reserved by the author.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/frontend/-/blob/WEB-APP-FRONTEND/src/frontend/src/components/UPCScanner.vue?ref_type=heads

This is a link to the UPC scanner component that I recently implemented.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/frontend/-/blob/WEB-APP-FRONTEND/src/frontend/src/layouts/MainLayout.vue?ref_type=heads

This is a link to the Main Layout for the Web App, this is essentially the homepage.

Reflection on What Worked Well

One of the biggest strengths of our team has been our ability to delegate and handle specific tasks effectively. Each team member has taken ownership of different aspects of the project, whether it’s the frontend, backend, or database. This clear division of work has helped ensure that progress is made across all areas of the application. Since I am working on the frontend, I have been able to focus on designing and implementing the UI while relying on my teammates to manage the backend and database.

Reflection on What Didn’t Work Well

Despite our strong ability to divide tasks, one area that has posed challenges is communication. There have been instances where misunderstandings or lack of updates led to delays in task completion. Additionally, not all tasks have been finished in a timely manner, which has put extra pressure on certain aspects of the project. This lack of synchronization has occasionally resulted in blockers, where one team member is waiting on another’s progress to move forward.

Changes to Improve as a Team

To enhance team efficiency, we need to establish better communication channels. This could include:

• Holding short daily stand-up meetings to discuss progress and blockers.
• Setting more reasonable due dates that account for individual workloads and unexpected obstacles. By implementing these changes, we can reduce miscommunication and ensure that tasks are completed within a reasonable timeframe.

Changes to Improve as an Individual

On a personal level, I recognize that I can make improvements by:

• Checking in with my teammates more frequently to see if they need help with their tasks.
• Setting personal deadlines to ensure I complete my work on time.
• Being more open to suggestions and feedback from my team, as collaboration often leads to better solutions. By making these adjustments, I can contribute more effectively to the team and help ensure the overall success of our project.

Apprenticeship Pattern: “Be the Worst”

Summary: This pattern emphasizes surrounding yourself with more skilled individuals so that you can learn and improve at a faster rate. By putting yourself in challenging situations where you are not the most knowledgeable person in the room, you can grow and develop your skills through observation and experience.

Why I Chose This Pattern: During this sprint, I have noticed that I can learn a lot from my teammates, especially in areas I am less experienced in, such as backend development and database management. Rather than just focusing on my own tasks, I want to take the opportunity to learn from their expertise and improve my overall skill set.

How This Pattern Would Have Helped: If I had adopted this mindset earlier in the sprint, I would have been more proactive in asking questions and seeking guidance from my teammates. This could have helped me avoid certain mistakes and speed up my development process. Moving forward, I will embrace this approach to accelerate my learning and become a more well-rounded developer.

From the blog CS@Worcester – Software Dev Capstone by Jaylon Brodie and used with permission of the author. All other rights reserved by the author.

Throughout the first sprint there were many learning experiences earned, and a great amount of progress was completed for our server. For a first sprint together as a team, I would say we did very well overall; and the second sprint will only be better. What we did best overall in the first sprint, was completing our manageable goals. In our initial sprint planning, I felt that we set attainable and workable goals. These goals were met by all members of the team in some capacity, demonstrating an equal workload across the team. We were very transparent in our communication, and our communication was frequent and on-topic. It felt that we were very efficient in coming to decisions and working towards a greater goal. I spent my time doing three major tasks; setting up and testing Thea’s Pantry on the server, researching Docker volumes and coordinating with Gio of team 2, and troubleshooting SSL certificates to allow the back-end and front-end to connect without an HTTPS error. 

What didn’t work well in the sprint was our lack of knowledge going into it. Our team in particular is charting entirely new ground, which requires us to learn a good deal before moving anywhere with our project. We also ran into a major issue quite early (SSL error above), which sidelined any progress with Thea’s Pantry on the server. We were able to overcome most of our obstacles, and prepare for an even better sprint two, but there was a rough start with the freshness of the material and our inexperience running sprints. 

As a team we could better work independently, as that is our main drawback. We had very little issues communicating, planning, or working; but most work was done as a group and we pooled our brains into individual issues. This slowed us down, and although we reached many of our goals, had we worked more independently we may have gotten through more. This is something we can improve for sprint two, and be more efficient with. As an individual I could better deal with frustrating issues. I got quickly discouraged by major issues that I could not solve, most notably with our SSL errors. My inability to switch tasks held me back from one of my sprint goals, because I was determined to solve an issue that I did not have all the tools to solve. I could also better document my work, as going into this retrospective I realize that outside of completed issues there is very little documentation of what I had done. 

The apprenticeship pattern that best describes my work in this sprint is Confront Your Ignorance. This fit because the work done with the staging and deployment server is something entirely foreign to me. To be able to approach the work, I had to swallow my pride and confront that I know nothing about the topic. And to improve that I did research throughout the sprint to better understand how to make progress. Reading this pattern allowed me to reconceptualize my lack of knowledge into an opportunity.

My tasks:
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/6
This was my first task in the sprint. I installed docker and docker-compose on the server, and got Thea’s Pantry running on our server. I have since tweaked our compose file and have been working on getting the back-end and front-end to connect on the server.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/16
Most of my sprint was spent tackling the issue of SSL certifications for our server. I made progress in getting a self-signed certificate to bind to the IP, but I could not access the index file to allow the front-end to work with the volumes used for the nginx config and certs.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/4
Here I made a minor contribution in establishing how we should go about implementing CI/CD, I researched how we could make it work and presented it in class. In the future I plan to implement a Python script to aid Andrew in this task.

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.

Hoo boy, where do I even begin with my experience for the Sprint…

If I am to be honest, I felt like I didn’t contribute anything to this current sprint. At every angle I either was either unable to receive a task to do, or when I was, I failed to meet said task or it was taken over by someone else.

Do not get me wrong, I don’t want to blame my teammates at all, in fact, I feel as though my teammates have been quite supportive. But at times, I felt like our communication and divvying of workloads could be a bit better. I also want to admit, because of my other courses, I have been scrounging for time for working on this one, so whenever I have had a task, I’m unable to put a solid dent into it.

If I had work to show, I would absolutely show it here. But in all honesty, most of what I’ve done has just been helping others whose work I am unsure of as to where it is on GitLab, or if it has even been pushed yet. I’m aware that you have been pushing us to use all the features it contained, but we have yet to do so. The one thing I can say I’ve done and show is setting up an issue board for me and Jaylon on the Frontend, which I have been the only one to utilize thus far: https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/frontend/-/boards

The other few tasks I was given, were as follows, and the reasons I wasn’t/didn’t do them is also listed.

• Create a Mock-up app for the scanner: Project was taken over completely by Jaylon.
• Implement a camera view into the web app: Also taken over completely by Jaylon.
• Download and inspect a MongoDB by OpenFoodFacts (https://world.openfoodfacts.org/files/api-documentation.html): Rendered useless by Marlon, who found something better as I was in the process of de-compiling the DB.
• Creating a README, and verifying our licenses: Small tasks that I honestly have no excuse as for why I haven’t done them. I really should at some point, but I’ve bee so focused on more important homework with due dates.

That last part is absolutely a major reason I feel lost, not only just because there’s a lack of communication and task distribution, but the lack of due dates for things makes me have no sense of urgency nor motivation, which is hard to generate for someone such as me with ADHD. Its no excuse of course, but it is absolutely a factor at play.

If I were to choose a pattern in specific from Apprenticeship Patterns, I would likely choose “Find Mentors” from Chapter 4. It discusses going down avenues not knowing where to turn to or what to do, even though it is a path others are treading. I feel as though this is a perfect summary of my situation during this sprint, and is something I will keep in mind going forwards in the next. Perhaps I should work a bit more closely with my Professor, and see if he has knowledge to imbue or assistance to give. I have already seem to have found a niche for this next sprint, with the design of our web app, so hopefully that ends up going much more swell that this week did.

If I were to say something positive about my team, however, I feel like when we meet up and work together, we are very strong and capable. It’s clear to me that everyone cares not only about our project, but each other. I have felt bad every time I end up late or absent from courses, as I feel like I am unable to contribute to this positive work effort our team is pushing. Hopefully in the future I can improve and build upon this, and make our teamwork even stronger.

Here’s hoping that the next Sprint goes a lot better!

From the blog CS@Worcester – You're Telling Me A Shrimp Wrote This Code?! by tempurashrimple and used with permission of the author. All other rights reserved by the author.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/merge_requests/49

This is the link showing merged changes into main branch after testing. During this sprint, our team collaboration was strong, with regular meetings during class checking on our progress and open communication that helped us stay aligned. Additionally, our task management system in GitLab was highly effective, helping us track progress and ensure that every team member had a clear understanding of their responsibilities. Another success was our ability to quickly adapt to challenges. When any of my teammates encountered any problems, we worked together to identify solutions and implement fixes efficiently. This adaptability was important in maintaining our project’s momentum and meeting our sprint goals. Despite the successes, there were areas where I struggled. One significant challenge was time. Some tasks took longer than anticipated due to unforeseen problems, particularly when dealing with the display of the First Entry Date in the frontend. I made some changes in the GuestInfoComponent.vue and at first it wasn’t displaying the entry date. With more research, I figured I also had to make changes in the VerifyPage.vue file. With these changes, my Date of first Entry was displayed after making my changes. Looking ahead, there are several ways our team can improve. One is better estimation of task complexity, where tasks can be broken down further and allocate time for unexpected challenges. Reflecting on my own contributions, there are several areas where I can improve. One is time management. Allocating more time for testing will help ensure deadlines are met more comfortably. This I would say is something I am going to do better at in the next sprint, as I believe it will help enhance my own skills as a developer.

The Apprenticeship Pattern I chose is “Expose your Ignorance” pattern which encourages developers to openly acknowledge what they don’t know and actively seek knowledge. Instead of pretending to understand everything, developers should ask questions, collaborate with teammates, and use resources to expand their expertise. I chose this pattern because it closely aligns with my experience during this sprint. When working on merging my work to GitLab after I had completed my issue, I struggled with this and came across many blocks. Instead of immediately asking for guidance, I spent too much time doing it on my own. Eventually, when I reached out to a teammate, I realized how quickly I could have resolved the issue with just a simple discussion. This experience reinforced the importance of embracing learning opportunities rather than trying to figure everything out alone. Had I fully embraced this pattern from the beginning, I would have immediately sought help. This approach would have saved me valuable time and reduced frustration. Moving forward, I plan to be more open about my knowledge gaps, actively seek advice, and continue improving my problem-solving efficiency. This sprint was a valuable learning experience that highlighted both our team’s strengths and areas for improvement. While our collaboration and adaptability were commendable, we also identified opportunities to enhance efficiency and communication. On a personal level, recognizing the importance of seeking knowledge earlier will help me grow as a developer. By implementing these improvements, both individually and as a team, we can ensure even greater success in future sprints. I look forward to working on the next sprint and implementing more changes that will make this sprint easier.

From the blog CS@Worcester – Lynn'sBlogs by lynnnsubuga and used with permission of the author. All other rights reserved by the author.

GitLab Activity

Install npm JWT Library and handle validation on Mock FE/BE issue – created a file called checkRole.js that as of moment takes a token and decodes it, however since Keycloak is not configured yet with the backend, checkRole.js is still not setup for the verification of tokens.

Reflection on What Worked Well

This sprint, I found that my ability to collaborate effectively with my team improved. We established a structured workflow using GitLab issues and merge requests, ensuring everyone was aligned. Team meetings and project reviews were also particularly helpful in maintaining quality and catching potential issues early. Additionally, I felt more comfortable with our tech stack, which allowed me to contribute more efficiently to the project.

Reflection on What Didn’t Work Well

One of the biggest challenges during this sprint was time management and managing expectations of fellow team members. Balancing multiple tasks while delivering high-quality work proved difficult, especially when unexpected issues arose. There were also moments when communication gaps led to duplicated efforts or confusion regarding task ownership.

Additionally, an unexpected bug related to the jsonwebtoken library took longer to resolve than anticipated, impacting our overall sprint velocity. I underestimated the complexity of debugging the issue, and this resulted in delays. Moving forward, I want to improve my debugging strategies by breaking down issues systematically and identifying potential causes earlier in the process.

Another challenge was that some tasks took longer than expected due to unclear requirements. There were times when I started working on a feature only to realize later that I had misunderstood part of the implementation. This led to rework and inefficiencies that could have been avoided with better clarification upfront.

Reflection on Changes to Improve as a Team

To improve as a team, we need to refine our communication and task allocation strategies. One possible improvement is assigning issues to members with clear deadlines and deliverables. This would help eliminate the need to check in constantly about each other’s progress and give everyone enough space to focus on their designated tasks.

Additionally, we could establish clearer guidelines on documentation and issue tracking. Proper documentation would minimize misunderstandings and ensure that we have a reference point if any team member forgets certain project details. This could be as simple as maintaining a shared document with important technical decisions, dependencies, and any issues we encounter.

Reflection on Changes to Improve as an Individual

On a personal level, I need to deepen my knowledge of the technologies we are using and strengthen my overall web development skills. Additionally, I must improve my time management and prioritization strategies to ensure more efficient task completion. Allocating time for debugging and testing earlier in the sprint would help reduce last-minute stress and improve the stability of our work. I also plan to dedicate time outside of sprint tasks to learn best practices and gain a more comprehensive understanding of our tech stack. Finally, I recognize the importance of seeking help sooner when I encounter challenges, as doing so will allow me to work more efficiently and avoid unnecessary delays.

Apprenticeship Pattern: “Be the Worst”

Summary of the Pattern

The “Be the Worst” pattern suggests deliberately placing yourself in an environment where you are the least experienced or skilled person. By doing so, you expose yourself to opportunities for rapid learning and growth by observing and working with more skilled individuals. While this can be uncomfortable, it forces you to improve and challenge yourself continuously.

Why I Selected This Pattern

I chose this pattern because, during this sprint, I often felt like I was struggling to keep up with some of my teammates who had more experience with certain technologies. Instead of being discouraged, I realized that this was an opportunity to learn from them and elevate my own skills. Their feedback and insights helped me refine my practices and problem-solving approach.

How This Pattern Could Have Changed My Behavior

Had I fully embraced this pattern earlier in the sprint, I would have proactively sought out mentorship and learning opportunities rather than hesitating to ask questions. Additionally, I would have taken more initiative in tackling challenging tasks instead of sticking to what I was comfortable with. Moving forward, I plan to embrace this mindset and view my inexperience as an advantage rather than a limitation.

From the blog CS@Worcester – The Bits & Bytes Universe by skarkonan and used with permission of the author. All other rights reserved by the author.