Members: Brian Richard, Eric Lei, Kenneth Fang, Tyler Sherman
Team Procedures
Preferred method of communication:
Slack → will be used for all logistics and questions
In person → will be used for major design decisions and reviewing progress
Decision-making policy:
By consensus
All topics will be thoroughly discussed before a decision is made
Method for setting and following meeting agendas:
Current “Team Leader” will create and post meeting agenda in Slack and the meeting minutes document
“Scribe” will record the meeting minutes in the document on Google Drive
This position will be randomly selected and will rotate every week
To help keep the team focused during meetings, time will be alloted for breaks
This is especially true during our 3-hour lab session
All team members should feel comfortable to take a break as needed
Team members are responsible for speaking up if someone seems like they aren’t
taking enough breaks (and their productivity has suffered) or if they’re taking
too many breaks
At the end of each meeting—whether it be for technical work or logistics—the
logistics for the next meeting will be discussed and anticipated work will be
distributed and recorded on the “Tasks” document on Google Drive
Method of record keeping:
Designated Scribe for the meeting is responsible for recording and disseminating meeting minutes
Meeting minutes will always be kept in the shared folder on Google Drive (link also available on the team website)
Agendas and minutes will be kept in the same Google Drive document
Meeting Times:
Weekly → 11:15 - 12:05 PM on Fridays in Upson Hall 142
Weekly → 7:30 - 10:30 PM on Thursdays in Phillips Hall 427
As Needed → 10:00 - 12:00 PM on Saturdays in Phillips Hall 427
Always consult the Slack channel for special circumstances or questions
Team Expectations
Work Quality:
All work must be completed by the deadline set out by the team
This doesn’t mean don’t ask for help. Quite the contrary, ASK for help immediately if you don’t understand what your assigned to work on or need extra assistance
Consequences for failing to meet deadlines or attend meetings include having to bring snacks to the next team meeting and addressing what steps will be taken to prevent this from occurring again
All new code needs to be reviewed by at least one other person
Majority of code should be written using pair programming
All code should be concise and heavily commented
All files should be uploaded to the Google Drive folder or GitHub repository to preserve revisions and make accessibility easy
Team Participation:
Current Team Leader will be responsible for ensuring all members remain on task and on schedule and that all meetings are productive and accomplish the goals outlined in the agenda
All team members are expected to actively participate during team meetings
This includes: proposing ideas, pointing out issues, asking questions, and updating the group on the status of your current work
All tasks assigned to each team member will be clearly outlined in the meeting notes, as well as in the “Tasks” file on Google Drive
Team leader is responsible for ensuring all team members are comfortable with their work distribution and for altering assignments if necessary
Personal Accountability:
Team members are expected to punctually attend and participate at all meetings
Being a few minutes late (5 to 10 minutes) is fine if accompanied by a message in Slack
Any additional tardiness should come with advanced notice (>24 hours in advance)
You are responsible for completing the tasks for which you have been delegated, within the time window the team has defined
This project is representative of all of the group members as a whole
You are expected to take your work seriously as it is a reflection of the entire team
Team members are expected to respond to all Slack messages (or other forms of communication) as soon as reasonably possible
Always send some sort of acknowledgment to show you read and understood a message
Only commit to what you can reasonably achieve
If for some reason you are unable to complete your obligations, take responsibility for that and talk to the team about re-allocating work
Recognize team design decisions are where the efforts of all members will be focused
Voice concerns and tradeoffs during design meetings, but once a decision has been made, team members should support it until it is finished, or a flaw is discovered
Consequences for Failing to Follow Procedures and Fulfill Expectations:
Infractions of any of the obligations of this team contract will be addressed as soon as possible (at the next team meeting)
That being said, we are a team and our goal is to support one another
We will utilize constructive criticism and task conflict, not relationship conflict
The person at fault is responsible for bringing this up and outlining how this will be avoided in the future
If infractions continue, we will schedule a full team meeting with Professor Kirstin and/or a TA and/or Rob Parker to give people an opportunity to voice their opinions and resolve this conflict
Team Leadership
Every person on the team will have to take the role as a leader.
The role of the leader will be to organize meetings and make sure that
everything is submitted in a timely manner. Please note here who will
be responsible when:
Weeks 1 - 4 (Startup, Lab 1, Milestone 1)
August 23 - September 14
Kenneth Fang
Weeks 5 - 8 (Lab 2, Lab 3, Milestone 2)
September 17 - October 12
Eric Lei
Weeks 9 - 12 (Lab 4, Milestone 3)
October 15 - November 9
Brian Richard
Weeks 13 - 16 (Milestone 4, Competition, Final Report)
November 12 - December 4
Tyler Sherman
Signed
I participated in formulating the standards, roles, and procedures as stated in this contract
I understand that I am obligated to abide by these terms and conditions
I understand that if I do not abide by these terms and conditions, I will suffer the consequences as stated in this contract
This contract is understood to be a living document that will be amended as necessary, however, only with the entire group present