Meeting 11 of 451 - bounswe/bounswe2025group5 GitHub Wiki

Details

📅 Date: 05 / 11 / 2025
📍 Location: Lab Session
🕐 Duration: 15.00-16.30
📝 Note Taker: Yusuf Onur Öksüz

👥 Attendees

Agenda

  1. Goals/Objectives for MVP
  2. Implementation Plan
  3. Lessons Learned & Mitigation
  4. Testing Strategy and Accepting Testing Strategy

Discussion Items

1. Goals/Objectives for MVP

  • Emphasized that environmental impact visualization and user motivation are now primary objectives for MVP.
  • Team agreed that analytics and data visualization are priority tasks to highlight progress and encourage engagement.
  • Discussed community engagement upgrades, focusing on notifications, reporting system, and moderation tools** to create a safer and more interactive platform.
  • Reaffirmed that usability and accessibility are not optional—keyboard navigation, color contrast, and screen-reader compatibility must be implemented for the MVP.
  • Agreed to ensure security, scalability, and sustainability principles are respected in infrastructure planning.

2. Implementation Plan

  • Noted that accessibility features previously postponed (e.g., focus indicators, keyboard operability) will be integrated in this milestone.
  • Confirmed that GitHub issue tracking and Slack integration remain effective; no major process changes required.
  • Backend, web, and mobile subteams will maintain separate sub-groups for focused progress tracking and troubleshooting.
  • Discussed importance of real-time waste tracking updates and ensuring synchronization across user devices.

3. Lessons Learned & Mitigation

  • Highlighted two critical learnings from the previous milestone:
    • (a) The necessity of customer-driven development — integrating feedback early improves alignment and feature relevance.
    • (b) The need for balanced workloads — front-end teams were overburdened last cycle.
  • Improvements made: upgraded server infrastructure, distributed UI workload more evenly, and introduced flexible deadlines.
  • Impact Visibility features (user contribution graphs, challenge completion notifications, community statistics) will be developed early in this cycle.

4. Testing Strategy & Acceptance Test Plan

  • Discussed current lack of unit tests; Postman testing provides 100% endpoint coverage, but it’s not automated.
  • Decided to begin implementing unit and integration tests to improve automation and reliability.
  • Will prioritize test coverage for:
    • Waste tracking
    • Post creation/moderation
    • Notification system
    • Accessibility checks (WCAG compliance)
  • Acceptance criteria reviewed and confirmed as comprehensive. Each subteam will validate their components against respective user stories.

Action Items

# ## Details Assignee(s) Deadline