The Team Contract

1. Team Members

1.1 Danish team

Tobias Elleboe Cordsen

Email: teco@itu.dk

Laura Pantis

Email:

ITU: lapa@itu.dk

Anita Bejan

Email:

ITU: cabe@itu.dk

2. Roles and Responsibilities

Possible Roles in a Software Development Team:

3. Mutual expectations

3.1 Workload

Every group member is expected to be focused during group work, and respect the the agreements made in the group. During peak workload times, weekends and evenings may be revoked for group work. Furthermore each group member is supposed to do their individual assignments before the deadline set by the group.

3.2 Evaluation of group work

Team meetings will be held on Fridays at 14.00. If a group member is not able to attend the weekly meetings, that member must inform the rest of the group beforehand.

3.3 Informing the group

Ilness and delays must be informed to the group members as quickly as possible. This can be done by mail, sms or phone.

3.4 Atmosphere

All suggestions and thoughts must be taken seriously and considered by the group as a whole. We will decide upon  suggestions by vote.
All members are expected to speak english.

3.5. Team collaboration

Our main focus will be the process. This includes close team work, frequent meetings to avoid misunderstandings and keep the project on track.

The success criteria for our team is to meet the goals we set.

3.6 Conflict Mitigation Plan

We will write project plans for every iteration, trying to include some buffer time, in case of something going wrong.

"Dirty Friday"

Each Friday we will use 30 minutes for talking about how we feel the process is going. Every group member takes turn talking about how they feel the process is going. Everything can be brought to the table.

4. Processes and tools

We are going to work agile using Scrum and plan on following the Agile Manifesto.

We are going to use Assembla, which supports this agile method by providing facilities for scrum meetings, a ticket system, a wiki, and message board.

Team communication will be through Skype, messenger and email.

For code reviews we plan on using Skype's screen sharing function.

Documents/files will either be kept at the Assembla wiki or files section or submitted to SVN.

5. Working software

As mentioned in section 4. Assembla will host both our SVN repositories and all the project documentation.

Process documentation will be held on the Wiki provided by Assembla. Here, we want to keep the course log, which is a diary for our project and process. Tracking of our progress will also be included. 

We agreed on using Hudson as a continuous integration server. It will be used with Ant. JUnit tests will be included. 

Although our focus is on the process we want to achieve good quality software. As for coding, we will follow the standard guidelines.