Skip to content

MVP Demo Plan

Ebubekir Erden edited this page Apr 8, 2026 · 8 revisions

1. Demo Structure and User Scenarios

Core Focus: Demonstrating the end-to-end flow of a mentorship connection, from discovery to session scheduling, including session management (canceling/declining) across both mobile and web platforms.

User Scenarios:

  • Scenario 1: Mentee Discovery & Booking (Mobile): A mentee uses the mobile app to search for a Machine Learning mentor. He reviews an expert's profile, checks their availability, and submits a session request.
  • Scenario 2: Mentor Session Management & Approval (Web): A mentor logs into the web dashboard. First, due to an unexpected plan, he cancels a pre-existing booked session. Then, he reviews his pending requests: he declines one request to manage his workload, and accepts our main mentee's request. Finally, he checks his updated schedule.
  • Scenario 3: Mentee Confirmation & Profile Update (Mobile): The mentee verifies that the request has been accepted and updates his profile to reflect his new learning journey.

2. Script (7-8 Minute Flow)

0:00 - 1:00 (Narrator): Introduction & Setup

  • Action: Screen displays mentee dashboard on the mobile app. Both users are already authenticated.
  • Dialogue (Barkın): "Welcome to our MVP demo. Today we will show you how our platform, Campus-Neighborhood Mentorship Network, seamlessly connects mentees and mentors. Our platform is a community-driven application designed to connect expert mentors with interested mentees based on interests, career paths, and real-world locations. In our demo today, we will witness a university student connect with an industry professional to learn Machine Learning."

1:00 - 2:30 (Narrator, Mobile Presenter): Discover & Request (Mobile)

  • Action (Turgut): Navigate to the 'Discover' tab. Filter for "Machine Learning". Click on Mentor Göksel's profile. Scroll through Expertise and availabilities. See Wednesday is busy, select Thursday, and submit a request.
  • Dialogue (Barkın / Turgut): * (Turgut): "I am a student at Boğaziçi University and I really want to learn about Machine Learning. I heard about this Neighborship app from a friend, so let's give it a try and search for a mentor."
    • (Turgut): "Let's filter for Machine Learning. Oh, Göksel Deniz Çelik looks like a great match. He works at Amazon, which is impressive. Let's check his availability. He is not available on Wednesday, but he is free on Thursday. Let's send a request."

2:30 - 4:30 (Narrator, Web Presenter): Session Management - Cancel, Decline, Accept (Web)

  • Action (Göksel): Go to Profile/Schedule. Cancel an existing Saturday session. Go to Dashboard to check pending requests. Open the first profile and decline it. Open Turgut's profile, accept it. Navigate to the Schedule to verify the new class. Navigate to connections page to have an overview of mentees
  • Dialogue (Barkın / Göksel):
    • (Barkın): "At this point, our mentor comes into play. He is a seasoned professional working at Amazon, giving back to the community. However, he suddenly has an unexpected problem with his schedule."
    • (Göksel): "One of my friends just called me over, so I need to make plans with him. First, I want to cancel my existing session on Saturday at 11 AM... Cancel booking, done. I'll mark that time as unavailable."
    • (Göksel): "Now let me go to my dashboard. I have two pending mentorship requests. Let's look at the first one. Hmm, this profile isn't that bad, but first, I have to check the number of my current mentees. Let me go to the connections section in order to see them. Hmm, there are plenty of them compared to my free time, so I will decline this one."
    • (Göksel): "Let's check the second request from Turgut. This looks like a very decent profile. Even though I have enough students, I will accept him anyway since he is studying at the university that I've graduated from. Solidarity of the Boğaziçi students is not easy to find. Finally, let me check my schedule to see my upcoming classes for today... Looks good."

4:30 - 5:30 (Narrator, Mobile Presenter): Dashboard Verification & Profile Update

  • Action (Turgut): Refresh the mobile app. Check the "Upcoming Sessions". Go to Profile settings and update the bio.
  • Dialogue (Barkın / Turgut):
    • (Barkın): "Later that evening, our mentee checks his app to see whether his mentorship request was accepted or not."
    • (Turgut): "Let me check if my request is accepted... Wow, it's accepted! It's now in my Upcoming Sessions. Now, let me quickly update my profile bio to say: 'Learning Machine Learning from Göksel Çelik.' Save... and done."

5:30 - 7:00 (Narrator): Conclusion & Future Features

  • Action: Both screens rest on their respective homepages/profiles.
  • Dialogue (Barkın): "As we can see, the connection is complete. This concludes our core scenario. We have many more features planned for future implementation. We are planning a messaging functionality so mentees and mentors can easily share materials. We will also introduce an admin panel with reporting features, notification systems, and a feedback/rating mechanism. Most importantly, we plan to implement a location-based filtering system—a true 'neighborhood' feature—that allows users to match with mentors within a specific radius, like 15 kilometers, for easy in-person meetings. Thank you for listening. We will now take your questions."

3. Demo-Data Strategy

  • User Roles & Accounts Needed (4 Total):
    • Mentor User (Göksel): Pre-authenticated on Web. Profile has "Amazon" in the bio, "Machine Learning" tag, and availability set up.
    • Mentee User 1 - Main (Turgut): Pre-authenticated on Mobile. Profile mentions being a Boğaziçi University student.
    • Mentee User 2 - The Cancelled: An account that already has an approved, booked session with Göksel on Saturday at 11 AM (so Göksel can cancel it live).
    • Mentee User 3 - The Declined: An account that has sent a pending request to Göksel (acting as the "extra" student Göksel declines).
  • Pre-populated State:
    • The Discover page on mobile should have Göksel appearing at the top when filtered for Machine Learning.

4. Role Assignments

  • Göksel Deniz Çelik: Web Presenter / Mentor: Introduces the web dashboard, manages the cancel/decline/accept flow.
  • Turgut Gürel: Mobile Presenter / Mentee: Introduces the mobile app screen, navigates discovery, and updates profile.
  • Barkın Akkol: Narrator: Introduces the flow, handles transitions, and closes with future features.
  • Mehmet Emin Algül : Timekeeper: Tracks the 8-minute clock.
  • Mehmet Ali Özdemir / Enes Öztürk: Note Taker: Observer for Q&A.
  • İnan Kazancı: Technical Support: Controls the web flow, manages screen mirroring (Type-C to HDMI), and backup videos.
  • Ebubekir Sıddık Erden: Technical Support: Controls the mobile app flow, manages screen mirroring (Type-C to HDMI) and backup videos.

5. Backup Plan (Failure Cases)

  • Internet/Connectivity Issues: If live mirroring of the mobile app fails, Technical Support will have a pre-recorded video of the mobile flow queued up to play while narrating.
  • API/Database Latency: If the request doesn't immediately show up on the web dashboard (stale time issues), the Mobile Presenter is prepared to manually refresh, while the Narrator fills the dead air naturally.
Team Members

Requirements & Design


Milestones & Deliverables

Final Milestone (1.0.0)

Final Release Reports

Milestone 2 (0.2.0-alpha)

MVP Milestone (0.1.0-alpha)


Project Documentation


Meetings & Reports

Weekly Meetings

View List

Customer & Stakeholder Meetings

Other Meetings

Lab Reports

View List

Templates

Clone this wiki locally