Methodology Overview¶
Toodle is developed by a team of five students using an adapted Scrum methodology. Scrum was chosen because the project is built incrementally across several milestones and requires coordination between frontend, backend, database, testing, documentation, and project-planning work.
The team is organised as follows:
| Name | Focus Area | Gitea Username |
|---|---|---|
| Kamogelo | Frontend & Backend Development | 2811548 |
| Tjeding | Backend Development | Tjeding |
| Nkosinathi | Frontend & Backend Development | Nathii.dev |
| Kwezi | Frontend & Backend Development | Kwezi-Mudacumura |
| Mpho | Documentation & Project Planning | Mpho10111 |
The project client and tutor is Zayd Suliman.
Team and Development Approach¶
The team uses an adapted Scrum methodology as a practical structure for planning and tracking work, tailored to the academic timetable and the size of the project. Toodle has several moving parts, so the methodology helps the team coordinate implementation, testing, documentation, planning, and review without treating those activities as separate projects.
The methodology is centred around short planning cycles, clear task ownership, visible progress tracking, Pull Request review, and regular reflection on what needs to change before the next milestone.
How the Methodology Fits Together¶
Toodle's methodology connects planning, implementation, review, and evidence:
- sprint work is planned and tracked through Trello;
- code and documentation changes move through Git branches and Pull Requests;
- relevant quality checks are run before work is merged;
- bugs and improvements are tracked through Jira; and
- meeting, sprint, and stakeholder evidence is kept on Trello rather than duplicated across the documentation site.
The supporting methodology pages describe each part of this process in more detail: