Skip to content

Latest commit

 

History

History
122 lines (63 loc) · 3.45 KB

TeamContract.md

File metadata and controls

122 lines (63 loc) · 3.45 KB

Team Contract


This Contract is the Final Version from the old repository "team-project"(link: https://github.com/Hwwv/team-project.git), where you can find people's commits for signing it.

Purpose of this Contract

This contract sets out shared expectations and commitments for how our team will collaborate during the course. It is designed to promote accountability, professionalism, and mutual support as we complete individual preparation, readiness assurance tests, in-class activities, and our course project.


Team Norms and Expectations

Communication

■ Use Discord as the primary communication channel

■ Respond to messages in at most 24 hours

■ Let others know if you need help/updates on how work is going as soon as possible

■ All communication will remain respectful, professional, and constructive

■ Weekly check-in for work (through Discord or Google Meet)

■ Let others know if you need help/updates on how work is going as soon as possible

■ Weekly check-in for work (through Discord or Google Meet)


Attendance

■ Let everyone know through Discord before the day of the lecture/lab if you cannot attend.

■ Participate fully through labs/lecture unless there is a reasonable excuse (communicate 24 hours before)

Preparation

■ Read through the labs instructions before labs

■ Do readings for TRAT’s

■ Go through the non-necessary (not-for-credit) self-test for each module on Quercus

Independent and Collaborative work

■ All work done independently and collaboratively will be tracked through a Google Sheet file (Provided on Discord)

■ Track all GitHub commits and PRs through Google Sheet file (Provided on Discord)

■ If a change is worth noting, alert everyone about changing the README file

Quality of work

■ Describe in detail all the changes you have made in the PR request description

■ Alert the other collaborators you are working with through Discord to review changes

■ Once everything is approved by collaborators, the PR can be merged

■ Use Software design principles as a reference

Meeting

■ Weekly check-in meeting to go over task progress (in person/online), task delegation, and any issues

■ Partner/Entire group work sessions (Scheduled in advance)

■ Longer meetings to go over the difficult parts of the project (Scheduled in advance)

AI

■ Discourage the use of AI


Decision Making

■ Project direction and breaking down task decisions will be made by voting

■ Tasks will be delegated based on skills and preferences, or by someone responsible for delegating tasks


Conflict resolution

■ Listening to each other's side of the issue and attempting to reach a compromise. Consult a TA or instructor as a team if a resolution has not yet been reached.


Accountability

■ Consistently not following the team contract + consistent low quality of work will result in low peer evaluations

Responsibilities

■ Responsible for keeping track of task progress: Ava and Meilin

■ Responsible for delegating tasks and holding meetings: Jayla and Stephen


By signing below, we acknowledge that we have read, discussed, and agreed to these terms. We understand that this contract is binding for the duration of the course and may be revised with the agreement of all team members.

Team Member Signatures:

  • Ava Bidari
  • Muhammad Rafie
  • Qilin Zeng
  • Winston Liang (Winstonnub)
  • Meilin Han
  • Jayla Lee

Date: Oct 12, 2025