Sprint 2

[benjaminsunliu]

This is the retro board for Sprint 2. All retrospectives and discussions should be posted here

Sprint 2 Retrospective

Sprint: 2
Dates: 2026-01-26 → 2026-02-08
Participants: @benjaminsunliu @JenLys @CanadianMaple-Syrup @Strange4 @Marian-Hristov @Vinuyans @SaraH6734 @SacciadisG @YehJordan @DallaliRim @sasha-klnd

Welcome to the Sprint 2 retrospective.
The goal is to reflect on what went well, what didn’t, and identify concrete improvements for the next sprint.

---

📌 How to Participate

• Add one comment per idea under the relevant section
• Use 👍 reactions to vote on comments you agree with
• Top-voted items will be reviewed and converted into GitHub Issues

---

🎯 Sprint Goal

What was the intended goal of this sprint?

---

✅ What Went Well

What worked well this sprint? What should we keep doing?

---

⚠️ What Could Be Improved

What didn’t go well? What caused friction or delays?

---

💡 Ideas & Action Items

Concrete, actionable improvements for next sprint.

---

🧩 Action Items

Action	Owner	Due

---

⏭️ Next Steps

• Top-voted items will be converted into GitHub Issues
• Action items will be added to the next sprint backlog

[DallaliRim]

The goal of Sprint 1 was to complete the user stories in epic 1. These included implementing the SGW and Loyola campus maps, highlight the campus buildings, display the building's relevant informations, highlight the current building.

---

✅ What Went Well

• with a new dedicated discord channel for the PR reviews and by tagging people, we got really good PR reviews from several team members
• Some features showed how we can use teamwork to fix bugs and find solutions efficiently

---

⚠️ What Could Be Improved

• some team members do not communicate with the rest of the team, which introduced confusion and delays.
• some team members were not proactive during this sprint in taking tasks and helping their peers

---

💡 Ideas & Action Items

• Have an "updates" channel where team members can post their progress in so that it does not get drowned in the discussion messages

[CanadianMaple-Syrup]

Sprint Goal

• The goal of the sprint was to setup the back bone of our application, which is a usable map and buildings that can be interacted with
• We also had the goal of setting up the testing frameworks

✅ What went well

• We had great communication during PR reviews. We would point out refactoring opportunities and any mistakes/bugs that were found, and we would also help come up with solutions for problems (like an IOS crash that didn't happen on android)
• A majority of the team would accomplish their tasks ahead of time to relieve the stress/pressure of rushing at the end (some exceptions like retrospective and implementing PO feedback can only be finished at the end)

⚠️ What could be improved

• We've gotten a lot better at responding to PR reviews; however, we still sometimes forget to @ the people we want to review, or say we will review and then forget to
• We decided to completely separate testing from coding features which has ended up with us rushing to test our code at the end. From now on we can have implementers also write unit tests when possible.
• Some of us waited until the end to ask for help or clarifications on what to do, which lead to a rush to complete tasks on the last day

💡Ideas & Action Items

• Even if you haven't done any work on the project, you should still look in on the chat every day so that you know what is going on. And possibly send a "I'm still alive message"
• Enforce testing on every feature PR from now on to save on time later, even if it is annoying
• If we haven't heard from someone in a while, we should continuously try to get into contact with them so that we can have some sort of update

[YehJordan]

🎯 Sprint Goal

What was the intended goal of this sprint?
The intended goal of this sprint was to finish setting up the CI/CD pipeline with SonarQube and to work and finish the tasks related to Epic 1. My task specifically was to work on the burndown charts and to work on the closest building feature.

---

✅ What Went Well

What worked well this sprint? What should we keep doing?

The flow of delivered work was very good. The burndown chart that I was creating showed that we followed the expected line for the majority of the Sprint, meaning that we didn't overestimate or underestimate our work load. All this includes coding, PRs and team discussions.

---

⚠️ What Could Be Improved

What didn’t go well? What caused friction or delays?

We are missing some tests. As suggested by the PO, we should integrate tests alongside the delivered feature together instead of delivering a feature, then assigning someone to make tests.
Furthermore, it seems that our team has misread a core feature we needed to deliver, which was pointed out by the PO near the end of the sprint. Instead of needing to find the closest building to the user, we needed to inform the building the user is in if he is in one. This will require us to refactor the feature and push it to the next Sprint

---

💡 Ideas & Action Items

Concrete, actionable improvements for next sprint.

Track unfinished issues during the next Sprint
Keep communicating with the team and keep in touch whenever called in the Discord channel or through any other means.
Include tests within feature deliveries

---

[JenLys]

🎯 Sprint Goal

The goal of this sprint was to implement the planned features, write unit tests, create future mockups, research System/UI test implementations, and install and run SonarQube.

---

✅ What Went Well

Each person completed their assigned tasks well, reflecting on the Burndown chart (following the expected delivery). Moreover, meetings have been taking place and most teammates are communicating and collaborating on PR reviews.

---

⚠️ What Could Be Improved

We were told to implement a feature to highlight the current building, however during the PO meeting it seemed that the expectations have changed and that now what was required was entirely different: the closest building. We will need more clarifications to understand if we must have both current and closest or replace the current building feature with the closest. I believe that such misunderstandings could've been avoided if more people gave their feedback on the mockups and looked through the requirements. --Another issue was that an implemented feature did not follow the UI design frameworks and the set colour palette, as a result this made the implementation fail colorblind feasability tests, making our app non-accessible.

---

💡 Ideas & Action Items

More mockup feedback, please :))
Could create a #frontend thread for the people working on frontend aspects to communicate
Improve the system for Reviewing PRs by tagging people under a specific PR thread

---

[Vinuyans]

🎯 Sprint Goal

The goal of the sprint was to finish all of Epic 1

NOTE: Myself, @Marian-Hristov and @Strange4 were at a competition and so were not there for the second half of the sprint.

✅ What Went Well
We got better at communicating more frequently on PR and to go into greater detail in them.

⚠️ What Could Be Improved
There is still a lack of communication outside of review in general. We mentioned in the previous retro that we should implement a mini-meeting based on role (frontend/backend) or larger task, but this was not done this sprint, as far as I know.

💡 Ideas & Action Items

• Implement smaller team meetings

[SacciadisG]

🎯 Sprint Goal

The goal of the sprint was to finish all of Epic 1

✅ What Went Well
Improved communication & great splitting of the code reviewing across PRs.
Splitting of coding & documentation seemed fair.

⚠️ What Could Be Improved
Certain elements such as testing were addressed too late & with too few people. In the future, testing should be done by a greater number of people to avoid overbearing workloads.

💡 Ideas & Action Items
Brief team meetings at the start of the next sprint would be ideal, so we could clearly split tasks & avoid delays. There is also a team meeting at the end of the first week of the sprint, which is great, and one at the start would bring everything together and avoid confusion.

[Marian-Hristov]

Notes: Myself, @Vinuyans , and @Strange4 were at a competition for the second half of the sprint there our comments will only pertain to the first half of the sprint.

🎯 Sprint Goal

What was the intended goal of this sprint?
The goal of the sprint was to finish #37

---

✅ What Went Well

• Strong communication
• Deeper and more insightful PR reviews
• Usage of threads for conversations on specific topics that don't involve everyone

---

⚠️ What Could Be Improved

• The order of tasks and the upcoming tasks are very vague which leads to people not knowing what to do when they are available
• Attending all meetings

---

💡 Ideas & Action Items

Concrete, actionable improvements for next sprint.

• Reminders for meetings one day in advance

---

🧩 Action Items

Action	Owner	Due
Set up reminders for meetings	@Strange4	ASAP

[Strange4]

The goal for this sprint was to create the base application that we will be continuing to improve throughout the project as we add more features.
My personal goal for this sprint was to give example of a good the organizational "workflow" of adding more features to the application. From assigning tasks, to reviewing PR's and looking at documentation and everything in between.

---

✅ What Went Well

• PR's reviews were good and insightful! thank you @benjaminsunliu
• The weekly meetings are used well to catch up everyone and make sure that everyone knows what they are doing.
• Assigning tasks worked (until no tasks were assigned)

⚠️ What Could Be Improved

• Make sure that people always know what is next to work on

💡 Ideas & Action Items

Action	Owner	Due
Invite people in each individual team to understand the current state of the app and take issues as their work has finished.	@Strange4 @DallaliRim	By the end of next sprint retro

[sasha-klnd]

🎯 Sprint Goal

The goal of this sprint was to work on features related to Epic 1, allowing the user to explore the campus maps, see which buildings were part of the campus, and view information for each of the buildings.

✅ What Went Well

Most of the team did well on getting their features done quickly so that progress for other team members wasn't slowed down.

⚠️ What Could Be Improved

I was not on top of my work when it came to completing my tasks on time or reviewing PRs, and it forced others to do more work to make up for it. Most other team members agree that poor communication and lack of PR reviews was the main issue with this sprint.

💡 Ideas & Action Items

I think there should be a greater separation of discussion topics in the Discord so that update message, meeting reminders, and general discussion do not all get mixed into the same channels or spread across many different channels, making it difficult to find. Maybe there could be more inter-personal communication through DMs as long as it doesn't make it harder for the rest of the team to keep up with what is happening. I also agree with @Vinuyans about having more frequent smaller team meetings between people working on related tasks or branches.

[benjaminsunliu]

🎯 Sprint Goal

The goal of Sprint 1 was to complete the core features of Epic 1 by building a usable campus map experience (SGW & Loyola), enabling building interaction, displaying building information, and setting up the project’s CI/testing foundations.

---

✅ What Went Well

• PR reviews were detailed and constructive, which helped catch bugs early and encouraged refactoring and better code quality.
• Teamwork was strong when issues arose (e.g. platform-specific bugs like iOS crashes), and multiple members collaborated effectively to find solutions.
• Most tasks were completed on time, and the burndown chart showed a steady and realistic progression throughout the sprint.
• The CI/CD setup and use of tools like Sonar helped establish good quality standards early in the project.

---

⚠️ What Could Be Improved

• Testing was often postponed until the end of the sprint, creating time pressure and uneven workload distribution.
• There was some ambiguity around requirements (e.g. current building vs closest building), which led to rework that could have.
• PR review time and responsiveness could be improved to avoid delays.
• Copilot could be added as a reviewer first to catch first issues before involving the others. I've had to assign copilot myself to the PR's of others

---

💡 Ideas & Action Items

• Add copilot to reviews before adding others.
• More responsiveness.

---

[SaraH6734]

🎯 Sprint Goal

The goal of this sprint was to complete and test Epic 1, which enables users to view campus buildings and access pop-up building information.

✅ What Went Well

Most team members completed their tasks ahead of schedule.

⚠️ What Could Be Improved

Testing was left to the end, leading to a rushed process.

💡 Ideas & Action Items

Start testing earlier in the sprint to avoid the last-minute rush.