Sprint 1 — 19/01/26 - 25/01/26
This document describes our first Sprint of TB2 and reflecting on the project structure of TB1
Reflecting on the negatives of TB1
- We met frequently, but conversations weren’t focused on sprint goals or deliverables.
- We didn’t have a clear, coherent vision for the project’s direction.
- Communication and coordination were weak; some teammates struggled to find appropriate tasks.
- We didn’t fully understand our meta-project goal (providing feedback to TI on the development process).
How to succeed in TB2
- Use the correct channels — the Client Liaison handles communications with the client.
- Set clear deadlines, especially when others are blocked by your work.
- Appoint a Project Manager to structure meetings and hold us accountable.
- Hold weekly standups (Friday/Monday) to review progress and plan the next week.
Weekly agenda
- Clarify with the client what feedback they want from us (crucial for our project).
- Talal & Henry: investigate 3D-printed mounts for radar and camera to reduce data-collection errors.
- Henry (PM): ensure meetings have an agenda and structure.
- Talal: write meeting notes, upload to Docusaurus, and organise the repository.
- Dan: replace the older visualiser and implement a camera tab/overlay on the TI Industrial Visualizer.
- Alina: continue radar data collection and coordinate with the ML team on required data format.
- Tom: combine micro-Doppler capture approach with Alina’s pipeline to find the optimal solution.
- Michal: explore ML with Tom (classification) and assist with 3D printing.
This week’s sessions
- Entire Team: Meeting with mentor Jack — Tuesday 2pm
- Entire Team: Data collection session — Friday
- Entire Team: Meeting with Sarah — Thursday