Slide-by-slide format
| # | Slide | Keep it to |
|---|---|---|
| 1 | Title, team, guide, college | — |
| 2 | Introduction | 3 points |
| 3 | Problem statement | 2–3 lines |
| 4 | Objectives | 4–5 points |
| 5 | Literature survey | One comparison table |
| 6 | Proposed system | What is new |
| 7 | Architecture / block diagram | One clear diagram |
| 8 | Modules | One line each |
| 9 | Technology / components | Table with reason |
| 10–11 | Implementation | Screenshots or model photos |
| 12 | Testing and results | Table or graph |
| 13 | Conclusion and future scope | 3 + 2 points |
| 14 | References | Top 5 |
| 15 | Thank you / questions | — |
Which slides for which review
- Review 1 (synopsis): slides 1 to 6 plus timeline
- Review 2 (progress): add architecture, modules, partial implementation and percentage completed
- Final viva: the full deck plus a live demo
Design rules
- One idea per slide, maximum six lines
- 24 pt or larger text, dark text on a light background
- Diagrams redrawn cleanly, not blurry screenshots
- Slide numbers on every slide, examiners refer to them
- 10 minutes of talking for 15 slides, then demo
Who speaks on what
Divide slides among group members by the module each built. Examiners usually ask each member a question on the part they presented.
FAQs
How many slides should a project PPT have?
12 to 15 for the final viva, 8 to 10 for a first review.
Should I put code on slides?
No. Show the architecture and outputs. Keep the code open in your editor in case the examiner asks to see a function.
Does Project Buddyy make project PPTs?
Yes. A 10 to 15 slide PPT built from your report, with speaker notes, is ₹499.
Last reviewed: 2026-10-11. Always follow the format your own department gives you.