A. Team Working Agreement

Software Design Project

Team Working Agreement

Autumn 2018

 

1)  Group Identification

Table # – Q

Instructor – James Toney

 

2)  Primary Means of Communication and Expectations

 

All members will be expected to read and respond to group texts as soon as possible or within 24 hours of it being received.

 

3)  Scheduling of Meetings

            Team will meet at the end of each class to discuss whether a meeting will be necessary for the week. If it is decided that the meeting is necessary, a time and place will be agreed upon if possible. Any exceptions should be communicated and decided upon by group members via text if all members are not together.

 

 

 

4)  General Responsibilities for All Team Members

 

The group will decide on how to divide up the work in class or in a meeting outside of class. Each member should be responsible for at least one of the major duties with the project and can be assisted or ask for assistance by another group member whenever it is desired. Each member is responsible to keep track of their deadlines and finish their tasks by then, with possible revisions from other members.

 

5)  Specific Team Member Responsibilities/Deadlines

 

Each member will be responsible for their tasks assigned to them in the team meeting. Along with doing the tasks, the members should keep track of their assignment and take notes on the process performed for their assignment. These processes will be combined into the team notebook and submitted at the end of the project.

6)  Conflict Resolution

 

When a member fails to do his share of the agreement, the following actions will occur:

 

  1. The members will schedule a meeting to discuss the problem.
  2. During the meeting, the members will identify the problem and discuss possible solutions.
  3. After the meeting, the solution should be applied and the situation should be monitored for problems going forward.

 

7)  Expectations of Faculty and GTA’s

 

If a team member fails to fulfil their part of the agreement and the rest of the group, and the group cannot come to a resolution,

 

8) Team Roles

 

Matthew Mileski: coder 1(Battleship)

Jack Gallucci: coder 2(Hangman)

Matthew Bagley: website scribe

Erfan Abuduwaili: Notebook scribe

 

 

9) Team Signatures

 

 

 

 

 

 

 

 

 

 

 

Matt Mileski

Matt Bagley

Jack Gallucci

Erfan Abuduwaili