2 Draft a Contract

You will recognize most of this section from CS 350. Your team’s first task is to draft a Team Contract.

Your contract must contain the following…

1. Contact information for each member:

   • name
   • ODU email address
   • GitHub username

2. Expectations for each other. These may vary considerably from one team to another, depending on what you consider to be most important.

Start your discussion with the following expectations..

• Each member will attend any meetings called during the above-listed available times with prior notice of at least 48 hours.

• Should a member be unable to attend a meeting, that person will notify all team members promptly (be sure to define promptly).

• All team members will use email/discussion board/Discord/Teams/Slack for team communications.

• Each member will do their share of the group’s work.

• Team members will respond to email/posts within 24 hrs on weekdays, 48 hrs on weekends.

• Team members will be professional and respectful of one another in all communications.

• No team member will allow more than a week to lapse without making some substantive & visible contribution to the project.

• Work that only exists on a person’s own PC or in a person’s own directories does not qualify as visible.

• Each member will complete their assigned tasks by no later than 48 hours before an assigned deadline.

3 Your Tasks

1. Reach out to your team.

2. Determine how your team will communicate this semester.

3. Draft your team’s contract.

4 Submission

Once you team has completed the Team Contract… navigate to Canvas and individually submit a URL that allows access to your team’s contract.

Note… everyone must submit the URL. This will serve as your agreement to abide by all expectations set forth by you and your team.