Team Working Agreement
Term (Autumn 2020)
Creation 9/2/2020 (Updated 11/8/20)
1) Group Identification
Lab section # – 11598
Table # – L
Instructor – Dr. Deborah Grzybrowski
Team Name (Optional) –
Team member info:
| NAME: | EMAIL: | PHONE: | OTHER: |
| Ben Zimmerman | zimmerman.808@buckeyemail.osu.edu | 419-631-0930 | |
| Ramsay Johnson | Johnson.8809@buckeyemail.osu.edu | 630-414-5343 | |
| Kyle Borah | borah.11@buckeyemail.osu.edu | 440-901-9424 | |
| Zack Alleman | alleman.26@buckeyemail..osu.edu | 614-600-4289 | |
2) Primary Means of Communication and Expectations
State your team’s agreed upon various means of communication and expectations for response.
(Example: All members will be expected to read emails from anyone in the group on a daily basis and respond in less than 12 hours.)
3) Scheduling of Meetings (Schedule at least one meeting as part of constructing your team agreement.)
Agreed upon means of scheduling meetings.
| Date: Sundays weekly | Time: 4:00 PM | Location: Online |
Participating members (If not all.): Everyone
Agenda:
Group will discuss major courses of action together, and then volunteer for actions for the week. Ramsay will present a productivity chart for the group, and assign responsibilities if necessary.
4) General Responsibilities for All Team Members
This element of the team working agreement is the list of rules/agreements or the contract that all members agrees to live by.
- Show up on time to team meetings.
- Create a productive work environment during Friday labs.
- Show up on time to class lectures.
- Be faithful to communication with other group members.
- Submit work in a time suitable and and a manner representative of the group.
- Be thoughtful and considerate to your fellow group members in discussions.
5) Specific Team Member Responsibilities/Deadlines (If applicable)
This section may be used to record specific tasks or responsibilities particular team members have assumed.
Example Statement:
- Team member Kyle Borah will be in charge of group communication and meeting scheduling.
- Team member Ben Zimmerman will take responsibility for software analysis and take care of the technological aspects of the group.
- Team member Ramsay Johnson will be the productivity manager, will create GANTT charts and help direct other members as needed.
6) Conflict Resolution
While conduct in the group is expected to be of a considering and professional manner, it is recognized that sometimes conflict is inevitable. Below is stated the terms of how such will be resolved.
- If there is a disagreement in how the group is to move forward, the group will go to vote after each side makes a plea for their case, with the winning side moving forward undisputed. If there is a tie, Kyle Borah will act as a tie breaker.
- If the conduct of a member is determined to be unacceptable (unprofessional, inconsiderate, or careless), members will be warned twice, before being reported to the instructor.
- If a member of the group needs to take an unexpected leave, or otherwise cannot participate in normal functions for the group, they will need to report their situation to Kyle Borah.
7) Expectations of Faculty and GTA’s
The only expectation of faculty and GTAs is to be fair and just in their handling of cases as reported by the group.
8) Team Signatures
Signature for each student is to be included.
Ben Zimmerman
Zack Alleman
Ramsay Johnson
Kyle Borah