Repository navigation
Sprint Summaries
Due: October 6, 2026
Sprint 1 set up the project foundations: the GitHub repository, project board, wiki and README, plus the submitted project proposal and license. We met with our stakeholder, a Concordia civil engineering professor, and got the stakeholder agreement signed. The team wrote the full first round of wiki documentation, covering project work (risks, budget, economic impact, personas, legal, ethics, diversity) and design and development (architecture and class diagrams, infrastructure, naming conventions, testing and CI, security, performance). The Sprint 2 backlog was created as GitHub issues.
Did we accomplish what we planned? Yes. All planned tasks were completed by the October 6 deadline. They are tracked as 22 closed issues (#108 to #129) on the Iteration 1 milestone: 8 setup issues and 14 documentation issues.
What slipped? Nothing slipped from the Sprint 1 plan.
Was anything done early? The GitHub issues were created for Sprint 2 as well as Sprint 1 (#115), so the next sprint's backlog was ready before it started.
Contractor estimate: about 72.5 hours at a junior contractor rate of $50/h CAD, for a total of $3,625. Hours are estimated per task because time was not tracked this sprint.
| Area | Est. hours | Cost |
|---|---|---|
| Project setup and stakeholders (proposal, repo, wiki, README, issues, stakeholder meeting and agreement) | 25.5 | $1,275 |
| Project work documentation (summary, risks, economic, budget, personas, diversity, EULA, legal and ethical) | 24 | $1,200 |
| Design and development documentation (architecture, infrastructure, naming, testing and CI, security, performance) | 23 | $1,150 |
| Total | 72.5 | $3,625 |
Full board: Sprint 1 retrospective
What went well?
- Accountability: when someone committed to a task, they followed through.
- Planning was solid, and the task board was kept up to date.
- Reviewing each other's work worked well.
- Staying aligned through the group chat between meetings.
What went wrong?
- The overall project plan kept being reworked, which delayed getting into code.
- Meetings ran too long and lost focus.
- Roles were not always clear, so people sometimes worked in isolation.
- Too much time went into long email threads with secondary stakeholders.
What improvements will we make?
- Start implementing features at the beginning of the sprint, leaving time to refactor.
- Write tests alongside features instead of at the end.
- Hold shorter, more frequent meetings, and walk through user stories so everyone has context.
- Review PRs within a day, avoid last-minute merges, and pair up on harder tasks.
No GitHub release was created for Sprint 1. Its automatically generated release notes would contain two commits: the initial commit (@Gur-Lal) and the README (@MusmusIRQ). The rest of Sprint 1 was documentation, written on this wiki and tracked as issues on the Iteration 1 milestone.
| Member | Contribution | Issues |
|---|---|---|
| Gur | Created the GitHub repository and project (initial commit); co-wrote the project proposal and license. | #108, #109 |
| Priyesh | Co-wrote the project proposal and license; wrote the Budget and Security pages; created the Sprint 1 and 2 GitHub issues with Ria. | #108, #115, #121, #128 |
| Samuel | Emailed the stakeholder contact; created the Architecture page with the overall architecture and class diagrams; wrote Infrastructure and Tools; led getting the stakeholder agreement filled. | #110, #124, #125 |
| Mustafa | Wrote the README (commit e826472); created the GitHub wiki. | #111, #112 |
| Oussama | Wrote the project summary and the Diversity Statement. | #116, #123 |
| Amanda | Wrote the Risks and Economic Impact pages. | #117, #120 |
| Derek | Wrote User Consent and License Agreement and Legal and Ethical Issues. | #118, #119 |
| Ria | Wrote the Personas and Performance pages; created the Sprint 1 and 2 GitHub issues with Priyesh. | #115, #122, #129 |
| Lucas | Wrote Naming Conventions. | #126 |
| Darcy | Wrote Testing Plan and Continuous Integration. | #127 |
| Everyone | Chose the stakeholder and met with them; got the stakeholder agreement filled. | #113, #114 |