Together Each Achieves More <br />“TEAM Constitution”<br />
Article I: Name<br />The name of this Baker University Academic Collaboration is Together-Each-Achieves-More.<br />The acronym “TEAM” shall be used as a shortened form to refer to this group. <br />
Article II: Purpose<br />The purpose of the Baker University Academic Collaboration is to provide students with opportunities for personal, academic and professional development. The Articles set fourth will help further provide the TEAM with clear expectations for all TEAM activities.<br /><ul><li>In order to attain these goals, the TEAM shall do the following:
Attend and participate in scheduled team meetings.
Share individual experiences and perspectives on lesson topics.
Create an open forum that will allow ideas to be discussed.</li></li></ul><li>Leader<br /> Will be responsible for TEAM Conferences (setting time and date, and creating agenda) This role has been given to Jeremiah Sterling<br /> <br />Organizer<br /> Will be responsible for collecting all contributions for projects and placing them in the appropriate format. This person will then submit the project and make it available for all members of TEAM. This role has been given to Brittany LaChance<br /> <br />Timekeeper<br /> Will be responsible for remind members of TEAM of set conferences, project due dates and making sure everyone is contributing and is on task. This role has been give to John Becker<br /> <br />Recorder <br /> Will be responsible for recording events and communications for TEAM. This will include but not be limited to agendas, minutes and documents. This person will have an alternative storage location for this data in the event of a technology failure. This role has been given to Jason Cummins. <br />Interim <br /> In the event that any other member of TEAM can not perform their roles, this person will take their role temporally. This role has been given to Ken Panchy<br />Article III: Membership<br />
Attendance<br /> All team members will be required to attend meetings, attendance is not optional.<br />Place<br /> All meetings will take place on the ‘Conference’ page designated on the BakeruTeam website. <br />Agenda<br /> Meetings will have an agenda with time allocated to each agenda item.<br />Promptness<br /> Meetings will start at designated time. If the meeting time expires before all agenda topics are discussed a vote to continue the meeting or reschedule a follow up shall take place.<br />Participation<br /> All team members are expected to contribute during meetings.<br />Minutes<br /> The recorder will take meeting minutes and will distribute the minutes to every member of TEAM and the adviser for the class, via e-mail.<br />Consequences<br /> If any member doesn't participate in 3 mandatory conferences (without a legitimate reason), miss 3 deadlines or doesn't contribute you will be dropped from the group at the end of the course. <br />Article IV: Meetings<br />
Each team member will abide by what the team and team-leader have set fourth to ensure that all tasks have been completed in a timely manner.<br />If for some reason there isn’t enough time to complete the task or the task will be running late, the member will inform the rest of the team prior to the assignment being due.<br />Article III: Assignments<br />Article IV: Meeting Place<br />The team leader or designated team member will provide a pre-determined meeting place where the Team will meet .<br />The team leader or designated team member will inform all team members whenever there is a change in to the meeting place.<br />
The Group shall not carry on any other activities not permitted to be carried on by the instructor associated with this class or by Baker University.<br />Article V: Operational Limitations<br />Article VI: Document Collaboration<br />All documents will be submitted on the ‘Document’ page of the BakeruTeam website. <br />All comments on the submitted documents will be done in a mature and constructive manner. If comments are found to be otherwise, they will be submitted to the Leader of TEAM and to the advisor for the class. In the event that the Leader is submitting such comments, the advisor for the class will be informed.<br />
If any member of TEAM has a conflict with another member, in aspects of interest and developmental conflicts, the member needs to write a paragraph explaining honestly (a) what they want and (b) how they feel, (c) explain interests as well as positions, (d) take the opposing perspective, (e) create a number of optional agreements that maximize joint outcomes, and (f) reach agreement on one of the options. <br />This paragraph needs to be submitted to the Leader of TEAM (if the conflict is with the Leader then it should be submitted to another member) and to the advisor assigned to the class. <br />When the conflicting members cannot successfully negotiate a constructive resolution to their conflict, a mediator will be available. Said mediator will either be the Leader or the advisor assigned to the class).<br />Article VII: Conflict Resolution<br />
This Constitution will be available on the BakeruTeam website and the class forum. This Constitution will also be distributed to every member of TEAM and the advisor for the class. This Constitution will be accessible to all members of TEAM throughout the duration of the degree program.<br />Article VIII: Constitution Availability<br />Article IX: Assignments<br />All members of TEAM will be assigned a portion of a project and will be responsible for their task. If a member can not complete their task they need to let the Leader of TEAM no and ask another member to complete it for you. Please note that if this happens, this situation too will be involved in your Individual Evaluation.<br />
TEAM will be using Wetpaint for their website host. The website is to be called BakeruTeam and will be used for project completing and TEAM communication. All members of TEAM have the ability to edit pages and threads.<br />Article X: Website<br />Article XI: Team Evaluation<br />After every project each member of TEAM will evaluate the project and their contributions. They will then come up with ideas on how to better their performance. This will be done either via TEAM conference or via email.<br />
Article XII: Individual Evaluation<br />Every member of TEAM has been notified and understands that each member is being evaluated by every member of TEAM. Each contribution and interaction with the TEAM will be evaluated. <br />Article XII: Governance<br />This constitution is based on the terms of the Baker University Learning Team Handbook. <br />
Article XII: Amendments<br />Any attempts to amend this constitution must be brought before All TEAM members. The members shall ensure the proposed amendment is within the guidelines of Baker University Learning Team Handbook. The membership shall then vote on the proposed amendment, and a majority vote shall constitute adoption of the amendment, which shall then be added to the constitution.<br />TEAM is a legitimate Learning Team approved by the advisor of the course and Baker University throughout the duration of the degree program.<br />