Final Demo Notes

Final Demo Notes

Raw notes captured during / reconstructed shortly after the Final Milestone demo. Linked from §4.7 of Final Milestone Deliverables. Owning issue: #421

Date of demo: 13 May 2026, Wednesday, 15:00 – 16:00 Note-taker: İbrahim Kayan Attendees: Mehmet Bora Sarıoğlu, İbrahim Kayan, Beratcan Doğan, Amin Abu-Hilga, Muhammet Sami Çakmak, Burak Ögüt, Övgü Su Afşar

---

Demo timeline

Note: the actual demo flow differed from the original Final Demo Plan. The scenario had to be revised shortly before the demo, so the notes below are reconstructed from the live presentation flow and team memory.

• 15:00 — Demo session started with the full team present.
• Bora introduced the project and gave a high-level overview of the final-milestone features, emphasising the social feed / blog / post surface and the mentorship-management features (tasks, meetings, milestones, and the progress timeline).
• Burak continued with the mobile-side demonstration. The mobile walkthrough covered feed browsing, scrolling through posts, post interactions (likes / comments), recommendation-related behaviour, mentor discovery through matching, and blog / profile flows.
• Bora then continued with the web-side and backend-related explanation. This covered tasks, meetings, milestones, the progress timeline, social-feed interaction logic, recommendation logic for posts / the social feed, messaging flows, mentor profile settings, and availability-related features.
• The demo exceeded the planned time limit. This reduced the effectiveness of the presentation and limited the time available for showing some features clearly.

---

Questions asked

• Q: How does the progress timeline relate to meetings and mentorship progress?

  • A: The team explained that the progress timeline aggregates mentorship-related activities — meetings, milestones, and tasks — onto a single chronological view so the mentorship journey can be followed over time.

• Q: How does the recommendation / matching logic work?

  • A: The team explained the recommendation idea at a high level: users are matched through profile information, interests, and mentor / mentee compatibility, with the advanced ranker layering semantic similarity, geographic proximity, and availability signals on top.

• Q: Question related to the social feed and the post-interaction / recommendation behaviour.

  • A: The team explained the general idea behind post interactions (like, comment, share, repost, bookmark) and the recommendation behaviour in the social feed (interest-overlap baseline plus the advanced engagement-driven ranker that feeds the For-You tab).

---

Issues encountered during the demo

• The demo scenario had to be revised shortly before the demo, which made the final presentation flow less stable than planned.
• The demo exceeded the time limit.
• Several features could not be shown sufficiently because of time pressure and the late scenario change.
• Some planned features were either not fully prepared for a smooth live demonstration or could not be demonstrated clearly within the available window.
• Implemented features that were not presented in the live demo, despite being shipped:
  • admin panel (user moderation queue, report queue, admin direct / broadcast messaging)
  • banning / moderation flows (automatic temporary ban for excessive cancellations, admin-imposed ban, ban-lifted notification)
  • end-mentorship flow (mentor-side PATCH /end)
  • task-assignment flow in full detail (assign → submit → review with APPROVED / NEEDS_REVISION outcomes)
  • file attachments (in mentorship chat and on feed posts)
  • some additional mentorship-management flows
  • several secondary features that could not fit into the revised scenario

Each of these is independently documented in §4.4 (UI / UX screenshots) and §4.2 (Status of Requirements) of the Final Milestone Deliverables, so the absence from the live demo does not imply the work is missing — only that it did not fit into the demo time budget.

---

Instructor / customer feedback

• Instructor Suzan Üsküdarlı responded positively to the blog / post and in-app messaging features.
• The scrolling-feed experience and interaction logic were received positively.
• The social-feed idea and interaction model were generally appreciated.
• The Explore / recommendation tab and recommendation-algorithm logic were acceptable, but could have been demonstrated more clearly (the factor-chip explanation and ranker behaviour did not get enough on-screen time).
• The task, meeting, milestone, and progress-timeline ideas were generally appreciated.
• The team's overall feature ideas were received positively, but the presentation would have been more effective if the scenario had been more stable and all planned features had been demonstrated smoothly.

---

Action items captured

• Improve the final demo narrative / scenario structure for future presentations so that feature coverage fits the time limit.
• Prepare a shorter fallback demo path for cases where not all features can be shown live.
• Make the recommendation and Explore-tab behaviour easier to demonstrate visually (e.g. a prepared seed account whose top-5 matches each show distinct factor chips).
• Ensure mentorship-management flows (tasks, meetings, milestones, progress timeline, end-mentorship) can be shown clearly in one coherent scenario.
• Document features that could not be demonstrated live but are implemented or planned — see §4.4 of the Final Milestone Report for the screenshot-evidenced record.
• Collect confirmations from presenters about the exact order of the demo and any missing questions / feedback so this page can be amended.