Be ready to open the code and walk through it live

Examiners may ask: "Show me where the reminder is scheduled" or "What happens in the code when two phones edit the same batch?" Prepare so this is easy:

• Have the repository open in your editor before the slot, on the version you submitted.
• Know where the key files are; a short list of "file to feature" helps.
• Use clear names and a tidy structure so navigating is quick.
• Be able to trace one request from the user interface through the API to the database and back.

Practise this: one member names a feature, another finds and explains the code for it within a minute. It is the best possible rehearsal for this part of the defence.