The project viva decides a healthy chunk of your final-year credits — and it’s the most predictable exam you’ll ever face. Examiners ask the same families of questions every year. Prepare them and the viva becomes a conversation, not an interrogation.
The questions that always come
- “Explain your project in two minutes.” Problem → existing gap → your solution → result. Rehearse this aloud until it’s smooth.
- “Why this technology/method?” Have one honest reason plus one alternative you considered — “we compared X and chose Y because…” lands well.
- “What is YOUR contribution?” Each teammate must own a module completely — code, logic, decisions.
- “What are the limitations / future scope?” Admitting real limitations reads as maturity, not weakness.
- One deep-dive: the examiner will pick a line in your report or a screen in your demo and dig. Know every diagram and claim in your own report — unread reports sink vivas.
Demo-day insurance
- Record a full demo video beforehand — networks and laptops fail at the worst moments, and a video keeps the viva moving.
- Keep screenshots of key outputs in your slides.
- Test on the projector/room setup earlier if at all possible.
What examiners actually reward
Clarity about the problem, honesty about limitations, and evidence you built it (fluent navigation of your own code/report). What they punish: memorised scripts, teammates who can’t answer for “their” module, and claims the demo can’t support.
A strong viva project doubles as your first portfolio piece — write the README as if a recruiter will read it, because one probably will. Picking a project? See final-year project ideas.
Frequently Asked Questions
What questions are asked in a project viva?
Almost always: explain the project briefly, why you chose your technology/method, your individual contribution, limitations and future scope, plus one deep-dive into your report or demo. Preparing these five families covers most vivas.
How long is a project viva?
Typically 15-30 minutes per team including the demo, varying by panel and batch size. The two-minute project summary you open with usually sets the tone for everything after.
What if my demo fails during the viva?
Stay calm and switch to your recorded demo video or screenshots — prepared backups are exactly what examiners expect from a good team. Explain what the demo would show while the backup plays.