Team Standards

January 27th, 2010

The Bookmark Brigadiers

Mackenzie Boyd

Justin Hill

Forrest Guice

Table of Contents

1 Roles

1.1 Leader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.2 Communicator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.3 Recorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1.4 Facilitator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2 Meetings

2.1 Weekly Meeting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.2 Standard Agenda . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.3 Decision Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.4 Minutes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.5 Attendance Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

2.6 Conflict Resolution Strategy . . . . . . . . . . . . . . . . . . . . . . . . 2

3 Document Standards

3.1 Word Processor Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.2 Coordination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.3 Version Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.4 Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3.5 Review Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

4 Self Evaluations

4.1 Self Evaluation Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4.2 Self Evaluation Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

5 Group Interactions

5.1 Design Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

5.2 Meeting Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Roles

The roles listed below are not a final list of all the roles team members will be taking on, more this is a description of who is taking on these specific roles as there is significantly more work and roles which will be filled by team members.

1.1 Leader

Mackenzie Boyd, in charge of setting up meetings outside of standard times, divvying up tasks with team member input.

1.2 Communicator

Mackenzie Boyd, responsible for communications between team and client as well as communications between any other outside entities as necessary.

1.3 Recorder

Forrest Guice, take notes during meetings, distribute minutes afterwards.

1.4 Facilitator

Justin Hill, will work to resolve disputes and insure meetings stay on topic and cover necessary topics of discussion.

2 Meetings

2.1 Weekly Meeting

Weekly meetings will take place on Mondays at 11:20 am. If more time is needed for the meeting before people have to leave, Wednesdays at the same time can be used.

2.2 Standard Agenda

Meetings will start with an overview of how members did at the tasks assigned since the previous meeting. Any problems with the project or assignments can be brought up at this time to be discussed or noted for later discussion. Then, current assignments and solutions can be discussed openly among members of team. Finally, new assignments will be given out to each member based on the assignments due from the class schedule and what is currently being worked on with the software.

2.3 Decision Strategy

Decisions will be made with a general consensus of the group. A consensus will be reached by conducting a logical discussion about the decision. If the members can’t agree, a majority vote will be used.

2.4 Minutes

The team recorder will distribute the minutes for each meeting by the following day. The minutes will be distributed in the form of XHTML documents made available to team members through the project SVN and email. The minutes may be posted to the project website at a later date at the team leader's discretion.

2.5 Attendance Rules

Team members are expected to be on time to every scheduled meeting. Team members may miss a meeting by providing advanced warning but may not miss more than one consecutive week of meetings. Arriving slightly late to meetings is acceptable but team members who are very late or habitually late may be considered absent.

The team may file a complaint with the mentor against a team member who misses meetings without advanced warning if that team member is unable to sufficiently explain their absence. A complaint will also be filed in the event a team member becomes non-communicative by missing too many meetings regardless of warning.

2.6 Conflict Resolution Strategy

The team decision making process is consensus-based with disagreements settled by majority vote. Any interpersonal disputes between two team members will be arbitrated by the third team member. Non-participating team members will be contacted directly and given warning. Team members who attempt to change the project design without team consent will be lectured on the virtues of consistent design. All modifications to project design will be reviewed based on the reasons for change and expected benefits. The team may file a complaint with the project mentor against team members who fail to abide by the team decision making process.

3 Document Standards

3.1 Word Processor Version

Assignments for the class will be done in Google documents in order to have a central place for all members of the team to contribute. In addition, all members can see changes from other members and can review the entire document at any time.

3.2 Coordination

The person to pull together individual pieces into a full document will change based on the document as well as the time that each team member has available to work on the document. This will be set at a meeting concerning the document in question.

3.3 Version Control

SVN will be used for version control, a repository has already been setup on a NAU server and all team members have access.

3.4 Format

This document is in the expected format for our documents. When possible, tables will be used in place of bulleted lists. Anything not obvious in this document will be decided through a team decision.

3.5 Review Process

Documents must be completed such that there is a night and a team meeting (Monday or Wednesday) before the document is due. The night before will be used for team members to review the document and come up with changes, and the meeting will be used to have all team members vet changes and complete the final document.

This requirement means all documents must be submitted to the coordinator at least 36 hours before the team meeting, preferably earlier. Depending on the document this may be bumped up so that the coordinator will have a full night to compile the document before the team is to review it on their own.

4 Self Evaluations

4.1 Self Evaluation Frequency

Team members will perform self-evaluations on the previous week of work at each weekly team meeting. Team members will state their goals for the week at the end of each weekly meeting and report on completion status at the next meeting.

4.2 Self Evaluation Method

Self evaluations will be completed in the form of informal discussions. Team members will describe the completion status of the previous week's goals and rate their performance as “good” or “not so good”. Team members who feel they are doing “not so good” should request assistance from the rest of the team.

5 Group Interactions

5.1 Design Changes

Any design changes to the project must be discussed with the team. Only after the team has discussed the change and made a decision on whether or not to implement it, a team member may make the appropriate change if necessary. However, any team member may bring up a change that they believe needs to be made before the team.

5.2 Meeting Behavior

Behavior in meetings consist of simple manners. Since there are only three people in the group, many of the regular problems like side talking won’t be relevant. Everyone will be expected to do their best to show up on time or at least let someone else from the team know when something comes up.