The Website of Team 14.
ECE 3400, Fa 2018 Team # 14
Team Members: David Burgstahler (dfb93), Gregory Kaiser (ghk48), Andrew Lin (yl656), Michaelangelo Rodriguez Ayala (mr2242)
Day, time, and place for regular team meetings:
Preferred method of communication (e.g., e-mail, cell phone, wired phone, Blackboard Discussion Board, face-to-face, in a certain class) in order to inform each other of team meetings, announcement, updates, reminders, problems:
Decision-making policy:
We will come to team decisions by majority rule, meaning that a proposed agenda idea approved by at least 3 members will be treated as group consensus.
Method for setting and following meeting agendas (Who will set each agenda? When? How will team members be notified/reminded? Who will be responsible for the team following the agenda during a team meeting? What will be done to keep the team on track during a meeting?):
We will have a shared google document to list and manage our meeting agenda. Any member can add agenda items before the meeting. The team leader will manage this document.
Method of record keeping (Who will be responsible for recording & disseminating minutes? How & when will the minutes be disseminated? Where will all agendas & minutes be kept?):
Meeting minutes will be recorded in the agenda document. All team members are responsible for notating any meeting results in the shared google doc under the relevant agenda item.
Work Quality:
Project standards (What is a realistic level of quality for team presentations, collaborative writing, individual research, preparation of drafts, peer reviews, etc.?):
Team Participation:
Strategies to ensure cooperation and equal distribution of tasks:
Tasks should be distributed initially at meetings. Labs will act as check-ins on these tasks where we can collaborate/help each other complete certain tasks. Expected in-lab tasks will be designated beforehand during meetings.
Strategies for encouraging/including ideas from all team members (team maintenance):
Any new ideas or changes to the project plan should be proposed at team meetings. Members can then weigh in on these ideas, suggest modifications, and vote on the final plan. At meetings, we will make sure there is a clear plan with tasks for all team members before going forward with independent work or lab/team work.
Strategies for keeping on task (task maintenance):
During labs, we will check in with each other’s progress. Labs will be the time to make any small changes to the agreed-upon agenda and providing team assistance on any critical tasks. In addition, if a team member is struggling he should message the rest of the team asking for help/guidance/re-assignment.
Preferences for leadership (informal, formal, individual, shared):
Leaders for general areas of work will have to emerge organically since we are unaware of skills in which we perform best. If someone is responsible for a task, they are de facto leader of that task so changes to a mechanism or code related to that task must be run by that person.
Personal Accountability:
Expected individual attendance, punctuality, and participation at all team meetings:
Team members will commit to arriving at planned team meetings 5 minutes early. A person who arrives up to 10 minutes late with a lame excuse more than once will get a stern talking to.
Expected level of responsibility for fulfilling team assignments, timelines, and deadlines:
Once we set timeline, team members are responsible for delivering by this timeline consistently. Timelines should allow time for trial/error & team collaboration. Each individual is expected to communicate clearly about progress on a task, and about whether or not it will be completed on time.
Expected level of communication with other team members:
ny planned meeting/lab work time conflicts should be made known as soon as possible, with at least 24 hours of notice to all team members via group chat or email.
Expected level of commitment to team decisions and tasks:
Team members will commit to any plans agreed upon by group consensus, including attendance of team meetings and deadlines for project tasks. Any disagreements with such decisions must be brought up during team meetings.
Consequences for Failing to Follow Procedures and Fulfill Expectations
Describe, as a group, you would handle infractions of any of the obligations of this team contract:
Team meeting will commence with all members present at the indicated start time, and late members will forfeit their ability to dispute any consensus made in their unexcused absence. On the homepage of our website, we will have a scoreboard to keep track of the number of late arrivals to meeting and/or late deadline deliveries.
Describe what your team will do if the infractions continue:
A dunce cap (or another piece of identifiable clothing, yet to be constructed) will be worn by those who commit multiple offenses against this contract. It shall be worn during team meetings for a duration chosen by the rest of the team, based on the number of infractions. The “dunce” shall be responsible for the article of shaming clothing, and it shall be returned to the team bin when time has been served.
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:
Week 1-4 (Start-up, Lab 1, Milestone 1): David
Week 5-8 (Lab 2, Lab 3, Milestone 2): Greg
Week 9-12 (Lab 4, Milestone 3): Andrew
Week 13-16 (Milestone 4, competition, final report): Michael
a) I participated in formulating the standards, roles, and procedures as stated in this contract. b) I understand that I am obligated to abide by these terms and conditions. c) I understand that if I do not abide by these terms and conditions, I will suffer the consequences as stated in this contract.
1) David Burgstahler date: 8/31/18
2) Michaelangelo Rodriguez date: 8/31/18
3) Gregory Kaiser date: 8/31/18
4) Andrew Lin date: 8/31/18