Communication Plan - bounswe/bounswe2026group4 GitHub Wiki

1. Communication Channels

GitHub (Primary Communication)

  • Main platform for all project-related communication and coordination.
  • Issues and Pull Requests are the primary way to track work and decisions.
  • Writing clear, detailed issues and PR descriptions is required.
  • All team members should regularly check the repository and their emails for mentions and updates.

GitHub Discussions

  • Used for topics that require broader input or are not tied to a specific issue/PR.
  • Encouraged for design decisions, questions, and open-ended discussions.

Meetings (Synchronous Communication)

  • Used for alignment, planning, and resolving blockers efficiently.
  • Important decisions should still be reflected on GitHub for traceability.

Lab Hours

  • Valuable time to raise concerns, clarify uncertainties, and get immediate feedback.
  • Recommended to use actively for both technical and coordination discussions.

2. Meeting Schedule

Weekly Team Meetings (Mandatory)

  • Held once every week. Mondays, 20.00-21.00 unless decided otherwise unanimously
  • Meeting Structure:
    • General Updates: Each member/sub-team shares progress briefly.
    • Blockers & Issues: Discuss current challenges and dependencies.
    • Planning: Define tasks and priorities for the upcoming period.
    • Feedback: Share suggestions on implementation and workflow.
    • Testing/Validation (if applicable): Review results such as end-to-end tests.

Sub-team Meetings

  • Frontend, Backend, and other sub-teams meet as needed.
  • Preferably at least once per week during the implementation phase.
  • Focus on detailed technical discussions and coordination within the sub-team.

Milestone Meetings

  • Dedicated meetings to evaluate milestone success.
  • So far:
    • 1 milestone meeting completed

3. Communication Guidelines

  • Use GitHub as the single source of truth for all technical work.
  • Keep communication*transparent and documented.
  • Respond to mentions and requests in a timely manner.
  • Clearly state assumptions, decisions, and trade-offs in issues/PRs.
  • Avoid undocumented decisions made only in meetings.