Communication Plan

📡 Communication Plan

This page outlines our communication strategy for the Ethical Job Board & Resume Mentorship Platform project. Clear, timely, and respectful communication is essential to ensuring our large team of 10 members works effectively throughout the development process.

---

🧩 Objectives

• Maintain alignment across frontend, backend, and mobile teams
• Ensure transparency in decision-making and task assignment
• Facilitate asynchronous and synchronous collaboration
• Track progress, resolve blockers, and provide feedback efficiently

---

🗂️ Channels of Communication

Channel	Purpose	Tool
GitHub Issues	Task assignment, progress tracking	GitHub
GitHub Wiki	Documentation (meetings, architecture etc.)	GitHub
WhatsApp Group	Daily communication, quick questions	WhatsApp
Google Meet	Periodic stand-ups, milestone discussions	Google Meet

---

🧑‍💻 Communication Norms

• Daily updates in WhatsApp (progress, blockers)
• Meetings via Google Meet (Decided through issues)
• Issues should be updated when:
  • A task is started (add in-progress label)
  • A blocker is encountered (comment on the issue)
  • A task is completed (PR linked & issue closed)
• Pull Requests should:
  • Link related issues using keywords (e.g., Closes #23)
  • Be reviewed by at least one team member
  • Include screenshots or test logs when applicable

---

🔁 Meeting Structure

🧾 Weekly Team Meeting

• When: On Decided Dates at 21:00 (A poll is opened for determining the time)
• Where: Google Meet
• Who: All team members
• Format:
  • Review what was done since our last meeting
  • Provide feedback on ongoing issues
  • Redistribute remaining tasks if needed
  • Discuss blockers and deployment updates

🧠 Sub-Team Syncs

• Held on-demand for frontend/backend/mobile team discussions
• Coordinated via WhatsApp and meetings are conducted through Google Meet

---

🆘 Handling Blockers

1. Share the problem in the WhatsApp group. Explain it as detailed as possible!
2. Tag relevant contributors or domain leads.
3. If unresolved, escalate in the meeting.

---

✅ Documentation Responsibilities

• Meeting notes must be uploaded to the GitHub Wiki.
• All architectural and process decisions should be documented.

---

🧪 Example Workflow

1. You are assigned a task → you create or are added to an issue
2. You start development → mark the issue as in-progress
3. You need help → you send a message in WhatsApp and tag relevant members
4. You finish the task → you open a PR and link the issue
5. Your PR is reviewed and merged → you close the issue
6. The status is reflected in issues and discussed at meeting

---

🏁 Final Notes

• All communication should remain respectful and constructive.
• Over-communication is better than under-communication.
• Be proactive in raising issues or offering help.

Let’s build something impactful together!