Best practices · Students
Final Year Project Presentation and Defence Best Practices
FreeA 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.
Written by Tauseef Fayyaz7 chapters, 23 practicesAbout 18 min23 quiz questionsReviewed 31 October 2026What you will learn
7 chapters · about 18 min
1Know what each evaluation assessesMid evaluations, final presentations and vivas look for different things. Read the rules and the marking form first, then shape your presentation around them.3 practices · 3 min
2Build slides that support youSlides should help the panel follow you, not replace what you say. Keep them simple, visual and timed.3 practices · 2 min
3Give a live demo that does not breakThe 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 practices · 3 min
4Answer examiner questions honestlyQuestions 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.3 practices · 2 min
5Explain your own code and decisionsPanels 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.4 practices · 4 min
6Present as a teamIn 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.3 practices · 2 min
7Rehearse, prepare the day and follow upA mock defence, a checklist for the day and acting on feedback afterwards turn a stressful hour into a routine you have already practised.3 practices · 2 min
About this guide
The presentation and defence are where a year of work is judged in under an hour. Examiners watch the demo, read your slides, ask questions and decide how well you understand what you built. A team that built a good system can still lose marks if the demo crashes, the slides are unreadable or nobody can explain a part of the code. A team with a modest system that presents clearly and answers honestly often does better than it expected.
This guide is about presenting and defending your own work well. It is not about memorising answers. The best defence comes from understanding your project deeply, showing it clearly and being honest about its limits. The chapters follow the order you meet them: knowing what each evaluation assesses, building slides, giving a live demo that survives problems, answering questions, explaining your own code and decisions, presenting as a team, and rehearsing.
The advice draws on published university material: the University of Sheffield's guide to undergraduate project vivas, Sheffield Hallam University's guidance on vivas, the University of Lahore's Islamabad campus FYP guidelines on final presentations, and the FAST School of Computing FYP handbook. Formats differ. Some departments hold a mid evaluation and a final presentation, some an open defence with external examiners, some a short viva with no slides at all. Check your own handbook for timings, panel make-up and marking.
Whether your defence is in Islamabad, Bengaluru, Chittagong or anywhere else, the same habits apply. Each chapter ends with a short quiz.
Common questions
How do I prepare for my final year project defence?
Know what the evaluation assesses, build simple slides that tell the story from problem to result, script and rehearse the demo, record a backup video, and run a full mock defence with people who have read your report. Make sure each member can explain their own code in depth and the rest of the system in outline.
What if my FYP demo fails during the presentation?
Name the problem, try one quick fix, and if it does not work, switch to a backup video of the same version and offer to retry at the end. Never pretend a failed step worked. Panels judge how you handle problems as much as the problem itself.
What questions do examiners ask in an FYP viva?
Common themes are why the problem matters, what already exists, why you chose your design and technologies, how you tested the system, what your results mean, the project's limitations and what you would do next. Many panels also ask members to open the code and explain a specific feature.
Is it okay to say I don't know in a viva?
Yes. University viva guidance, such as Sheffield's, says it is fine to say you do not know and to build on what you do know rather than bluff. Admit it, reason from what you know and say how you would find out.
How many slides should an FYP presentation have?
It depends on your time limit. Roughly one slide per minute of speaking is often comfortable, but rehearse with a timer and cut until you finish with a minute or two to spare, leaving room for the demo and questions.
How should a team divide the final year project presentation?
Give each member the part that matches what they built, with roughly equal time, and let them demo that part. During questions, let the member who built the relevant part answer first.
Sources (5)
Checked against these, last on 31 October 2026.
- Undergraduate Research Project Vivas in Physics: a resource for students, University of Sheffieldsites.google.com/sheffield.ac.uk/undergradphysicsprojectvivas/home
- Vivas: Presentation Skills, Sheffield Hallam University Librarylibguides.shu.ac.uk/presentations/vivas
- General Instructions (Final Year Project), University of Lahore, Islamabad campussites.google.com/view/uol-isb-fyp/guidelines
- BS Final Year Project Handbook 2023 (FAST School of Computing), FAST-NUCESnu.edu.pk/public/downloads/FYP-Handbook-2023.pdf
- ACM Code of Ethics and Professional Conduct, ACMwww.acm.org/code-of-ethics
Related on Sefism
Picked from the other libraries by shared topics.
Roadmaps
See allBest practices
See all- Final Year Project Proposal Best PracticesChoose and scope a final year project, then write a proposal with a clear problem, testable objectives, a short literature review, method, feasibility, timeline and risks.
- Final Year Project Report Best PracticesWrite a final year project report or thesis: chapters, literature review, design, testing and results, IEEE and APA citations, figures, similarity checks and honest AI use.
Checklists
See allCareer questions
See all- Is a UK master's still worth it in 2026?It can be, but the maths has changed. Graduate tech jobs in the UK are harder to find, the Graduate visa drops from two years to 18 months for applications from 1 January 2027, and sponsored jobs have salary floors many junior roles miss. A UK master's is worth it if you want the degree itself, have a realistic plan for sponsorship, and can afford it without crushing debt.
- Should I do a master's abroad or get work experience first?For most software engineers, one to three years of work experience before a master's makes the degree more useful, the application stronger and the job search afterwards easier. Go straight away if you have a clear research goal, a strong scholarship, or a time-limited opportunity. Decide by your goal, not by what classmates are doing.
- How do I improve my English communication for remote and international tech jobs?Focus on the English you actually use at work: short written updates, clear pull request descriptions, explaining your project in two minutes and asking questions in meetings. Practise daily with recordings and writing drafts. For remote roles, clear written English often matters more than a perfect accent.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.
- 1:1 Mentorship
- Fresh Graduate Mentorship
- Career Guidance
Brand deals, promos and partnerships: tauseeffayyaz@gmail.com