The primary team communication tool will be the team group chat.
If a member is late or will be absent, they will notify the team through the agreed communication channel ASAP. Critical updates will be sent through the channel as well.
Team members will respond to messages and emails within 24 hours on weekdays. If no response is received within the agreed timeframe, silence will be taken as agreement unless stated otherwise.
Any communication with our client, coach, and professor will be done via email and all teammates will be copied on the email.
Meetings will start at the scheduled time. All members are expected to join on time.
All members are expected to contribute actively and respectfully.
If a member anticipates falling behind, they must notify the team immediately to allow time for adjustments.
Teams will work together to address any issues as early as possible and determine a resolution.
For critical tasks, one member will be designated as a backup to step in if needed.
If delays occur, the team will redistribute work to balance the load.
Coding Practices
We will conform to the style guide for each language we will be using.
Commit messages must follow the Convention Commit Standard.
All work will be done in individual feature branches; no direct commits to main.
Pull Requests (PRs) are required before merging into main.
At least one other team member must review and approve a PR before it is merged.
Code should not be merged if build/tests are failing.
The team will work to actively maintain documentation: including comments in code, updating the project board, tool documentation
Documentation will be updated at minimum every two weeks