Stakeholder Interaction¶
The Toodle team meets regularly with the project tutor acting as the client/stakeholder. These meetings are used to clarify requirements, review progress, discuss technical decisions, and identify changes required before each milestone.
Meeting Log¶
| Date | Focus | Key Outcome |
|---|---|---|
| 13 Aug 2026 | Project direction & technical planning | Clarified API, documentation and Sprint 1 expectations |
| Add next meeting | Topic | Outcome |
13 August 2026¶
Purpose: Discuss the initial project direction, technology choices and expectations for Sprint 1.
Discussion¶
- Documentation, organisation and presentation should be treated as important project deliverables.
- The team was encouraged to explore technologies beyond those already familiar to them.
- Firebase/Supabase may be used, but the team must implement its own API endpoints.
- APIs will be exchanged between groups, requiring both external API integration and an API that another group can consume.
- The team should plan for external APIs becoming unavailable or unreliable.
- Database design should be prioritised before significant implementation.
- Sprint 1 should focus heavily on planning and documentation.
- The team was advised to avoid a monorepo structure.
Actions¶
- Separate the frontend, backend and documentation into different repositories.
- Design the database before building dependent functionality.
- Implement a hand-written Express REST API.
- Maintain comprehensive online documentation.
- Investigate suitable external API integration and failure handling.
Evidence¶
Future Meetings¶
For each stakeholder meeting, record:
- date and attendees;
- topics discussed;
- stakeholder feedback;
- decisions made;
- actions assigned; and
- changes made to the project as a result.