Lab 5 Meeting Notes

Lab 5: MVP Implementation & Planning

Date: November 4, 2025

Attendees

• Barathan
• Selman
• Çağlar
• Berke
• Emin
• Berkay
• Ahmet
• Taha
• Nilsu
• Ömer Faruk

---

Agenda

• Define and finalize MVP goals and objectives
• Outline implementation plan including critical points, workflows, and progress tracking
• Review previous milestone feedback and discuss lessons learned
• Establish testing strategy and unit test coverage reporting
• Design a preliminary acceptance test plan focusing on user and business validation criteria

---

Discussion

• MVP Goals and Objectives:

  • The primary focus is to enhance user engagement and community interactivity.

  • Two key new features will be prioritized:

    1. Personal Statistics Page – shows real environmental impact (e.g., “You saved 3 turtles!”).
    2. Event System – location-based sustainability events and notifications.

  • These were chosen based on client feedback to strengthen motivation, inclusivity, and real-world engagement.

• Critical Implementation Points:

  • Core Functionalities: Account Management, Waste Logging, and Goal Setting.
  • Interactivity: Events, Leaderboards, and Challenges.
  • Accessibility: W3C standards, Turkish/English support, and multiple color palettes.
  • Engagement: Stats page, motivational notifications, and community challenges.

• Issue Tracking:

  • GitHub Issues are actively used with custom templates and assigned reviewers.
  • Each issue contains acceptance criteria, detailed descriptions, and deadlines.
  • GitHub Projects and Milestones are used to monitor deadlines and dependencies.
  • Example: documentation and feature issues were shown with progress screenshots.

• Execution Practice:

  • Design: Figma used for UI and design standards.

  • Development: Teams divided into Web (React), Mobile (React Native), and Backend (Django).

  • Version Control: Git with branch protection and PR reviews.

  • Deployment: Render platform for both frontend and backend.

  • Coordination:

    • WhatsApp for daily communication.
    • Google Meet for formal meetings.
    • Git & Communication Policies established for workflow consistency.

• Progress Tracking:

  • Weekly reports and lab notes on Wiki.
  • GitHub milestones for versioned progress tracking.
  • Revised SRS and UML documentation checked against implementation.
  • “Pre-release versions” used for internal demos and milestone validation.
  • Adaptive reprioritization based on feedback (e.g., adding personal stats).

• Lessons Learned:

  • Main insight: engagement must feel meaningful — users should see their environmental impact.
  • Transition from manual location input to geolocation-based experience for better usability.
  • Introduction of motivational notifications and community feedback integration.
  • Shift toward community-centered development and gamification.
  • Accessibility and inclusivity remain ongoing priorities.

• Testing Strategy:

  • Backend: 13 unit tests implemented (≈43% coverage).

    • Covers authentication, waste logging, and goals modules.

  • Frontend (Web): Partial login tests (≈14% coverage) — dependency issues under review.

  • Frontend (Mobile): No current tests; planned for upcoming sprint.

  • Goal: Achieve 60%+ coverage by end of semester.

  • Backend tests proven meaningful — detect real functional errors (login, session, field validation).

• Acceptance Criteria & Scenarios:

  • Core Validation: Users can register, log waste, set goals, and view impact.
  • Engagement Validation: Event participation and leaderboard functionality motivate recurring usage.
  • Accessibility Validation: W3C compliance and multi-language support tested via WAVE and axe tools.
  • Location Validation: Automatic detection, city-based challenges, and event suggestions verified.
  • Cross-Platform Validation: Web ↔ Mobile synchronization tests for logs and leaderboards.
  • Community Validation: Feedback and problem-sharing features tested with beta users.

---

Action Items

• Implementation Tasks

  • Finalize Personal Statistics Page prototype — assigned to Frontend Team.
  • Integrate Geolocation Tracking for events — assigned to Mobile Team.
  • Refine Motivational Notification System — Backend & Design Teams collaboration.

• Documentation & Tracking

  • Update Project Wiki with Lab 5 report and meeting summary.
  • Link issues to GitHub Milestone MVP Implementation.
  • Track test coverage updates in dedicated QA dashboard.

• Testing & Validation

  • Add 10+ frontend test cases before next milestone.
  • Conduct accessibility and geolocation QA sessions by Nov 15, 2025.
  • Schedule stakeholder feedback demo for Nov 18, 2025.