Theory
Months of work, a few minutes to show it
After all the building comes the moment to show it: the project presentation to an evaluation panel, usually followed by a viva (their questions). Months of work are judged largely on how well you present them in a short time, so presenting well genuinely matters.
This lesson gives project-focused guidance on preparing and delivering your presentation and handling the viva. (Your soft-skills subject covers presentation skills in depth; here we focus on showing the project.) With clear slides, a working demo, practice, and readiness for questions, you can make your hard work land, rather than fumbling it in the final minutes.
Theory
Preparing: slides and a demo
Prepare two things: slides and a live demo.
Your slides should be clear and uncluttered, telling the story: the problem, your objectives, the design/architecture (use your diagrams), the key features, the technology used, testing, and a conclusion. Do not cram; a few clear slides beat many busy ones. Keep to your time limit.
Your demo shows the working system doing its real job, this is often the most convincing part, seeing it actually work. Crucially, test the demo beforehand and prepare a backup (screenshots or a short recorded video) in case the live demo fails on the day (networks and laptops misbehave under pressure). A working demo, with a safety net, is the heart of a strong presentation.
Formula
Deliver well, and know your own project
On the day: tell a story (problem to solution) rather than listing features; speak clearly and confidently; and show the demo working. Then comes the viva, the panel's questions about your project, your decisions, and your understanding.
The key to the viva is simple: know your own project deeply. You built it, so you should be able to explain WHY you made each choice (the problem, the tech, the design), how it works, and what its limitations are. Panels can tell who truly understands their project and who does not. Practise the whole presentation beforehand, and anticipate questions (why this stack? how does this feature work? what would you improve?). Preparation turns nerves into confidence.
Quiz
What is a wise precaution when preparing to give a live demo of your project to the panel?
- Do not test the demo, to keep it fresh
- Test the demo beforehand and prepare a backup (screenshots or a recorded video) in case the live demo fails on the day
- Refuse to demo the project at all
- Make the slides as crowded as possible
Show the answer
Test the demo beforehand and prepare a backup (screenshots or a recorded video) in case the live demo fails on the day
A wise precaution is to test your demo beforehand and prepare a backup, such as screenshots or a short recorded video, in case the live demo fails on the day (networks, laptops, and deployments can misbehave under pressure). Option A is reckless: not testing invites an embarrassing failure in front of the panel. Option C is wrong: the demo is often the most convincing part of the presentation, showing the system actually working, so you should demo it, just with a safety net. Option D is poor practice: crowded slides confuse; clear, uncluttered slides communicate better. Rehearse the demo, and have a backup ready so a technical hiccup does not sink your presentation.
Think first
Why does knowing your own project deeply matter so much in the viva?
You built the project, so surely you know it. Why stress understanding it deeply for the panel's questions? Then tap.
Show the answer
Because the viva is designed precisely to test whether you genuinely UNDERSTAND your project, or merely assembled it, and panels are skilled at distinguishing the two through questions, so deep understanding is what lets you answer confidently and demonstrate the competence the whole project is meant to prove. It is surprisingly common for students, especially in teams, or when heavily following tutorials, to end up with a working project without fully understanding every decision and mechanism: someone else built that module, or a solution was copied without grasping why it works. The viva exposes this. Panels ask WHY questions ('why did you choose this technology?', 'why is the data structured this way?', 'how does this feature actually work?', 'what would you improve?') because these reveal understanding that a demo cannot: anyone can click through a working app, but only someone who truly understands it can explain the reasoning, the trade-offs, the internal workings, and the limitations. If you know your project deeply, these questions are easy and even enjoyable, you explain your genuine decisions and thinking, and your competence shines through, which is exactly what earns marks and respect. If you do not, you flounder, give vague or wrong answers, or reveal that you cannot account for parts of your own work, which undermines the whole project no matter how good the demo looked. There is also fairness and integrity here: the viva helps confirm that the work is genuinely yours and understood, not just presented. And practically, deep understanding lets you handle unexpected questions and even turn a tough question into a chance to show insight (for example, discussing a limitation thoughtfully). So 'know your own project' is not a trivial reminder; it is the core of viva success, because the viva is fundamentally a test of understanding, and understanding is what a final-year project is supposed to demonstrate. Build it, understand every part of it, and be able to explain your choices, then the viva becomes a showcase rather than a trap. Deep understanding of your own work is what the viva rewards.
Summary
Key takeaways
- The project presentation (and viva) shows your work to an evaluation panel; presenting well matters greatly.
- Prepare clear, uncluttered slides telling the story: problem, objectives, design/architecture (with diagrams), key features, technology, testing, conclusion, kept to time.
- Prepare a live demo of the working system, the most convincing part, and test it beforehand.
- Prepare a demo backup (screenshots or a recorded video) in case the live demo fails on the day.
- Deliver by telling a story (problem to solution), speaking clearly and confidently, and showing the demo.
- For the viva, know your own project deeply, be ready to explain why you made each choice, how it works, and its limitations.
- Memory hook: clear slides, a tested demo with a backup, tell the story, and know your project deeply for the viva.