55 Knots has created the following guidelines for project roles, meeting procedures, communication, generation and submission of assignments, and team conduct. These guidelines represent the standards to which we have agreed to hold ourselves, both individually and as a group, as well as the consequences for failing to meet those standards.
Project Roles
Project roles are based on each team member's particular skills, and will persist over the course of the entire project. Specific project tasks relating to assignments will also be assigned on the basis of these skills.
Client Liaison: Jordan
The client liaison will be responsible for all communication with the Gale Project contact, Elaine Engstrom.
Backup: Silhee-
Instructor Liaison / Photographer: Silhee
The instructor liaison will be responsible for submitting final drafts of all assignments and responsible for communicating with Mick (instructor).
Backup: Josh -
Webmaster: Josh
The webmaster will be responsible for creating the website, uploading new information, maintaining it, handling technical difficulties.
Backup: Jordan -
Project Manager: Jordan
The project manager will be responsible for facilitating meetings, assigning and coordinating tasks, and managing the group basecamp in Ctool site.
Backup: Josh
Milestone Leaders:
- Milestone 1 - Project Focus: Jordan
- Milestone 2 - Contextual Inquiry: Silhee
- Milestone 3 - Personas and Scenarios: Jordan
- Milestone 4 - Lo-Fi Prototype: Josh
- Milestone 5 - Hi-Fi Prototype: Josh
- Milestone 6 - Final Presentation: Silhee
Meeting Procedures
- Team meetings will take place every Sunday at 10:00 a.m. at DIAD lab or Shapiro library.
- Meetings will last about 3 hours. If meetings last beyond this point, the team will schedule an emergency meeting for that week. The project manager will be responsible for determining the exact time and location of the emergency meeting, and communicating that information to the team.
- Meetings will follow the agenda set and distributed by the meeting manager.
- The meeting manager will take the minutes of the meeting and distribute them to the other members of the team following the meeting.
- Meetings will end with the meeting manager reading individual assignments to be completed prior to the next meeting. This information will also be included in the meeting minutes.
Communication
- The primary means of communication among team members will be e-mail; all team members will agree to utilize a g-mail account for this purpose.
- Team members will respond to any e-mail that they receive within 12 hours.
- Team members will coordinate their schedules using a shared Google Calendar.
- If a team member cannot attend a meeting because of unforeseen circumstances, he or she will contact the meeting manager via text message as soon as possible. He or she will also submit any assignments in progress to the meeting manager as soon as possible. The meeting manager will then inform the rest of the team and distribute the assignment among the other team members.
Code of Conduct
- All team members are expected to proactively and productively contribute their unique talents to the project.
- Be open to the ideas of others; at the same time, be willing to express concerns and dissent; focus critiques on ideas, not on other team members.
- Address conflict directly with the team member with whom you disagree. Do not critically discuss a team member with the rest of the team when that member is not present.
- Address conflict when it occurs to avoid the build-up of frustration and resentment.
- Be punctual; contact team members if you are running more than 10 minutes late.
- Be as flexible as possible to accommodate the needs of the group as a whole.