- Tek - Key strengths include design, front-end
- Cullen - Key strengths include communication, documentation
- Louis- Key strengths include leadership skills, project management
- Sunny - Key strengths include adaptability, communication
We as a team utilize these strengths to create our vision into reality. We are committed to user experience by clear communication and an understanding of code flow.
- Tek - Better communication
- Cullen - Team spirit
- Louis - Technical skills
- Sunny - Tool knowledge
- We utilize Notion to keep track of due dates and todos
- We will meet Monday - Friday 9AM to discuss progress for the project before implementation.
- We will meet back up again around 5PM for code review, discussion, and final pull requests.
- For communication we will utilize Slack for day to day operations.
When conflict arises, we will first and foremost communicate and gather a solution. If conflict escalates we will reach out toa third party member such as a TA or the instructor to mitigate our conflict and come to a uniform solution.
Each team member will contribute and contributions made by each team member will come from constant communication and a check-up to see what has been done. If any team member finds that there is no work to be done, we will discuss what needs to be done and the team member will contribute to work that can be done.
Each team member will come to a uniform understanding in a technical and and skill level standpoint through constant communication and sharing references to documentation. In the event that there is no understanding of all team members, that is the time to reach out to a third party such as a TA or an instructor for clarification. We will give ourselves a 15-30 min time-frame to figure a solution without third party intervention.
For team members not adequately contributing, communication is the first step in determining if this team member is currently struggling with something, before assigning a role to that team member.
Unsuccessful conflict resolution will result with a third party intervention from a TA or an instructor to find the adequate solution
Hours of operational communication will be from 9AM to 5PM, via Slack messaging, Zoom break-out rooms, or a table in Remo. If a team member is working after or before hours, communication will be done through Slack messaging and then CAN escalate into a video conference.
Breaks will be performed at the top of each hour and general lunch time will be at 12PM and is flexible dependant on work load.
A strategy to include everyone will be with constant communication and a review from each team member. All voices will be heard and an agreement from all team members must be done in order to progress.
This is a safe environment, so if there is anything that will potentially offend, we will ensure that each topic that is discussed is done so in a professional manner. Discrimination is not tolerated.
To be able to merge onto the main branch of a repository, 1 team member MUST approve the code. There will be a merge branch before it is merged onto the main branch where it will be merged at the 5PM meeting after code review and discussion.