Sprint 3

[CanadianMaple-Syrup]

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

Sprint 3 Retrospective

Sprint: 3
Dates: 2026-02-09 → 2026-02-22
Participants: @benjaminsunliu @JenLys @CanadianMaple-Syrup @Strange4 @Marian-Hristov @Vinuyans @SaraH6734 @SacciadisG @YehJordan @DallaliRim @sasha-klnd

Welcome to the Sprint 3 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

[CanadianMaple-Syrup]

Sprint Goal

• The goal of the sprint was to complete building-to-building navigation
• We also had the goal of fixing the comments from the professor

✅ What went well

• We managed to fix the comments made by the professor
• We had very thorough PR reviews
• Whenever a feature was complete, we pushed the associated tests as well

⚠️ What could be improved

• When planning the sprints we didn't consider the time of the semester it is (Midterm season)
• When we aren't able to work on something because of external factors, we didn't always communicate it right away
• We weren't anywhere near to completion of the sprint

💡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"
• When planning the next sprint, take into account the surrounding context for everyone

[SacciadisG]

Sprint Goal

• The goal of the sprint was to complete building-to-building navigation
• We also had the goal of fixing the comments from the professor

✅ What went well

• Comments by professor have been addressed
• Communication is still honest amongst the team, even when it comes to admitting we're delayed.

⚠️ What could be improved

• Didn't consider the time of year when assigning sprint items
• We fell way behind our predictions, task timeline-wise

💡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"
• When planning the next sprint, take into account the surrounding context for everyone

[YehJordan]

🎯 Sprint Goal

This sprint's goal was to complete tasks related to Epic 2 and finish any task that was incomplete from the previous sprint.
My personal goal was to finish the "Highlight current building" feature as well as the task about selecting your current building for the navigation.

---

✅ What Went Well

The incomplete feature from the previous sprint was properly accomplished and communication was good during its conception.
For every PR made, communication with the concerned individuals was great and good feedback was shared with everyone.

---

⚠️ What Could Be Improved

Everyone was particularly busy with midterms and assignments. A lot of deadlines were due in the 2 weeks of this sprint. Our velocity this sprint was horrible and it shows with the burndown chart

---

💡 Ideas & Action Items

There is reading week coming up, and it would be wise to increase our productivity with the extra time on our hands.
A lot of us were really quiet during the sprint (although it is probably due to the workload for the past 2 weeks). It would be great to keep communication levels high by messaging on the discord if you cannot complete your task or if you are waiting for something or someone.

[DallaliRim]

Sprint Goal

• The goal of the sprint was to complete the outdoor navigation (building to building)

✅ What went well

• We started refactoring and addressing the technical debt
• Communication issues from previous sprint have improved during this sprint

⚠️ What could be improved

• We were very late with many user stories still left incomplete
• we failed to consider the midterm rush in the sprint planning

💡Ideas & Action Items

• keep in mind other responsibilities during sprint planning

[benjaminsunliu]

🎯 Sprint Goal

The main goal of this sprint was to complete the building-to-building outdoor navigation feature which included including route display and transportation modes. We also wanted start refactoring parts of the codebase to improve long-term maintainability and resolve SonarQube issues. We also aimed to address and fix the feedback received from the professor to ensure better alignment with the project requirements and improve overall quality.

---

✅ What Went Well

• Tests were pushed alongside completed features instead of afterwards.
• Communication during code reviews was effective and responsive.
• We talked about better user flows & improvements of the codebase.

---

⚠️ What Could Be Improved

• Planning was somewhat ambiguous, which led to reduced productivity.

---

💡 Ideas & Action Items

• We should continue having the sprint plan channel in the discord like it was done for the first 2 sprints.
• We should have some kind of order of how issues should be completed, and which can be done concurrently.
• Have more specific timelines for the issues on the roadmap of the GitHub projects.

[sasha-klnd]

Sprint Goal

The goal of the sprint was to implement features related to navigation between buildings on campus, including indicating when a user is inside a building.

✅ What went well

The level of communication and coordination between team members definitely improved compared to last sprint.

⚠️ What could be improved

We fell very short of completing the planned tasks because everyone's schedules became much busier due to midterms and projects in other courses. There's not much that could be done about everyone having less time to work on the project, but maybe we should have accounted for this during the sprint planning and aimed for a smaller, more achievable pool of tasks.

💡Ideas & Action Items

I agree with Benjamin's idea of continuing to use a sprint plan channel in the Discord server. I also agree with the general sentiment from all other team members that we should be more attentive to everyone's schedules during sprint planning to make our sprint goals more feasible.

[SaraH6734]

🎯 Sprint Goal

The goal of this sprint was to do Epic 2 tasks and refactor the existing tests to improve reliability and maintainability.

✅ What Went Well

Team communication improved compared to previous sprints.

⚠️ What Could Be Improved

Due to assignments and midterms, not all planned work was completed.

💡 Ideas & Action Items

Plan future sprints while accounting for other duties and commitments we may have.

[Vinuyans]

Sprint Goal

The goal of the sprint was to implement features detailed in Epic 2 as well as finish any missing ones from Epic 1

✅ What went well

Communication has been signigicantly improved amongst team members

⚠️ What could be improved

The entire team was overwhelmed with work from across different classes and so we were not able to accomplish everything we set out to for this sprint.

💡Ideas & Action Items

Plan sprints taking into consideration all the other classes we have at the same time. Assign work depending on who has what (people taking class A will have a lighter work load when there are things due)

[Marian-Hristov]

🎯 Sprint Goal

The goal of the sprint was to implement features from Epic 2 as well as some missing from Epic 1. We had feedback to address from the teacher & PO. My personal task was start on refactoring.

✅ What Went Well

Communication between the team members is still strong and very smooth.

---

⚠️ What Could Be Improved

All the team members were swarmed with tasks from the other classes such as assignments and midterms and thus we were less focus on this project.

---

💡 Ideas & Action Items

We need to plan sprints while keeping in mind that we will be busy with other work outside of this project. Luckily, we have the reading week that is upcoming so we will have to take advantage of that period to do more work and regain traction.

---

[Strange4]

🎯 Sprint Goal

The goal for this sprint was to continue implementing new features and furthering the completion of the app. The structure and planing were all there to be able to do.

---

✅ What Went Well

Communication within the team.

---

⚠️ What Could Be Improved

Quite a few of the team members are in the same classes, so assignment due dates align and the progress stagnates since no one has time to work on the project.

---

💡 Ideas & Action Items

Try to complete some work in advance from next sprints in order to have a buffer when assignment due dates align.

[JenLys]

🎯 Sprint Goal

Implement the outdoor building to building navigation and correct features from Sprint 2. Namely, address the current building visualization.

✅ What Went Well

For this sprint the UI team expanded to include two people. I find that this greatly helped with getting more ideas and delivering refactored mockups on time. Moreover, as always, each team member communicates and completes their assigned tasks.

⚠️ What Could Be Improved

Each one of us had midterms and multiple project submissions. Due to this, our team did not deliver according to our initial expectation. What could be improved: it seems that ui mockups and ui logic (such as highlights, overlays, etc) are not followed at times. Perhaps the information is hard to find? Perhaps some elements need to be changed? Now that the UI team is bigger, it would be appreciated if teammates communicated their concerns or asked questions instead of creating a product that doesn't align with our ui/ux deliverables. Because of this, there has been a lot of back and forth and the devs had to do double-work to re-implement the proper features. *Not putting blame on anyone here, just expressing some observations in the hopes of fixing this and improving our methodologies :)

💡 Ideas & Action Items

See the last point above