We, all the members of team 3 (need a team name) , Alexandria Wood, David Abasta, Fengyu Cao, Jie Jin, Justin Alford, Richard Rodriguez, and Tony Kaloutian, unanimously agree to the following rules for the Business Gateway 6:30 pm class in Summer session 3 of 2010.
A. Code of Conduct
As a Gateway class project team, we are all determined to follow the Code of Conduct:
1. Strive to complete all assigned tasks before or by deadlines (delete "or by", I think..what do you think?)
2. Complete all tasks to the best of his/her ability.
3. Work proactively, progressively and efficiently, being fully prepared before all meetings and anticipating potential problems.
4. Set aside personal goals to behave with the team’s good in mind. Keep minds open, listen to all different opinions objectively, and provide thoughtful evaluations of information.
5. Always keep other members informed of information or corrections related to the project.
6. Read and evaluate carefully all team assignments and provide necessary corrections.
7. Work will be divided equally among team members.
8. Maintain agreed project plan and other priorities.
B. Attendance Policy
1. All group members are required to attend at least one meeting every week: Monday, Tuesday or Thursday from 3:15pm to 6:15pm.
2. Meeting Dates and time will be announced at the end of every meeting based on each team members schedule for the following week.
3. If a team member is late or absent to a meeting, he or she will be given a warning and points deducted from the team evaluation. (It might be better to put specific rules of how many points will be deducted, since on the Course Pack P21 says, “Are the rules specific or too general?”)
4. Exceptions may be permitted only if a member has a reasonable excuse and calls every other team member at least one (1) day prior to inform them that they will not be able to attend the group meeting so they will be prepared to make sure that the project will be fully finished on time. (This part I'm sort iffy about..we need to reword this perhaps)
C. Communication Policy
1. All the team communications will be done through: in person meetings, phone calls, email, Google calendar, Wikispaces, Facebook group, and text messages.
2. Each team member is responsible to check all above mentioned communications daily. If the team is waiting for a response from a team member, he or she must reply back within 24 hours to avoid delays in projects.
3. Each team member is encouraged to visit the team’s designated Wikispaces page and or Facebook group page as often as possible and post regular posts. Posts may be an encouraging opinion regarding another team member’s work, discussion on a new idea, release of frustration, positive criticism etc.
4. In case of an emergency, team members must make at least one (1) complete and successful (good job on adding successful) contact with any of the other group members and tell the member what assignment you have, and make sure others will be able to finish the project on time.
5. If the person is in the middle of an emergency, and is not able to make any phone calls, the person has to show the proof after.
6. If the person does not attempt to make any connection and also fails to finish his or her assignment, he/she will be given a warning and points deducted from the group member evaluation score.
D. Conflict Resolution Procedures
1. All the conflicts shall be communicated with the entire team; the parties involved will then be given five minutes to make their respective cases. (Isn't this part just for the voting?) (Not really, since we need specific procedures to handle conflicts.)
2. The remaining team members will then carefully evaluate the evidence provided. If the majority of these agree on a certain course, this opinion shall be accepted by the team.
4. If the majority cannot be reached, the member who is majoring this subject will have final authority (i.e., Finance student regarding Finance-related conflicts)
5. All team members shall agree and respect the final decision.
6. Unprofessional manners and disrespectful conduct (such as, but not limited to yelling, name calling, offensive language, and fighting) are absolutely banned. These violations will lead, at a minimum, to a deduction from the member's evaluation score.
E. Voting Rules
1. All the decisions shall be agreed on by the majority of team members.
2. If the majority cannot be reached, the member majoring the certain major has the authority to make the final decision.
3. All team members shall agree and respect the final decision.
F. Team Contact Person
1. Justin Alford will be the person who will contact the instructor on behalf of the team.
G. Unmet Expectations:
When team members fail to live up to the above expectations, it is important that the group as a whole not be dragged down by their lack of responsibility. Therefore:
1. Any member who misses 2 meetings, assignments or other key elements of the team effort shall be deemed to have failed to meet the expectations agreed to above.
2. The penalty for this failure is expulsion from the group, with whatever consequences that might entail.
Your signature below confirms that you have read and agreed to these terms. If you don’t plan to abide by them, advise your group and don’t sign. Any modification to this contract needs to be done by an addendum and must be approved and signed by all team members.
We, the undersigned, have read and understood all of the above terms and conditions and agree fully to abide by them or accept the consequences set out above.
Team 3 Rules of Behavior
We, all the members of team 3 (need a team name) , Alexandria Wood, David Abasta, Fengyu Cao, Jie Jin, Justin Alford, Richard Rodriguez, and Tony Kaloutian, unanimously agree to the following rules for the Business Gateway 6:30 pm class in Summer session 3 of 2010.
A. Code of Conduct
As a Gateway class project team, we are all determined to follow the Code of Conduct:
1. Strive to complete all assigned tasks before or by deadlines (delete "or by", I think..what do you think?)
2. Complete all tasks to the best of his/her ability.
3. Work proactively, progressively and efficiently, being fully prepared before all meetings and anticipating potential problems.
4. Set aside personal goals to behave with the team’s good in mind. Keep minds open, listen to all different opinions objectively, and provide thoughtful evaluations of information.
5. Always keep other members informed of information or corrections related to the project.
6. Read and evaluate carefully all team assignments and provide necessary corrections.
7. Work will be divided equally among team members.
8. Maintain agreed project plan and other priorities.
B. Attendance Policy
1. All group members are required to attend at least one meeting every week: Monday, Tuesday or Thursday from 3:15pm to 6:15pm.
2. Meeting Dates and time will be announced at the end of every meeting based on each team members schedule for the following week.
3. If a team member is late or absent to a meeting, he or she will be given a warning and points deducted from the team evaluation.
(It might be better to put specific rules of how many points will be deducted, since on the Course Pack P21 says, “Are the rules specific or too general?”)
4. Exceptions may be permitted only if a member has a reasonable excuse and calls every other team member at least one (1) day prior to inform them that they will not be able to attend the group meeting so they will be prepared to make sure that the project will be fully finished on time. (This part I'm sort iffy about..we need to reword this perhaps)
C. Communication Policy
1. All the team communications will be done through: in person meetings, phone calls, email, Google calendar, Wikispaces, Facebook group, and text messages.
2. Each team member is responsible to check all above mentioned communications daily. If the team is waiting for a response from a team member, he or she must reply back within 24 hours to avoid delays in projects.
3. Each team member is encouraged to visit the team’s designated Wikispaces page and or Facebook group page as often as possible and post regular posts. Posts may be an encouraging opinion regarding another team member’s work, discussion on a new idea, release of frustration, positive criticism etc.
4. In case of an emergency, team members must make at least one (1) complete and successful (good job on adding successful) contact with any of the other group members and tell the member what assignment you have, and make sure others will be able to finish the project on time.
5. If the person is in the middle of an emergency, and is not able to make any phone calls, the person has to show the proof after.
6. If the person does not attempt to make any connection and also fails to finish his or her assignment, he/she will be given a warning and points deducted from the group member evaluation score.
D. Conflict Resolution Procedures
1. All the conflicts shall be communicated with the entire team; the parties involved will then be given five minutes to make their respective cases. (Isn't this part just for the voting?) (Not really, since we need specific procedures to handle conflicts.)
2. The remaining team members will then carefully evaluate the evidence provided. If the majority of these agree on a certain course, this opinion shall be accepted by the team.
4. If the majority cannot be reached, the member who is majoring this subject will have final authority (i.e., Finance student regarding Finance-related conflicts)
5. All team members shall agree and respect the final decision.
6. Unprofessional manners and disrespectful conduct (such as, but not limited to yelling, name calling, offensive language, and fighting) are absolutely banned. These violations will lead, at a minimum, to a deduction from the member's evaluation score.
E. Voting Rules
1. All the decisions shall be agreed on by the majority of team members.
2. If the majority cannot be reached, the member majoring the certain major has the authority to make the final decision.
3. All team members shall agree and respect the final decision.
F. Team Contact Person
1. Justin Alford will be the person who will contact the instructor on behalf of the team.
G. Unmet Expectations:
When team members fail to live up to the above expectations, it is important that the group as a whole not be dragged down by their lack of responsibility. Therefore:
1. Any member who misses 2 meetings, assignments or other key elements of the team effort shall be deemed to have failed to meet the expectations agreed to above.
2. The penalty for this failure is expulsion from the group, with whatever consequences that might entail.
Your signature below confirms that you have read and agreed to these terms. If you don’t plan to abide by them, advise your group and don’t sign. Any modification to this contract needs to be done by an addendum and must be approved and signed by all team members.
We, the undersigned, have read and understood all of the above terms and conditions and agree fully to abide by them or accept the consequences set out above.
Signatures:
Alexandria Wood
Date:
David Abasta
Date:
Fengyu Cao
Date:
Jie Jin
Date:
Justin Alford
Date:
Richard Rodriguez
Date: