Daily Standup Meeting Log - snuhcs-course/swpp-2026-project-team-16 GitHub Wiki

Daily Standup Meeting Log

Meeting Log Template

  • Date: YYYY-MM-DD
  • Attendees: A(PM), B, C
  • Discussion Points:
    • Progress check
    • Blocker
    • Task allocation
  • Individual Progress:
    • A (PM):
    • B
    • C

Log #1 : 2026-09-30 (Iteration 1 Kickoff)

  • Date: 2026-09-30
  • Attendees: Soonyoung Park(PM), Yewon Lee, Anton
  • Goal: Sync on Iteration 1 task and workflows

  • Key Architecture & Tech Stack Decisions:

    • Backend Framework: Transitioned from FastAPI to Django (by Anton) for built-in User/Route Database management, and scalable API structures.
    • Updated Iteration 1 MVP Scope:
      • In-Scope (Iter 1): Route generation (Start point, Distance), LLM briefing, User-based Route Save/Store, Route Delete.
      • Next Iterations Scope: Elevation parsing based on user input, Route sharing, User profile pages, Route reviews, Signal count management, Offline job.
      • Out-of-Scope: Real-time GPS tracking, Preferred path routing (parks, etc.).

  • Updated Iteration 1 Development Timeline:

    • By 10/01: Anton decide Route DB schema & JSON structure $\rightarrow$ Team review & feedback.
    • By 10/01: Soonyoung (PM) create base Android UI skeleton $\rightarrow$ Pass to Yewon.
    • By 10/02: Anton create Django Mock Server.
    • By 10/05: Yewon complete working Android App integration with Django Mock Server.
    • By 10/07: Integrate AI/LLM route generation algorithm into Django server ahead of TA Check-in.

  • Individual Action Items:

    • Soonyoung (PM): Update Requirements Spec & other documents on Wiki (reflect Django & revised scope), build Android Base UI Skeleton by 10/1.
    • Anton: Define DB schema/JSON structure by 10/1, build Django Mock Server by 10/2.
    • Yewon: Receive UI Skeleton (10/1), connect Android App to Django Mock Server by 10/5.

Log #2 : 2026-10-04 (Iteration 1 Mid Progress Sync)

  • Date: 2026-10-04
  • Attendees: Soonyoung Park(PM), Yewon Lee, Anton
  • Goal: Progress check and task alignment for Integration and Algorithm implementation

  • Progress Check & Discussion Points:

    • Django Mock Server: Anton shared the Mock Server progress. Yewon provided review feedback, and the Mock Server setup is now finalized.
    • Android UI Skeleton: Soonyoung presented the base UI skeleton. Yewon provided review feedback. (Updates will be applied as soon as Soonyoung's laptop repair is completed.)

  • Task Allocation & Next Steps:

    • Yewon: Work on Android-Backend integration using Anton's Mock Server.
    • Anton: Implement a simple working path-generation algorithm on the backend for immediate testing and demo execution.
    • Soonyoung (PM): Apply UI review feedback, update several Documentations on Wiki, and design a advanced path-generation algorithm for future (iterations).

Log #3 : 2026-10-09 (Iteration 1 Review & Retrospective)

  • Date: 2026-10-09

  • Attendees: Soonyoung Park(PM), Yewon Lee, Anton

  • Goal: Iteration 1 Review, Retrospective, and Planning for Iteration 2

  • Iteration 1 Review & Accomplishments:

    • End-to-End Working Prototype: Successfully connected Android App with Django backend, enabling route generation, Gemini AI briefings, POI search, and route saving/deletion.
    • Deliverables Completed: Published all Wiki documentations (Design Doc, Requirements Spec, AI Collaboration Report), uploaded demo video to iteration-1-demo branch, and updated project schedule/README.

  • Retrospective & Lessons Learned:

    • Process Improvement (AI Collaboration Report): Compiling PR numbers, commits, and prompt histories at the very end of the iteration required significant manual effort. Moving forward into Iteration 2, we will log AI usage and PR metadata immediately after each task/PR is completed.

  • Next Iteration (Iteration 2) Scope & Action Items:

    • Project & Feature Development:
      • Elevation API Integration: Connect Open-Elevation API to parse slope and terrain data for generated routes.
      • Traffic Signal Parsing: Implement regex/OSM tag parsing for crossing=traffic_signals to calculate and display obstacle/signal counts.
      • Map UI Connection: Render actual polylines on the interactive Android map view.
    • Documentation & Testing:
      • Prepare initial Testing Documentation and begin writing unit/integration test suites alongside feature implementation.
      • Prepare Midterm Presentation.

  • Iteration2 Kickoff Meeting Date: 2026-10-13

Log #4 : 2026-10-13 (Iteration 2 Kickoff)

  • Date: 2026-10-13
  • Attendees: Yewon Lee(PM), Soonyoung Park, Anton
  • Goal: Decide the Iteration 2 tasks, owners, and deadlines

  • Task Allocation & Deadlines:

    • Anton: Fix loop generation error (10/15), backend route name change (10/14), account management backend - sign-up, log-in (10/14).
    • Soonyoung: Connect elevation data (10/15), connect traffic signal data (10/15), connect the data to the map UI (10/16).
    • Yewon (PM): Account management UI (10/14), account management front-back integration (10/15), scoring function and data-based LLM briefing (10/16), integration test, midterm presentation (10/19).
    • Everyone: Unit tests for their own parts and ground truth collection (10/17).

  • Key Decisions:

    • Elevation on the map: Show slope by color (uphill red, flat yellow, downhill green).
    • Scoring function: Rank the 2-3 loop candidates with score = w1 x elevation gain + w2 x traffic signals + w3 x distance error. Weights stay fixed for now; in Iteration 3 the LLM adjusts them to the user's preference.
    • Data-based LLM briefing: Put the calculated numbers into the briefing (e.g. total climb 25m, 3 traffic lights, uphill from 2.1km).
    • Testing: Unit tests for each part (e.g. 3 signal nodes within 20m count as 1, an elevation list gives the right total climb). Integration test from the start point through loop generation, elevation/signal parsing, scoring, and briefing. Ground truth: count traffic lights and check elevation at a few places by hand or on a map, and compare with the system values.

  • Iteration 3 & 4 Preview:

    • Iteration 3: Run tracking (GPS, background recording, run summary), offline route view, turn-by-turn voice guidance, route review (star rating, comment), LLM preference mapping (natural language to scoring weights), run history.
    • Iteration 4: Route sharing and explore, running group, off-route detection and return guidance, external pilot test (2-3 users) and bug fixes, feature freeze and deployment build.

Log #5 : 2026-10-19 (Iteration 2 Mid Progress Check)

  • Date: 2026-10-19
  • Attendees: Yewon Lee(PM), Soonyoung Park, Anton
  • Goal: Check progress against the kickoff plan

  • Progress Check:

    • Done: Everything except testing and the data-to-map UI connection.
      • Elevation data (PR #8), traffic signal counting (PR #12)
      • Loop generation error fix, account backend - log-out and Google log-in (PR #9), route name (PR #11, app side PR #14)
      • Account management UI (PR #10), front-back integration (PR #15), scoring function and data-based briefing with 3 route options (PR #16)
    • Added during the iteration: Demo build fix (PR #13), local Seoul street graph because the public Overpass server was at capacity (PR #17), swipe-to-delete for saved routes (PR #18).
    • Not done yet: Connecting the data to the map UI (slope colors), unit/integration tests, and ground truth collection.

  • Next Steps (owners from the kickoff plan):

    • Soonyoung: Connect the data to the map UI (slope colors).
    • Yewon (PM): Integration test, midterm presentation.
    • Everyone: Unit tests for their own parts and ground truth collection.