Project Roadmap¶

Toodle is being developed incrementally across the project milestones. Each sprint builds on the previous one, beginning with the project foundation before moving toward complete tutor-management workflows.

Roadmap¶

Milestone	Date	Main Focus	Status
Sprint 1	25 August 2026	Project foundation, documentation, database, authentication and initial system design	🟡 Current
Sprint 2	15 September 2026	Core tutor-management features, API integration and testing	⬜ Planned
Sprint 3	29 September 2026	Feature completion, user feedback, testing and refinement	⬜ Planned
Final Submission	11 October 2026	Integration, deployment, performance, documentation and final release	⬜ Planned

Sprint 1 — Foundation¶

Sprint 1 establishes the technical and organisational foundation of Toodle.

Key work includes:

setting up separate frontend, backend and documentation repositories;
deploying the documentation site;
designing the PostgreSQL database;
establishing authentication and user roles;
defining the system architecture and API structure;
documenting the development and Git methodologies;
establishing Trello as the project work tracker; and
creating the initial UI and development plan.

Current Progress¶

The following foundations are already available:

the documentation site is deployed;
the application is available online;
Google authentication through Auth0 is working;
authenticated users can be recognised by role;
the PostgreSQL database has been established; and
the team is using Trello to manage sprint work.

Sprint 2 — Core Workflows¶

Sprint 2 will focus on implementing and connecting the main tutor-management workflows.

Planned work includes:

managing courses and tutors;
tutor allocation;
allocation constraint checking;
tutor availability;
timesheet workflows;
excusals;
overflow work;
frontend and API integration; and
automated testing.

Sprint 3 will focus on completing features and improving the quality of the system.

Planned work includes:

completing remaining Intermediate and Advanced features;
stakeholder and user feedback;
usability improvements;
additional automated testing;
bug fixing;
performance improvements; and
documentation updates.

Final Submission — Production Readiness¶

The final phase will prepare Toodle for submission as a complete system.

This includes:

final frontend, API and database integration;
production deployment;
security and access-control review;
performance testing;
final documentation;
resolving outstanding bugs; and
creating the final project release.

Why This Order?¶

The roadmap prioritises foundation before features.

Authentication, database design, architecture and development processes are established first because later functionality depends on them. Core tutor-management workflows can then be implemented on a stable foundation, leaving the later sprints for testing, feedback and refinement rather than major architectural changes.