Document Sample
TEAM CONTRACT Powered By Docstoc
					                                       TEAM CONTRACT

Successful team performance depends on balancing personal accountability for individual ideas and
behaviors with those that the team demands. When working in teams, individuals can be motivated to
maximize their own rewards and minimize their own costs. However, conflicts arise when individualism
disrupts the team’s collective goals. For example, conflict can stem from an unequal division of
resources. When team members believe they are not receiving enough benefit or recognition for what
they are giving, they sometimes reduce their effort and turn in work of lower quality. Such “free riding”
occurs most frequently when divide and conquer strategies combine individual contributions into a single
product or performance and individual effort is perceived as unequal. At this point, some team members
may take on extra responsibilities while other team members may reduce their own efforts or withdraw
from the team completely, engaging in “social loafing.” These behaviors may engender anger, frustration,
or isolation—resulting in a dysfunctional team and poor quality of work. However, a well-formulated team
contract might help a team avoid such potentially dysfunctional dynamics.

Developing the following team contract should accelerate your team’s development by establishing
procedures and roles to move the team to the performing stage more quickly. The group members must
communicate and negotiate to identify standards for mutually acceptable quality of work and comfortable
levels of group participation and individual accountability. Generating a team contract can jumpstart a
group's collaboration by quickly focusing team members on definite tasks.

(N.B.: You may also want to look at the Team Merit Review while working on the following Team Contract
to help you understand the criteria on which your teammates will evaluate each other after completing the
project. As you work on your contract, you might ask yourself what will help you achieve high scores on
those measures.)

Team Name: Give your team a name.

Penguin LLC

Team Purpose: Provide a brief description of the purpose of your team, i.e. why does your team exist?
Summarize your interpretation of your team project. What are you attempting to design? What does the
client want? What does your project manager hope to see?

Penguin LLC exists to allow team member to collaboratively design the most effective Personnel
Information Management System (PIMS) for the Springfield Police Department. This solution, while cost
effective, should also include scalability, data security, reliability, and deployment design. The design
should provide both the client and administrative personnel (Project Manager) with access to necessary
data and a user-friendly interface. This design should include all requirements from Attachment A of the
inter office memorandum sent to the Penguin LLC team dated 1/20/2007. The Project Manager should be
provided with a professional and organized proposal that demonstrates the team’s ability to work
productively, professionally, and collaboratively in a timely manner.

Team Processes: Identify strategies your team will use to ensure effective communications and
decision making. These strategies may include what sort of leadership and decision-making structures
you will use, how the team will communicate, who will set/distribute agendas, what file keeping methods
you will use, when/where you will meet, and any other logistical details.

Team Contract Assignment
Revised 1.14.2007
The Penguin LLC team will communicate through the use of Google groups supplemented by in person
meetings and class work. Our team will make decisions based on open discussion and research. As
disagreements and issues arise, we will attempt to reach a general consensus. For all unresolved issues,
meetings and discussions will be documented and open issues will be kept on a running list that will
include project weak points, potential system failures, and other items that may not be addressed over
the course of this project. Any project critical disagreements will have a set decision deadline no later
than a week before the related deliverable is due. Team member Paul Johnson will manage agenda
setting and distribution. He will be the team’s point of contact for adding agenda items. All “Master” file
version will be kept on google web space to provide easy access and file redundancy. Meetings will
tentatively be Tuesday and Thursday evenings, or Thursday’s immediately following class. At this point,
no set meeting schedule will be in place. Any team member can propose an in-person meeting through
the team’s Google group. One week notice is requested, although deadlines may require shorter notice.
Microsoft Word file format (*.doc) will be used for all text documents.

Ground Rules/Team Expectations: Develop a list ground rules that all team members have agreed to
follow. Some examples may include:

Show up.                                  Be on time.                              Be fair.
Be honest.                                Actively participate.                    Submit work on time.
Submit quality work.                      Practice empathic listening.             Practice win/win.
Demonstrate personal accountability.      Respect others’ ideas/opinions.          Commit to team goals.

List the ground rules ALL team members have identified and agreed to follow. Be sure to specify what
you mean by these rules. For example, what standards characterize quality work? How active is active

Show up and be on time to all in-person meetings. If for some reason you cannot make a meeting, 24
hour advance notice is requested. All work submitted should be high quality. Team members can and will
help in final revisions of all major deliverables. Work should be actively engaged in by all team members
on a schedule that allows for unforeseeable and technical difficulties that would require team
consultation. All work should be your own. Input from all team members is desirable and all ideas can be
discussed. The entire team should be committed to submitting work on time and meeting scheduled
deliverables. Any team member that will not be able to meet deadlines should communicate this to the
rest of the team as soon as possible.

Consequences: Develop a list of consequences appropriate for team members breaking the ground
rules your team has established. They should be reasonable, enforceable and agreed to by all team

All failures to meet these ground rules will be recorded in the minutes of team meetings and will be
included in all peer/team reviews. Any further disciplinary action necessary will be dealt with on a case by
case basis and may include the involvement of the Project Manager.

Forming: As we discussed in class, groups go through stages of forming, storming, norming, and
performing. To help your group move through the forming and storming processes, your group should
also document four -ing processes with digital pictures. Include pictures of the group engaged in the
following -ing activities:
      Eating
      Deciding
      Posing
      Contracting

Team Contract Assignment
Revised 1.14.2007




Team Contract Assignment
Revised 1.14.2007

Shared By: