Lab 7 Report

Lab 7 Report

Objective

Finalize the Milestone 1 (MVP) Demo plan, define user scenarios, write the demo script, prepare the demo-data strategy, assign roles, and rehearse the presentation flow.

Work Done During Lab Session

1. Demo Structure & Scenario Design

We defined two complementary demo scenarios with zero functional overlap, covering 14 distinct MVP features:

• Web Scenario (4 minutes) -- Mentor Perspective: Demonstrates mentor profile editing, availability scheduling, incoming request list, candidate review with privacy controls, accepting and rejecting requests, active mentorship list, and capacity tracking.
• Mobile Scenario (4 minutes) -- Mentee Perspective: Briefly shows the registration page, then demonstrates mentee profile viewing and editing, mentor discovery and browsing, mentor profile detail view, sending a mentorship request, and request status tracking via the "My Requests" page.

The mentorship request is the narrative bridge connecting both scenarios: the mentee sends it on mobile, and the mentor reviews and acts on it on web. Each scenario ends with its natural consequence -- active mentorship list on web, request status tracking on mobile.

2. Script Writing

We wrote a detailed, timestamped script for the full 8-minute presentation. Each segment specifies the speaker, the actions performed on screen, and what the audience should observe. The script follows the format outlined in the lab instructions. The full script is included in the MVP Demo Plan wiki page.

3. Demo-Data Strategy

We designed a realistic data set to support both scenarios:

• Mentor accounts pre-populated with professional profiles, availability, and a fixed max mentee capacity of 3.
• Mentee accounts at different stages (one with a pending request, one already in an active mentorship) to avoid creating data from scratch during the demo.
• Edge case data including a mismatched request (for realistic rejection) and a mentor at full capacity (3/3) to demonstrate system validation.

Full details are in the MVP Demo Plan wiki page.

4. Role Assignments

We assigned specific responsibilities for the demo day:

Role	Assigned To
Web Demo Presenter & Narrator	Amin Abu-Hilga
Web Demo Operator	Muhammet Sami Cakmak
Mobile Demo Presenter & Narrator	Burak Ogut
Mobile Demo Operator	Ovgu Su Afsar
Backend & Architecture Q&A	Mehmet Bora Sarioglu, Ibrahim Kayan
Infrastructure & Deployment Q&A	Beratcan Dogan
Note-taker (customer feedback)	Ibrahim Kayan

5. Deployment & Realistic Data

• The application will be deployed and accessible via a secure public HTTPS URL (not run locally).
• All demo data reflects realistic user journeys (real names, plausible bios, context-appropriate interests and skills) rather than placeholder or dummy values.

6. Backup Plan for Failure Cases

Failure Scenario	Mitigation
Internet connection is down	Pre-record a video walkthrough of both scenarios as a fallback.
Backend is unresponsive	Have a local Docker Compose setup ready on a laptop as a backup environment.
Mobile emulator crashes	Use a second device or a pre-recorded screen capture of the mobile flow.
Database is empty or corrupted	Maintain a SQL seed script that can repopulate demo data in under 30 seconds.

Individual Contributions

Amin Abu-Hilga

• Drafted the web demo operator action steps and transition plan #163
• Defined backup plan strategies for deployment failure scenarios #162
• Contributed to demo role assignments and web presenter coordination #164

Ovgu Su Afsar

• Authored the mobile demo scenario and mentee onboarding user story #163
• Designed the mobile demo-data strategy for mentee accounts #163
• Documented mobile demo findings in lab report #164

Muhammet Sami Cakmak

• Drafted the web demo narration script with timestamped segments #163
• Defined the mentor dashboard user scenario and feature walkthrough #162

Beratcan Dogan

• Designed the demo-data seeding strategy and database population plan #163
• Defined deployment requirements and HTTPS accessibility criteria #162
• Contributed to backup plan for infrastructure failure cases #164

Ibrahim Kayan

• Documented demo environment setup requirements for lab report #164
• Contributed to demo-data strategy for mentor account profiles #163
• Assigned as note-taker for customer feedback during demo #162

Burak Ogut

• Planned the mobile demo operator workflow and device transition strategy #163
• Defined mobile registration and profile completion demo steps #162

Mehmet Bora Sarioglu

• Coordinated demo structure design and feature coverage matrix #162
• Authored the MVP demo plan document with script and data strategy #163
• Compiled and finalized the lab 7 report #164