Mini project PPT
Mini project PPT, review by review.
A third-year mini project (the minor project at some colleges) is reviewed two or three times by a panel, and each review wants a different deck. This page covers what usually goes in each one and how to write the slides. Where your department’s format sheet differs, follow the format sheet.
What each review usually asks for
Colleges name and split the reviews differently (zeroth, first, second, final), so check your format sheet. A common pattern:
| Review | Slides | What the panel wants to know |
|---|---|---|
| First review (zeroth at some colleges) | Title and guide, abstract, problem statement, objectives, literature survey with the gap you found, proposed method, block diagram, hardware and software requirements, work plan, references | Is the scope small enough to finish this semester, and have you read the work before yours? |
| Second review | A one-slide recap, architecture, modules and who owns each, design diagrams (use case, ER, flow), what is built so far with screenshots, plan for the rest | How much works, and does each member know their own module? |
| Final review | Recap, implementation, testing with test cases and results, results as charts, comparison with an existing method, demo, conclusion and future scope, references | Does it work, and can you explain where each number came from? |
Some departments also want slides for the institute’s vision and mission, programme and course outcomes, or a mapping to the UN Sustainable Development Goals. Put those where your format sheet puts them. The full first-review deck is on the zeroth review page.
Slide by slide
- Abstract: what the project does, how, and the result you expect, in about five lines. Panels often read only this slide closely.
- Problem statement: one or two sentences that name the user and the gap. If you can’t write it that short, the scope is probably too wide.
- Objectives: three or four, each one you can check off at the final review. “Detect potholes from dashcam video” can be checked; “improve road safety” can’t.
- Literature survey: a table with the paper, its method, its result and its limitation. The limitation column is where your gap comes from.
- Block diagram: the parts of the system and the data moving between them. Draw it once and reuse it in every review so the panel sees the same system grow.
- Work plan: weeks against tasks, with names. Keep it realistic, because the second review checks it.
- Results: charts from your actual test runs, with the dataset and the metric named. Avoid screenshots of console output.
- Future scope: what you would do with another semester, specific to your project.
Before the review
- Every member should be able to explain the block diagram, not only the one who drew it.
- Bring the demo running on a laptop, with a recorded video in case the venue Wi-Fi fails.
- Expect “why not use the existing method?” and “how did you get this number?”, and have the answer on a slide or in the repo.
- Keep the same title, team and guide details on every review’s deck.
Draft it from your repo or notes
Paste your project repo, then add your abstract, paper notes and results on the next page, with the headings your format sheet wants. devreport writes the review deck from them, with charts from your own results. You get a PDF, and a PowerPoint file if you want one (2 more credits). 15 free credits on sign‑up (enough for your first deck). No card.
Questions
How many slides should a mini project PPT have?
Most review decks run ten to fifteen slides, but follow your department’s format sheet if it gives a number. A first review needs fewer slides than the final one, which has results and a demo to show.
How is a mini project review different from a final-year review?
The structure is much the same. A mini project has a smaller scope and a shorter timeline, so panels look harder at whether you can finish in the semester. For final-year decks, see the final-year project page.
Our department has its own PPT template. Can I use it?
Yes. Upload the department’s .pptx when you start and the deck takes its colours, fonts and logo. List the slide headings your format sheet asks for in your notes and the deck follows them in that order.
We haven’t written any code yet. Can it make the first review deck?
Yes. The first review is about the plan, so a repo is optional. Give it your abstract, your notes on the papers you read and your idea for the system, and it writes the deck from those.
Will it write the literature survey for us?
It summarises and compares the papers you give it notes on. It does not invent papers, authors or citations, so a survey slide only lists papers you added.
What does it cost?
New accounts get 15 free credits. A deck costs 10 credits and each change you ask for afterwards costs 1; editing text on the page yourself and switching themes are free. A build that fails gives its credits back.
Related
Review coming up? Start from your repo.
Your code, results and notes in; a review deck with your own charts out.
Paste my repo