Project Roadmap¶
Toodle was developed by Infinite Loopers using an adapted Scrum methodology across four sprints. Each sprint built on the work completed in the previous one, allowing the team to progress from initial planning and system design to a fully integrated tutor management application.
The development process focused on establishing a reliable foundation, implementing the main tutoring workflows, gathering feedback, and refining the system for final submission.
Project Milestones¶
| Milestone | Deadline | Main Focus | Status |
|---|---|---|---|
| Sprint 1 | 25 August 2026 | Project planning, system architecture, initial designs and setup | Completed |
| Sprint 2 | 15 September 2026 | Core tutor management functionality and frontend/backend integration | Completed |
| Sprint 3 | 29 September 2026 | Intermediate and advanced features, user testing, feedback and improvements | Completed |
| Sprint 4 / Final Submission | 11 October 2026 | Final integration, testing, documentation and release preparation | Completed |
Sprint 1 — Planning and Foundation¶
Deadline: 25 August 2026
The first sprint focused on establishing the technical and organisational foundation of Toodle.
The team:
- Analysed the project requirements and planned the initial system.
- Established the frontend, backend and documentation repositories.
- Designed the initial user interfaces, database and system architecture.
- Set up authentication and the development environment.
- Established Trello for sprint planning and task tracking.
- Defined the team's Git workflow and development methodology.
By the end of the sprint, the team had established the foundation required for implementing Toodle's main functionality.
Sprint 2 — Core Development¶
Deadline: 15 September 2026
Sprint 2 focused on developing the essential tutor management functionality and connecting the frontend with the backend.
The team implemented:
- Course and tutor management.
- Tutor applications and allocations.
- Availability and allocation validation.
- Timesheet management.
- Excusal requests and volunteering opportunities.
- Frontend and API integration.
- Initial automated testing and debugging.
This sprint established the core workflows needed for students, tutors and academic staff to interact with Toodle.
Sprint 3 — Feature Development and Feedback¶
Deadline: 29 September 2026
Sprint 3 focused on extending the application's functionality and improving the overall user experience.
The team:
- Developed additional intermediate and advanced features, including course-scoped Lecturer access and calendar subscriptions.
- Expanded allocation and scheduling functionality with transactional eligibility checks and retained allocation history.
- Conducted user feedback sessions with students familiar with CSAM tutoring processes.
- Collected feedback through forms and in-app problem reports.
- Recorded and prioritised identified issues using Jira.
- Improved usability, navigation and responsiveness.
- Expanded automated testing and documentation.
The feedback process helped the team identify areas requiring improvement and informed further refinements.
Sprint 4 — Refinement and Finalisation¶
Deadline: 11 October 2026
The final sprint focused on strengthening the completed application, improving consistency across workflows, and preparing Toodle for submission.
Key activities included:
- Completing explainable allocation proposals and saved drafts, session-specific excusals, dated swaps and timesheet review refinements.
- Adding verified staff invitations and access requests, course assignments and a separate staff welcome flow.
- Improving notification email outcomes, automated reminders and date-aware calendars with terms and availability exceptions.
- Addressing outstanding usability and integration issues.
- Reviewing authentication and permissions, including history-preserving account closure and protection against stale sessions.
- Expanding automated and PostgreSQL integrity tests, running quality checks and improving CI runner reliability.
- Improving frontend resource loading through lazy routes, vendor chunks, WebP images and removal of redundant API requests.
- Finalising API and database references, the complete ERD, methodology, testing and anonymised feedback evidence.
- Preparing the integrated system for final submission.
This phase brought together the work completed across the previous sprints and focused on delivering a consistent and reliable application.
Development Progression¶
The team followed a structured development approach in which each sprint built upon the previous one.
Sprint 1 established the foundation, Sprint 2 introduced the core functionality, Sprint 3 expanded the application and incorporated user feedback, and Sprint 4 focused on refinement and finalisation.
This progression allowed Infinite Loopers to manage development incrementally, identify problems throughout implementation, and improve Toodle while maintaining a clear focus on the project requirements.
Project Completion¶
All four development sprints were completed by 11 October 2026, bringing together the implemented features, final refinements, testing and documentation for submission. Detailed verification remains in the relevant technical and testing pages.
Final Project Statistics¶
| Measure | Final recorded value |
|---|---|
| Development sprints | 4 |
| Frontend coverage | 80% |
| Backend coverage | 92% |
| Prisma models | 28 |
| Prisma migrations | 25 |
| Jira issues marked Done | 21 |
| User feedback responses | 21 |
| Application roles | 4 |
Registered /api/v1 endpoints |
117 |
Coverage figures are the reported results documented in Testing Strategy. Jira and feedback totals refer to the anonymised evidence described in User Feedback & Usability.