Team Covenant
The Team Covenant outlines how the group will function, communicate and govern itself.
In this covenant, our team defines the communication protocols, meeting times, and rules for team participation that we will use. We all agree to abide by these rules as set forth below, and accept the consequences specified if not followed.
Meeting Times & Agreements
- Team meetings will take place on Wednesdays from 6 pm to 9 pm at SI Student Lounge. This time can be changed on a week-to-week basis if needed, as long as all members agree and are aware of the change.
- Meetings will begin at the scheduled meeting time; members are expected to arrive early or on time as we will not wait for everyone to arrive before beginning.
- All meetings will follow the following format:
- Review of agenda
- Follow-up on progress of previous meeting's action items
- Meeting business
- Compilation of action items
- Members are expected to come to each meeting prepared and with their assigned action items completed.
Team Member Roles
- Debra will be the project manager, responsible for setting meeting agendas, keeping meetings on topic, and maintaining the Basecamp site. She will email meeting agendas 24 hours in advance of all meetings, and put action items in Basecamp within 4 hours after meetings.
- Sang will be the notetaker, responsible for taking meeting notes and sending an email directly after each meeting with action items.
- Andrea will be the website manager, responsible for putting milestones and other materials on the website.
- Noah will be the client liaison, responsible for sending emails to Local Orbit and getting materials to them or from them when necessary.
- Amy will be the faculty liaison, responsible for emailing/talking with Professor McQuaid when necessary.
Communication Agreements
- Team members agree to check email at least once a day, and respond to all emails that need responses within 24 hours. (Noah will not be checking email or phone messages between Friday night and Saturday night.) Emails will be the primary contact method, though phone calls are also fine.
- If a team member cannot attend a meeting, they should notify the entire team ahead of time by email and give their materials to one of the group members ahead of time. If a team member misses two meetings without giving notice, they must email Professor McQuaid and admit responsibility for letting down the team. If a team member misses three meetings, they will be kicked out of the group.
- If a team member cannot complete one of their responsibilities by the due date assigned, they are responsible for notifying the team at least 48 hours before it is due, and make arrangements for how it will be completed. The first time this happens without telling the team, no action will be taken. The second time, the team member must email Professor McQuaid and admit responsibility for letting down the team. The third time, the team member is kicked out of the group.
- Debra will not be attending class, and will not be responsible for writing any text to go on the website for the milestones.
Milestone Leaders
We have decided to appoint a 'Milestone Leader' to lead each of the milestones. This team member will be responsible for doing the planning of how that milestone's tasks will be carried out, initiating the documents and deliverables necessary for that milestone, and writing the text to go on the website.
We have assigned the responsibilities as follows:
- Contextual Inquiry - Debra
- Personas - Sang
- Lo-Fi Prototype - Noah
- Scenarios - Amy
- Hi-Fi Prototype - Andrea
- Final Project Presentation - Group effort