Communication Plan

Communication Plan

This page defines how the team communicates, coordinates implementation, tracks tasks, and maintains development quality during the MVP process.

Communication Activities

Communication Activity	Frequency	Participants	Medium	Output
Core team sync meeting	Weekly (Wednesday 20:30)	Entire team	Google Meet	Meeting report with agenda, decisions, and action items
Implementation micro-syncs	After major functionality merges or blockers	Relevant sub-team and impacted members	Online call and team chat	Fast alignment on endpoint, UI, and integration changes
Frontend-backend coordination	Continuous during implementation	Frontend and backend sub-teams	Dedicated WhatsApp groups	Reduced integration gaps and clearer endpoint expectations
Task planning and tracking	Continuous	Entire team	GitHub Issues and project roadmap	Traceable tasks, owners, and deadlines
Code integration and quality control	Per pull request	Implementer and reviewers	GitHub Pull Requests	Reviewed, test-passing, and documented merges
Milestone and document synchronization	During reporting weeks	Entire team	Wiki and scheduled syncs	Updated report pages and submission readiness

Communication Principles

The team follows a lightweight but continuous communication model:

• regular weekly sync meetings for shared planning and status updates
• short targeted meetings when blockers or merge-dependent changes appear
• continuous written coordination through team messaging channels
• task tracking through GitHub Issues and roadmap planning
• pull request based review and integration workflow

This structure helps the team keep development aligned across backend, frontend, Android, and DevOps work.

Process Conventions

The following conventions are already adopted by the team:

• Branch naming: feature/name, bugfix/name
• Commit conventions: feat, fix, docs, chore
• Merge policy: tests pass, documentation is updated, and the build succeeds before merge

Expected Outcomes

The communication plan is intended to ensure that:

• responsibilities remain visible across the team
• blockers are resolved quickly
• integration issues are detected early
• project documents stay synchronized with implementation progress
• milestone preparation is coordinated in a structured way