# Team Contract

# Description

Create a team contract that outlines the goals and commitment of each team member to the project. It should be aspirational, outlining the goals and commitment the team is making to create the best possible app while also being realistic and spell out clear and fair rules for the team.

There is no required team contract structure or template. Each team should create a contract that works for their team dynamic. However, here are the basics to consider when writing the contract:

• Team goals
• Team expectations in regards to...
  • attendance (class time, internal team meetings, client meetings, etc.)
  • communication (slack, email, internal communication, client communication etc.)
  • conflict resolution (disagreements, team members not contributing, etc.)
  • task completion (deadlines, quality, etc.)
  • internal meeting structure (do you have set internal team meetings? Do you only meet when necessary? etc.)
  • ...any other expectations your team wants to include
• Team policies for when a the contract is broken
  • What kind of consequences or restorative measures are required?
    • Example: if someone misses a meeting, the next time they supply team coffee
  • What steps are taken to support the team member(s) so the issue is not repeated?
  • ...any other policies your team wants to include

Once the contract is written, reviewed with Adam and Adesh, and agreed upon by all team members, all team members sign their name at the bottom on the contract.

# Submission

Create your contract as a Google Doc in the appropriate folder in your team's Google Drive. Copy a link to the contract into Azure DevOps.