Template for a Group Working Contract 1

Template for a Group Working Contract

Template for a Group Working Contract[1]

Group: XXX

Members: XXX

Date: XXX

Roskilde Business College, 2003
Table of content

Template for a Group Working Contract 1

Project Requirements and Resources available 3

Introduction to this Study Project Assignment 3

Purpose of group work 3

Purpose of this document 3

Respect: 3

What is the goal for the group work (what is to be delivered to who) 3

Resources available for the group and assessment of Strengths and Weaknesses 4

Human Resources available 4

Short description of XXX 5

Short description of XXX 5

Short description of XXX 5

Short description of XXX 5

Individual Strengths and Weaknesses 5

Group Strengths and Weaknesses 5

Time available 5

Peer Review Contact: 7

The Advisors: 7

Technical Resources available 7

Software: 7

Hardware: 7

Risk assessment 7

Identified potential risks for the group work and preventive measures 7

Preventive Measures 9

Project organization and Roles 9

Roles 9

Role: Moderator and Project Leader (assigned to XXX) 9

Role: Nurse (assigned to XXX) 10

Role: Timekeeper (assigned to XXX) 10

Role: Notetaker (rotating) 10

Role: Backup Person: (assigned to XXX) 10

Role: Hardcopy person: (assigned to XXX) 10

Working schedule and place of work 10

Working Hours: 10

Working Place: 11

Project Progress Plan 11

Milestones: 11

The Life in Our Group 12

Decision Making: 12

Working Process: 12

Expenses: 12

Absence: 12

Sanctions: 12

How to change and evaluate group working contract 12

Signature 12

Project Requirements and Resources available

Introduction to this Study Project Assignment

This project will be carried out in the period XXXday 01.01.03 to XXXday 01.01.04 and constitutes the requirements of the XXX semester in the Advanced Computer Science Class (International) at Erhvervsakademi Roskilde.

The project team has not worked together before and none of the team members have experience with the chosen architecture.

The methodology we use will be RUP in the Inception, Elaboration and Transition phases, while the Construction phase will use XP in a RUP-compliant form. As determined in the “Introduction to the Study Project”.

Because none of the team members have ever worked with RUP or UML before, this is an ambitious assignment. We feel that our team is strong and motivated enough to tackle it.

As an integral part of the project, the team has proposed a problem definition. The existence of a problem definition reflects the dual nature of this project: it is both a research project and a systems development project, and we will deliver both a Project and a Product. The problem definition will be the driving force upon which we will base our investigations and decisions throughout the report. Conclusions to this problem definition will also be outlined in the report.

Purpose of group work

Purpose of this document

The group working contract is done for several reasons:

·  To support the project team by identifying human, technical and environmental resources available to the project

·  To allow team members to identify and accept the realities of the project: its scope, duration, rules, interested parties and goals and their roles in the project

·  To provide a simple, clear starting point for the project and a foundation for the team’s working practices and social dynamic

Respect:

Everyone is entitled and need to speak their minds even after a decision is made, as this is a school project and therefore a learning progress for us all.

Everyone need to respect everyone and show patience, we are all different human beings and understand things at a different speed.

Remember: “It’s not right it’s not wrong it’s just different”.

What is the goal for the group work (what is to be delivered to who)

The main objective of the project is to gain experience working with XXX in a programming and systems development project. It is also an opportunity to apply what we have learned in our education and to research and practice subjects and techniques that are not in our standard curriculum.

The goal is to complete the study project in time and to deliver Study Project documentation and Systems Development documentation to the school for evaluation at the final exam for this semester.

In addition to completing the assignment described above, this project is an opportunity to:

·  Gain further experience in organizing and managing development projects.

·  Exercise and develop our skills in Systems Development, Programming and Computer Networking.

·  Gain experience working in teams.

·  Apply the theory that we have learned in school to a practical exercise.

·  Apply and assimilate new theory and practices used in real-world development projects.

·  Develop, define and run our own methodology based on existing frameworks.

·  Gain experience in developing Web based applications.

The criteria for success have been included to aid us in evaluating the results of the project:

·  A working module is implemented.

·  A report outlining the decisions made and tasks performed during the completion of the research and system development project is delivered.

·  The project is completed on time.

·  Team members gain knowledge and experience in socket programming, Web programming and lightweight, agile iterative methodologies.

·  Team members gain understanding of new technical platforms and component-based architectures.

·  The project receives a good evaluation from the project advisors and censor.

Resources available for the group and assessment of Strengths and Weaknesses

Human Resources available

Below is a list of human and technical resources upon which we will rely during the development of the project.

The Project Team

Name / Address / Telephone / E-Mail / Nationality
XXX / XXX / XXX / / XXX
XXX / XXX / XXX / / XXX
XXX / XXX / XXX / / XXX
XXX / XXX / XXX / / XXX

Table 1– The Project Team

We gained great insight into the dynamics of team structure and individual tendencies on a previous project by using Dr. Meredith Belbin’s team-role theory. We have therefore chosen to asses the strength of our team by performing Belbin’s Self Perception Inventory Analysis and comparing the results to Belbin’s criteria for team building. The results of this analysis and a full description of the Belbin team/roles are given in appendix[2] Note that the roles indicated below apply at the beginning of the project, and may change as the project progresses. We will track those changes by performing the test again at later stages in the project.

Short description of XXX

Born in XXX, XXX has worked as a Civil engineer for over seven years in his home country before moving to Demark 5 years ago as a refugee. At the outset of the project he displays the traits of the following Belbin roles: Specialist, Team Builder and Monitor Evaluator.

Short description of XXX

XXX is the youngest with his 21 years. Before he started on the Datamatician course he had just graduated from the gymnasium. Last semester he was in Australia on a study abroad program, where he studied at Deakin University. The Belbin team roles that XXX possesses are Team Builder, Implementer, and Coordinator.

Short description of XXX

Born in Denmark, but have for four years lived and worked in the U.S. In addition, work experience includes two organizations in which new systems have been implemented. XXX displays the traits of the following Belbin roles: Completer/Finisher, Shaper and Implementer.

Short description of XXX

Born and raised in USA, his work experience consists almost entirely of menial jobs in restaurants and factories. He displays the traits of the following Belbin roles: Resource Investigator, Shaper and Plant.

Individual Strengths and Weaknesses

Name / Strengths / Weaknesses
XXX / Motivated, methodical, good programming and Systems. / Over-analytical, tends to overwork himself when faced with a new problem
XXX / Motivated, positive, good in Programming, Systems and compromising. / Lack of patience, sometimes needs a small kick to stay focused
XXX / Organized, dependable, punctual, motivated, office experience, good in databases, Web programming theory and systems. / Children place constraints on time
XXX / Dependable, good conceptual skills, good resource investigator. Good in programming, system development and business. / Impatient, short tempered, talks too much

Table 2– Strengths and weaknesses of the team members

Group Strengths and Weaknesses

With our varied backgrounds and broad range of strengths, we feel that we have a strong group. This is further evidenced by the fact that all of the nine roles that Belbin states should be present in a team are actually found among the team members. Thus our team could not be stronger according to Belbin’s criteria. One concern regarding the Belbin roles is that we have only one strong Completer/Finisher in our group, and we feel that this is one of the most important roles for this project. If the Completer/Finisher is absent, other team members must make a concerted effort to fill this role. Our primary weaknesses are limits placed on our time and danger of talking a subject to death and falling behind. We believe that our dedication and enthusiasm should allow us to overcome these dangers.

Time available

During week XXX-XXX for this project the following restrictions apply to the group work:

For XXX[3] the following restrictions apply / Monday / Tuesday / Wednesday / Thursday / Friday / Saturday / Sunday
Morning / 8-12: attending classes / 8-12: attending classes / 8-12: attending classes / 8-12: attending classes / 8-12: attending classes
Afternoon / 12-14: attending classes
16-18: Personal / 12-14: attending classes / 12-14: attending classes
16-18: Personal / 12-14: attending classes / 12-14: attending classes
16-18: Personal / 12-15 Deliver newspapers
Evening / Fitness

In summary for week XXX-.XXX the following time is available:

For the entire team the following restrictions apply / Monday / Tuesday / Wednesday / Thursday / Friday / Saturday / Sunday
Morning / 8-12: attending classes / 8-12: attending classes / 8-12: attending classes / 8-12: attending classes / 8-12: attending classes
Afternoon / 12-14: attending classes
16-18: Personal / 12-14: attending classes / 12-14: attending classes
16-18: Personal / 12-14: attending classes / 12-14: attending classes
16-18: Personal / 12-15 Deliver newspapers
Evening / Fitness

During full time project work (week XXX-XXX) the following restrictions apply to the group work:

For XXX[4] the following restrictions apply / Monday / Tuesday / Wednesday / Thursday / Friday / Saturday / Sunday
Morning
Afternoon / 16-18: Personal / 16-18: Personal / 16-18: Personal / 12-15 Deliver newspapers
Evening / Fitness

In summary during full time project work (week XXX-XXX) the following restrictions apply to the group work:

For the entire team the following restrictions apply / Monday / Tuesday / Wednesday / Thursday / Friday / Saturday / Sunday
Morning
Afternoon / 16-18: Personal / 16-18: Personal / 16-18: Personal / 12-15 Deliver newspapers
Evening / Fitness

Peer Review Contact:

The group has agreed with Study Group number XXX to do Peer Review. This means meeting from time to time and exchange ideas and give feedback on each others work.

The Advisors:

Project Advisor:

Short profile

Technical Resources available

The following is a list of resources owned by group members or available from Roskilde Handelsskole (RHS):

Software:

·  Microsoft Office XP (Word Processor)

·  Visio Professional 2000/2002 (Diagram Application)

·  Microsoft Project (Project Plan Application)

·  Sun Java 1.4.1 (Programming Language)

·  Apache Tomcat (Server/ Servlet container)

·  Windows 2000, Windows 2000 Server

·  Panda Antivirus

·  RUP Builder (RUP Software)

·  JUnit 3.8.1 (Java testing software)

·  Textpad (IDE)

Hardware:

·  PCs at RHS and at home

·  2 laptops

·  1 digital camera

·  Laser printer at RHS

·  Scanner at RHS

·  Floppy Disk and Flash plugs for backup

·  Internet and network connections for backup and communication

·  Overhead projector

Risk assessment

Identified potential risks for the group work and preventive measures

Based on the above analysis and the experience from previous group work typical risks in the group work fall in these categories[5]:

·  Disharmony in group work

·  Sharing of workload

·  Lack of skills

This risk assessment is aimed at possible hindrances to the successful completion of the school project. It is included as a means of anticipating possible problems that may arise during the execution of the project, and to help ensure a successful outcome.

Risk[6] / Consequence / Possibility / Priority / Preventive measures / Contingency Plan
Loss of Enthusiasm and Motivation / Setbacks
Conflicts
Stress / 3 / 5 / Job rotation and sharing power. / If one team member is particularly stressed, he/she will to take a day or two off.
Illness / Setbacks
Loss of Motivation / 4 / 5 / Re-assign tasks to other team members.
Company Withdraws From the Project. / Loss of motivation,
Information loss,
Poor Acceptance Testing / 1 / 3 / Continue project from assumptions. Document which parts of the report are based on the actual company.
End of iteration acceptance to be completed with project advisor
Project Falls Behind Schedule / Setbacks
Stress
Poor product / 4 / 5 / Add weekend days to schedule. Narrow scope of project. More individual work. Leave gaps in project schedule.
Project Uncertainties / Setbacks
Poor product
Stress
Loss of motivation / 4 / 3 / Perform baselines. Consult previous projects. / Consult with advisors. Make assumptions. Ask the user.
All Backup Media Lost / Loss of entire project
Loss of motivation
Poor Product
Setbacks / 1 / 5 / Gather all paper documentation, / Re-establish smaller project.
Personal Conflicts Within the Team / Loss of Motivation
Setbacks
Poor Product
Stress / 2 / 4 / Consult with project advisors. Meet outside project setting for informal discussion of the problem.
A Person Leaving the Team / Setbacks
Stress / 2 / 3 / Divide work amongst other team members, narrow scope of project.
Project Work gets Sidetracked in Long Discussions / Setbacks
Frustration
Loss of focus / 5 / 5+ / Concentrate on current task, review iteration plan

Key:

Very High / 5
High / 4
Medium / 3
Low / 2
Very Low / 1

Table 3– Risk Assessment