Final Year Project Presentation and Defence Best Practices

Chapter 1 · Practice 3 of 3

Tell one clear story from problem to result

From Know what each evaluation assesses

Why it matters

A good project presentation is a story with a simple arc:

  1. The problem: who has it and why it matters (one slide).
  2. What exists and the gap: briefly (one slide).
  3. What you built: objectives, architecture, key decisions.
  4. The demo: the system solving the problem.
  5. Evidence: testing and results against objectives.
  6. What you learned: limitations and future work.

The University of Sheffield's guide for undergraduate project vivas suggests a similar overview: aims, why the work matters, the approach at a broad level, your personal contribution in a group, and what you achieved. Keep week-by-week history out of it; examiners want to understand the result, not every step.

Do

  • Open with the problem, not the technology stack
  • End with results against objectives and limitations

Avoid

  • A chronological diary of the year