PadhaikoAll subjects

Progress Report Submission and Presentation

Project I (ENCT 413)

Open in the Padhaiko app

7.1 Submission of the project I final progress report two weeks prior to the end of the semester

Project I concludes formally with a comprehensive Final Progress Report submitted two weeks prior to the end of the seventh semester, followed by the Final Presentation and Defence. Unlike the 8–15 page Week-3 Proposal (which described future plans), the Progress Report documents what you have actually designed, built, tested, and verified during Phase I, along with your realistic roadmap into Project II.

Definition

Project I Final Progress Report

The Project I Final Progress Report is the culminating technical document of ENCT 413, submitted in department-approved format two weeks before the semester ends. It switches tense from future proposal plans ("will build") to completed Phase I achievements ("designed, implemented, and evaluated"), presenting system design, methodology progress, preliminary experimental or prototype results, limitations encountered, and the concrete Project II work plan.

7.1.1 Standard Chapter Structure of the Project I Progress Report

Always download and verify your department's current Progress Report LaTeX or Word template. Most Institute of Engineering Computer Engineering departments expect the following chapters and front/back matter:

Standard Organization of the Project I Final Progress Report
Report SectionTense & FocusKey Content Expected
Front MatterFormal academic metadataCover page, Certificate of Approval (supervisor + mentor if internship + HOD), Abstract (150–250 words), Acknowledgements, Table of Contents, List of Figures & Tables, Abbreviations
Chapter 1: IntroductionPresent / completed framingRefined background, finalized problem statement, SMART objectives, Project I vs. Project II scope
Chapter 2: Literature Review & Existing SystemsAnalytical synthesisExpanded thematic review of papers, relevant mathematical/system theories, and comparison matrix of existing tools
Chapter 3: System Analysis & DesignConcrete specificationsFinalized requirements, architecture/block diagrams, pipeline/sequence diagrams, ER schema or hardware schematics
Chapter 4: Methodology & Implementation ProgressPast tense (what was built)Dataset curation/setup, baseline & core algorithms, key modules implemented, tools used, challenges & fixes
Chapter 5: Preliminary Results & Proof of ConceptEvidence-drivenQuantitative baseline metrics, confusion matrices/latency tables, annotated PoC screenshots or hardware test logs, failure analysis
Chapter 6: Conclusion & Project II RoadmapForward planSummary of Phase I status (percent/milestone completion), known limitations, revised Gantt chart for Project II (Sem 8)
References & AppendicesExact attributionComplete IEEE/APA bibliography, plus optional mentor evaluation letter, API specs, or survey forms

7.1.2 Converting a Proposal Into a Progress Report (Common Mistakes to Fix)

Because the two-weeks-prior deadline arrives quickly around Week 12, teams often make four avoidable mistakes when updating their Week-3 Proposal into the Final Progress Report:

  1. Leaving future tense untouched: Writing "We will collect 1,000 images" in Chapter 4 when the semester is over immediately signals copy-pasting from the proposal. Rewrite completed sections in past tense ("1,120 images were collected and partitioned...").
  2. Mismatched diagrams vs. actual code: If you switched databases or model backbones in Week 7, update every diagram, table, and tool section so the report matches your live repository 100%.
  3. Screenshots without explanation: Never paste uncaptioned full-screen UI shots. Every figure needs a numbered caption (Figure 5.2: ...), legible text, and a paragraph explaining what the figure proves.
  4. No supervisor review buffer: Submit a complete draft to your supervisor (and internship mentor, if applicable) at least 5–7 days before the department's two-weeks-prior deadline so signatures and formatting corrections finish calmly.
Example 7.1

Rewriting Proposal Sections Into Evidence-Backed Progress Report Content

A group building a Nepali Legal Document Summarizer & Clause Extractor (Research Track) copied two paragraphs from their Week-3 Proposal into their Week-12 Progress Report: "We will scrape 500 court notices and fine-tune mBART to get high ROUGE scores." Show how to rewrite this properly for Chapters 4 and 5 of the Project I Progress Report.

Audit what is wrong with the proposal text: It uses future tense ("will scrape"), states a vague goal ("high ROUGE scores"), omits dataset cleaning/splitting details, and gives zero actual Phase I measurements.

Rewrite Methodology & Implementation Progress (Past Tense, Concrete Actions):

"Between Weeks 4 and 8, 420 publicly available Supreme Court and Ministry notices (PDF and scanned Devanagari formats) were collected. Scanned pages were extracted via OCR and manually spot-checked for matra errors, yielding 380 clean document-summary pairs split into 280 training, 50 validation, and 50 held-out test documents. A frequency-based extractive baseline (TextRank) and an initial fine-tuned mT5-small abstractive baseline were implemented in PyTorch."

Add Preliminary Results & Project II Roadmap (Evidence + Next Steps): Present a concrete preliminary table comparing TextRank vs. mT5-small (ROUGE-1, ROUGE-L, and observed Devanagari hallucination error rate on 50 validation documents), explain the two main failure modes discovered (date/number distortion in abstractive summaries), and state the Project II plan (adding constrained entity verification and expanding the test benchmark to 150 expert-reviewed judgments).

Answer:

Replacing future-tense promises with exact Phase I counts (380 clean pairs, 280/50/50 split), concrete baselines implemented (TextRank and mT5-small), measured preliminary ROUGE and error analysis, and a targeted Project II plan transforms weak proposal leftovers into a rigorous Progress Report.

7.2 Final Presentation

The Final Presentation (Project I Defence) evaluates both technical progress achieved so far and each team member's engineering readiness to carry the work to completion in Project II. Examiners typically include your supervisor, internal faculty evaluators, and sometimes an external examiner.

Definition

Project I Final Presentation and Defence

The Project I Final Presentation is the semester-end oral defence and live Proof-of-Concept demonstration before the evaluation panel. Groups typically receive 10 to 12 minutes to present Phase I outcomes and demonstrate the working PoC, followed by 8 to 12 minutes of technical Q&A (viva) testing system understanding, preliminary metrics, and Project II readiness.

7.2.1 Structuring the Final Presentation + Live Demo

Unlike the Week-3 Proposal defence—which spent most of its time on background and plans—your Project I Final Presentation should spend at least 60% of the time on Design, Implementation Progress, Live PoC Demo, and Preliminary Results:

Recommended 12-Minute Project I Final Presentation Flow
SlidesSectionTime AllocationKey Focus
1–2Title, Problem & Objectives1.5 minBrief reminder of problem, track, and Project I vs. Project II scope
3Literature Gap & Baseline1 min3–4 row comparison showing chosen baseline and why
4–5Finalized System Design2 minClean system architecture, ER/pipeline/hardware diagram (as actually built)
6–7Phase I Implementation Progress2.5 minData curated, modules completed, engineering challenges overcome
8–9Live PoC Demo + Preliminary Results3.5 minReal live run (plus backup recorded video), benchmark table, error analysis
10–11Limitations & Project II Plan1.5 minHonest bottlenecks discovered + Semester 8 Gantt milestones

7.2.2 Bulletproofing Your Live Proof-of-Concept Demo

Live demos fail most often because of venue Wi-Fi drops, expired cloud tokens, uncharged hardware batteries, or messy screen switching. Protect your demo with five habits:

  1. Run offline / localhost fallback: Pre-load local models, SQLite/PostgreSQL seed data, and dependencies so campus Wi-Fi drops never stall your demo.
  2. Record a 60-second unedited backup video: Keep a crisp MP4 screen capture (or smartphone video of hardware sensors) embedded on a hidden backup slide in case a projector cable, port, or power failure occurs.
  3. Prepare 2–3 unseen test cases: Examiners often ask to test a custom input live—ensure your UI/CLI accepts fresh inputs smoothly without crashing on edge characters.
  4. Bring hardware spares (for IoT/Embedded): Carry spare jumper wires, a multimeter, USB cables, and a power bank.
  5. Rehearse transitions as a team: Practice plugging in the laptop, switching between slides and live app/terminal, and handing the mic smoothly between all 2–3 members.
Example 7.2

Executing a Resilient PoC Demo and Viva Defence on Final Presentation Day

A 3-member Product Track team has built a PoC Smart Campus Energy & Classroom Occupancy Monitor (ESP32 + PIR/current sensors -> MQTT -> FastAPI -> React dashboard). On final presentation morning, the seminar hall Wi-Fi blocks custom MQTT ports. Show how proper preparation saves their demo and how they should handle a tough viva question on sensor false triggers.

Pre-planned Demo Resilience (Before Entering the Hall): Because the team tested their stack offline the night before, Member 1 brings a dedicated phone mobile hotspot / portable travel router pre-configured with the ESP32 SSID and local laptop IP (192.168.x.x), running the Mosquitto broker, FastAPI backend, and React dashboard locally via Docker Compose.

Smooth Live Demo + Backup Evidence:

When campus Wi-Fi blocks MQTT, the team switches effortlessly to its pre-tested local router, toggles a bench load + hand motion in front of the ESP32, shows live occupancy and watt updates on the dashboard within 2 seconds, and opens their 12-hour pre-recorded lab run log in the dashboard history view.

Answering the Tough Viva Question on False Triggers: An examiner asks: "PIR sensors miss stationary students sitting quietly during a lecture. Why didn't your room light turn off falsely?" Member 2 answers directly: "We observed that exact failure mode during preliminary lab logging in Chapter 5—stationary students triggered false-empty timeouts after 3 minutes. For Project I, we added a 10-minute hysteresis window plus current-draw cross-checking; for Project II, we plan to fuse mmWave presence radar or periodic low-resolution thermal/door-count checks to detect stationary occupants reliably."

Answer:

Running a self-contained local router + Docker stack avoids seminar-hall Wi-Fi failures during the live PoC demo, multi-hour historical logs back up the live run, and acknowledging stationary-PIR false triggers with a concrete Phase I workaround and Phase II sensor-fusion upgrade demonstrates mature engineering judgment.

Viva-Style Questions: Progress Report and Final Presentation

Question 1

According to the ENCT 413 syllabus, when must the Project I Final Progress Report be submitted? Why is it scheduled ahead of the final presentation?

Official syllabus timeline: Section 7.1 specifies submission of the Project I final progress report two weeks prior to the end of the seventh semester.

Reason for the two-week lead time: Submitting two weeks early gives the assigned supervisor and evaluation committee time to read the report, run plagiarism/format checks, verify preliminary results before the final presentation, and return any required formatting or technical clarifications before semester grades lock.

Answer:

The Project I Final Progress Report is due two weeks prior to the end of the semester so supervisors and evaluators can review the completed Phase I documentation and preliminary results ahead of the final presentation and grading.

Question 2

What are the major differences between the Week-3 Project Proposal and the Week-12 Project I Final Progress Report?

Tense and purpose shift: The Proposal is a forward-looking plan (8–15 pages) explaining what the team intends to do, why the tools were chosen, and the Semester 7 Gantt plan. The Progress Report is a backward-and-forward engineering record written in past tense for Phase I work and future tense only for the Project II roadmap.

Content additions in the Progress Report: It adds finalized system analysis & design diagrams (ER, architecture, hardware schematics), actual implementation progress, curated dataset statistics, preliminary quantitative results / PoC evidence, encountered bugs/limitations, and an updated Project II schedule.

Answer:

The Proposal pitches future plans and stack choices, whereas the Progress Report documents completed Phase I work in past tense—adding finalized design diagrams, actual implementation details, preliminary benchmark/PoC results, honest limitations, and the Semester 8 roadmap.

Question 3

During your Final Presentation, how should time be balanced across background/literature versus design, implementation, live PoC demo, and preliminary results?

Avoid repeating the Week-3 Proposal: Evaluators already heard your basic motivation in Week 3. Spending 6 minutes of a 10–12 minute defence on generic domain background leaves almost no time for your actual work.

Recommended balance: Keep Title + Problem + Literature Gap concise (about 20–25% of time, ~2.5 minutes), and devote 60–65% of the presentation to Finalized System Architecture, Completed Modules, Live PoC Demo, and Preliminary Results/Error Analysis, ending with 1–1.5 minutes on Limitations and the Project II plan.

Answer:

Spend only ~20–25% of the presentation recapping problem and literature, and dedicate 60–65% to finalized architecture, Phase I implementation progress, the live PoC demo, and preliminary metrics/error analysis, closing with the Project II roadmap.

Question 4

What practical steps should a team take to prevent live demo failures on Final Presentation day, especially when campus internet or hardware behaves unpredictably?

Venue-independent setup: Package the backend, database, and UI to run on localhost (or via Docker Compose) with local seed data and cached ML weights, or bring a dedicated mobile hotspot/local router for IoT demos.

Backup and verification:

  1. Test the exact presentation laptop on a projector/HDMI adapter beforehand.
  2. Keep an unedited backup demo video (screen capture or hardware video) ready on a fallback slide.
  3. Prepare 2–3 fresh test inputs and carry spare cables/power banks for hardware prototypes.
Answer:

Run an offline/localhost setup (or portable router for IoT) so campus Wi-Fi cannot break the demo, pre-test HDMI/projector compatibility, carry hardware spares, prepare fresh test inputs, and keep an unedited backup demo video as a safety net.

Question 5

If your preliminary PoC results in Chapter 5 show lower accuracy or higher latency than your target objective, should you hide those numbers before the Final Presentation? Explain why or why not.

Never falsify or hide preliminary numbers: Project I requires a Proof of Concept and preliminary works, not a polished final thesis. Fabricating or cherry-picking metrics destroys credibility and is easily caught when examiners ask to run a live test.

Turn honest results into engineering insight: Report the exact baseline and current metrics transparently, show a brief error analysis explaining why performance lagged (e.g., class imbalance, unquantized model overhead, lighting glare), and map each root cause directly to a concrete improvement planned for Project II.

Answer:

Never hide or alter preliminary metrics. Report baseline and PoC numbers honestly, diagnose the root causes through error analysis (e.g., class imbalance, unoptimized inference, noisy inputs), and tie each finding to concrete optimizations in the Project II roadmap.

← Initial Project Development Phase