Sprint 2 Summary - SOEN390-ConUNav/SOEN390-Mini-Cap-Project GitHub Wiki
Sprint 2
This sprint focused on implementing feature 1, which displays the map and the locations of the Concordia buildings.
Sprint Review
This sprint started off with a great start. Epic 1 was completed and fully implemented as initially planned. However, many user stories part of Epic 2, regarding the outdoor directions, were not completed and had to be moved to Sprint 3, causing delays to the project timeline. Additionally, the team was too ambitious with the number of user stories initially planned for Sprint 2, as many were moved to Sprint 3. However, part of the user stories for Epics planned for future sprints were implemented, such as Google authentication and linking one's calendar as events. Additionally, the shuttle information was implemented during this sprint. Overall, the takeaway from this sprint is to focus on one Epic, instead of many sub-issues, and to start implementation as soon as the sprint starts.
User Stories Table
| Story ID | Planned USP | Status |
|---|---|---|
| US-1.1 | 3 | DONE |
| US-1.1.2 | 3 | DONE |
| US-1.2.1 | 3 | DONE |
| US-1.2.2 | 3 | DONE |
| US-2.6.1 | 3 | DONE |
| Total | 15 | 15 |
Burndown Chart
Retrospective
Link for the retrospective board: https://www.reetro.app/board/69792c5e6d7e4076342de898/69846c6d7684dc7d94f97c28
What Went Well
- Good communication + efficient meetings: Updates are shared regularly, meetings feel focused, and there’s little wasted time.
- Clear task separation: Work was divided in a way that made progress easier to track and evaluate.
- Team support culture: People helped each other with environment setup, implementation, and mockups; help was accessible and quick when needed.
What Could Be Improved
- Environment setup issues: Team members struggled to get the project running locally (especially around configuration / API keys) since there was no strict guide to follow regarding the setup.
- Documentation is scattered: Setup instructions and common troubleshooting tips are spread out. There is no clear document to refer to regarding the common issues faced.
- GitHub issues lack clarity: Some issues don’t have enough detail, which creates different interpretations and slows implementation.
- Dependency: Some tasks couldn’t start until others finished their parts, which becomes risky close to the sprint deadline.
Action Items for Next Sprint
- Create a single “Project Setup” doc (README / wiki page):
- Step-by-step setup + required versions
- Where to get API keys/config values and where to store them
- Common errors + fixes
- Start implementation earlier in the sprint: Begin work related to implementation in week 1 of the 2-week sprint to leave time for thorough pull requests, merges, and debugging.
- Reduce blockers with earlier integration: Encourage smaller PRs and earlier merges, especially for high-priority work.
- Finish incomplete features: Prioritize closing remaining work before adding too many new items (or re-scope clearly).
Overall Reflection
This sprint had strong potential. The sprint started out with user stories being implemented. However, due to the environment setup issues and scattered documentation, delays were caused, and the planned user stories were not completed as anticipated. Next sprint, it is important to set due dates for user stories to avoid dependency delays for other team members. Additionally, earlier implementation and more frequent integrations will allow the team to deliver more consistently.