Communication Plan

Communication Plan

This document outlines the official communication channels, meeting schedules, task tracking methods, and announcement procedures for Group 9 (Social Event Mapper).

---

1. Communication Channels

To maintain organized and efficient teamwork, we use specific platforms for different types of communication:

• WhatsApp (Instant & Urgent Communication)

  • Used for quick questions, daily quick check-ins, and urgent announcements.
  • Ensures fast response times for blockers.

• GitHub (Official Documentation & Announcements)

  • Issues & Projects: Used for assigning tasks, tracking progress, and discussing specific code implementations.
  • Wiki: Used for archiving official project documents, meeting notes, and architectural decisions.
  • PR (Pull Request) comments are the primary place for code review discussions.

---

2. Meeting Schedule

We hold regular meetings to ensure alignment, resolve blockers, and plan our sprint tasks.

• Weekly Lab Meetings (Supervisor Sync)

  • Time: Thursday, 13:00 – 15:00 (CMPE 354 Lab Hours)
  • Location: CMPE Labs / In-person
  • Purpose: Syncing with teaching assistants, presenting weekly progress, and getting feedback on deliverables.

• Weekly Dev Sync (Internal)

  • Time: Wednesday, 21:30
  • Location: Google Meets
  • Meeting Format:
    1. Status Updates: Each member gives a brief 2-minute update on what they accomplished.
    2. Blocker Resolution: Discussing any technical or conceptual roadblocks.
    3. Task Assignment: Planning tasks for the upcoming week and updating the GitHub Project board.

---

3. Issue Tracking & Review Policy

• All tasks (development, testing, or documentation) must have an associated GitHub Issue.
• If a team member faces a blocker that takes more than 2 hours to resolve, they must post it on WhatsApp group and tag the relevant subgroup.
• Code merges to the main branch are strictly prohibited without a Pull Request (PR) and at least one review from another team member.

---