Final Year Project Presentation and Defence Best Practices

What this best practices guide is

A guide to showing your final year project at its best in the mid evaluation, the final presentation and the viva or defence. It covers what each evaluation looks for, slides that support you, a live demo with a backup plan, answering questions honestly, explaining your own code and design decisions, handling "why didn't you use X", and presenting as a team.

It has 7 chapters and 23 practices, each with why it matters, what to do and what to avoid. For final year and capstone students in computing.

Chapter by chapter

1. Know what each evaluation assesses (3 practices)

Mid evaluations, final presentations and vivas look for different things. Read the rules and the marking form first, then shape your presentation around them.

2. Build slides that support you (3 practices)

Slides should help the panel follow you, not replace what you say. Keep them simple, visual and timed.

3. Give a live demo that does not break (4 practices)

The demo is the most convincing part of the defence and the most fragile. Script it, control the environment, keep a backup video and know how to recover.

4. Answer examiner questions honestly (3 practices)

Questions are how examiners find out what you understand. Listen carefully, take a moment, answer what was asked and be honest about what you do not know.

5. Explain your own code and decisions (4 practices)

Panels increasingly ask students to open the code and explain it. Know your parts deeply, the whole system broadly, and be ready to justify your choices.

6. Present as a team (3 practices)

In a group defence, the panel judges both the team and each member. Split the presentation by ownership, hand over smoothly and support each other during questions.

7. Rehearse, prepare the day and follow up (3 practices)

A mock defence, a checklist for the day and acting on feedback afterwards turn a stressful hour into a routine you have already practised.

How it works on Sefism

The guide reads like a short course: a syllabus, then one chapter per page in a focused reader, with a quiz at the end of each chapter for members. Every chapter is open to everyone.

Every claim is checked against the sources listed on the page (5 cited).