Sie sind auf Seite 1von 11

ITB002 IT PROFESSIONAL STUDIES

TEAM AGREEMENT
for Group One

Prepared by: ... Team Number: 1.1 Team Members: Team Member Name Lachlan de Waard Tony Thornton Jonathan Packer Michael Roh Candice Hudson Student No. n6834388 n6829449 n6582796 n6798713 n6792936

Due Date: 22nd August 2008

Team Agreement Sign-off


The undersigned members of this team agree to abide by this team agreement to ensure the successful completion of the Latin Dancing Website project to meet the clients requirements and timeframes. Name Student No. Signature Date Jonathan n6582796 Packer Tony Thornton n6829449 Candice n6792936 Hudson Michael Roh n6798713 Lachlan de n6834388 Waard Client

Group One ITB002

Team Agreement Page 2

CONTENTS
Contents............................................................................................................................3 Introduction........................................................................................................................4 Team Agreement...............................................................................................................4 Team principles and processes.......................................................................................4 Principles.....................................................................................................................4 Operational Processes.................................................................................................6 Project management....................................................................................................8 Non-Compliance............................................................................................................10 Minor Non-Compliance Definitions.............................................................................10 Major Non-Compliance Definitions.............................................................................10 Penalties for Major and Minor Non-Compliance..........................................................10

Group One ITB002

Team Agreement Page 3

INTRODUCTION The purpose of this document is to define the agreed operation procedures and protocols under which Group One will operate. The operational procedures and protocols mentioned shall provide predefined methods by which Group One will communicate and collaborate to produce the Latin Dancing website. This agreement, collaboratively created by the entire team, aims to provide the said protocols in a way that the entire team is satisfied with. The ideals derived here dictate how the group must conduct themselves during team communication, and the responsibilities that each team member must carry in order to ensure the successful production of the project. The document shall outline the following items: The constitution of a successful team and how to implement it Communication methods that support the established principles Definitions of acts of non-compliance to the agreement, examples of said acts. Methods of resolving disputes and managing conflicts.

TEAM AGREEMENT TEAM PRINCIPLES AND PROCESSES PRINCIPLES

Principle: Frequent Communication


o

Rationale: For the team to work as a single unit, everyone must know exactly how the team is functioning. Operational Processes:

Notify team when a unit of work is finished or up for review Provide input on other peoples work, and ideas Constantly check email/communication medium. Show up to meetings on time, and do your best to stay for the duration.

Principle: Equality and respect


Team Agreement Page 4

Group One ITB002

Rationale: Respect ensures that the working environment is positive, and equality comes is a major part of respect, in ensuring that every team member has a say. Operational Processes: Ensure every participant of a meeting has a chance to make their opinion known for each subject No team members opinion should be equal when a decision is achieved at a meeting it should be done by consensus (unless the team elects a chair to control such decisions). Treat each team member as you would like to be treated.

Principle: Good work ethic


o

Rationale: A good attitude toward your work ensures that work is completed when it is needed, and of a suitable quality. Operational Processes: Ensure that good time management is used so that work can be delivered to the group on time. Actively review the description of your unit of work while implementing it, to ensure that you are performing the correct task.

Principle: Good Group Time Management


o

Rationale: Poor Time Management under group or individual circumstances can lead to poor results, or worse, an incomplete project. Operational Processes: Constantly check units of work against the scope definition, the ensure scope creep does not occur. Split tasks equally and fairly among group members. No member should have more work than they can handle, and no member should have significantly less work than the rest of the group. Follow the project schedule as close as possible, to ensure milestones are achieved at the desired times. If a group member is struggling with their workload, shift some to another member to ensure quality does not slip.

Group One ITB002

Team Agreement Page 5

Principal: Share knowledge


o

Rationale: Its easier to learn from a person than a textbook. A person teaching the skills required in the correct context can be much more efficient than spending time reading a text. Operational Processes: If you need help with some part of your work, make sure that you communicate this with the team so they can do their best to help you. If a piece of work is far out of your ability, let the team know so that they can reallocate it. If another team member needs help that you can provide, offer it in an intuitive and helpful way, without being condescending.

Principle: Deliver Good Quality


o

Rationale: A project that is poorly constructed will never satisfy the client, and reflects poorly on the team and all of its members. Operational Processes: Review the quality of your work make sure that it is up to your standards before presenting it to the group. If needed, provide constructive criticism of a team members work making sure that you do not insult the team member. Provide suggestions of how their work could be improved. Substantial units of work should be reviewed by the entire team before being committed to the final project. In the event of a team members work not passing the quality standards of the group, a revision should be supplied by either that team member, or another team member. Before starting a revision of someone elses work, ensure they know you are working on it.

OPERATIONAL PROCESSES

Meetings will be held weekly at TIME TBA. If for some reason one or more of the members cannot make it, an online meeting may be held via Windows Live Messenger (MSN) if it suits the missing team member.

Group One ITB002

Team Agreement Page 6

In the case that a team cannot make the meeting due to other appointments, the meeting minutes should be reviewed thoroughly, and input can be provided via the online forum. For more information on meeting absence without notice, see the non-compliance section. Meeting minutes will be posted on the online forum directly after each meeting.

The online forum (http://itb002.relasz.com) will be used as an integral communication medium between members. This medium provides a method of uploading files, and recorded discussion. o Because this is so easy to access, team members should communicate with each other as often as possible with this medium. As a minimum, the forum should be checked once every two days as well as email. Note that you can set the forum to email you when a post is made in one of your topics

Important documents relating to the project will also be posted on the forum such as the agreement, and the work breakdown structure.

If a team member cannot be contacted via email or forum, they have not responded within two days, or they need to be contacted immediately, mobile phone SMS (text messages) or calls may be used. Each of the team members phone numbers have been provided on the forum. Meeting agendas will be provided in the form of a forum thread. This way every member of the team has the ability to add to the agenda of meetings. Each meeting, the progress of the project will be reviewed, as well as scope creep, and the time management of the tasks of the project to make sure the initial plan is still viable. o A team chair will be elected each meeting to follow the agenda and keep track of time to ensure meetings cover all of the required topics within the allocated time. A team scribe will be elected each meeting to ensure that the minutes are recorded so that they may be referred back to at a later date. This person must also be responsible for entering all of the required data into TeamWorker.

Technical issues may be posted on the Issues category of the forum, where all of the members of the team may provide input on possible resolutions of the task.
Team Agreement Page 7

Group One ITB002

If a team member cannot perform their assigned task in the allocated time, a message should be posted on the forum, as well as an item added to the next meeting agenda to discuss who will help to finish the task without damaging the project schedule. If a new task is required to be added to the project schedule, the group member that wants to make the changes can alter the project plan using Microsoft Project, and then submit it to the group for consideration. o Alternatively, an item can be added to the agenda in which the group collaborates to allocate time for the new task.

PROJECT MANAGEMENT Note from Jonathan: Need to discuss this further in a group meeting as to what design methodology to use, if we are going to use one at all also, we need to finish up the gantt chart/work breakdown structure for this. Ill do a rough version of these in the coming days if needed. How the scope/quality/HR is handled depends on the design methodology, so we should add that to the agenda for the meeting on Tuesday. The stuff that isnt dictated by methodology Ive added below.

Communications As detailed in the Principles section, the primary sources of instant communication will be email and online forum. The forum technology provides a structured method of propagating information and items throughout the team, and ensures that all information is in one place where everyone can see it. Email is more convenient for some group members, but this can lead to some problems such as emails not being sent to the entire group. Even in a two way conversation relating to the project, it would be preferable to do it on the forum because the entire team can input on anything. This reinforces the Equality principle, ensuring that all of the team members have a say in anything. Equality leads to greater satisfaction of work throughout the team. Risk Although the project is being conducted in a relatively low-risk context, there are still some issues that need to be addressed. When the project is being scheduled, the entire team must review each unit of work and be certain that they can allocate the time needed to complete it. It should also be made certain that enough time is allocated for each unit of work, as well as a buffer that enables disaster recovery.
Group One ITB002 Team Agreement Page 8

Time The project will follow a specific work schedule that is defined in the attached Gantt chart and work breakdown structure. These should be thoroughly and continuously reviewed to ensure that enough time is allocated to complete the work without sacrificing quality.

Group One ITB002

Team Agreement Page 9

NON-COMPLIANCE MINOR NON-COMPLIANCE DEFINITIONS Breach of Team Principles. This is when a team member clearly does not comply with one of the team principles, and disregards the team agreement. For example:
o

Team member does not involve themselves in team communication for the week, and does not provide updates on how their work is progressing Team member treats another team member with disrespect, insulting them during a meeting. Team member is condescending when another team member asks for help..

Non-communication without explanation. For example: o Team member does not communicate with other team members to let them know that they are going away, leaving the team wondering where they are.

Late work without explanation. For example: o Team member does not submit work for a weak, and provides no explanation as to why they could not complete it, or ask for help.

MAJOR NON-COMPLIANCE DEFINITIONS Major Breach of Team Principles. For example o Team member does not do any work for two weeks, does not supply a reason why, and does not contact group for reasoning.

PENALTIES FOR MAJOR AND MINOR NON-COMPLIANCE Minor Non-Compliance In the event that the entire group agrees a member has breached a minor noncompliance definition, they will be given one minor warning. It is important that the entire group comes to agreement that the team member should receive the minor warning before it is given. Two minor warnings are equal to one major warning.

Group One ITB002

Team Agreement Page 10

Major Non-Compliance In the event a group member breaches a Major Non-Compliance definition, the member will be given a major warning. As with the minor warning, the group must come to a final and definite consensus that the person deserves the warning before it is given. A distinction also needs to be made, obviously, between whether they deserve a major or minor warning. If a team member receives three warnings, they are considered to have been given chances, and it is understood that the person no longer wants to be involved in the group. The group can then come to a common agreement of whether or not to evict that member from the group.

Group One ITB002

Team Agreement Page 11

Das könnte Ihnen auch gefallen