Communication Plan and Policies

Communication Plan

1. Weekly In-Person Meetings

• Schedule: Every Tuesday in the lab.
• Purpose: To evaluate progress, discuss challenges, and plan upcoming tasks.
• Expectations: All team members are required to attend, prepared with updates on their work and any issues encountered.

2. Weekly Virtual Meetings

• Schedule: Every Thursday from a time between 8:00 PM and 11:00 PM, to be determined by a poll, via Google Meet.
• Purpose: To align on project milestones, share updates, and address any urgent matters.
• Expectations: Team members must join on time, and actively participate in discussions.

3. Daily Communication

• Platform: WhatsApp group.
• Purpose: To facilitate quick updates, questions, and informal collaboration.

---

Development Policies

1. Branching Strategy

• Main Branch: The main branch is reserved for production-ready code.

• Dev Branch: The main development branch. All PRs must be merged to this branch.

• Feature Branches: All development work will be conducted in branches prefixed with feat/#issuenumber.

  • Example: feat/138-mobile-user-authentication, feat/240-backend-payment-integration.
  • Branch from the dev branch, and after development is finished, open a PR with proper description to the dev branch.

• Policy: Separate branches for mobile, backend, and frontend (as used in the previous term) will not be created. All features will be developed in unified feat/ branches to streamline collaboration.

• Detailed CI CD & Branching Policies

2. Collaboration Guidelines

• Code Reviews: All changes in feat/ branches must be reviewed by at least one other team member before merging into the main branch.
• Commit Messages: Use clear and descriptive commit messages to document changes (e.g., "Add user authentication API endpoint").
• Issue Tracking: Use the project’s issue tracking system to log tasks, bugs, and feature requests. Progress is managed through GitHub Projects.
  • Todo: Tasks that are created and must be done.
  • In Progress: Tasks that are being actively worked on.
  • Waiting For Review: Tasks that are waiting to be reviewed by the assigned reviewer.
  • Done: Closed issues