Section 1: Team Name and Mission
This team shall be known by the name: Pelton Wheel Development Project
The mission of this team is to analyze the existing status of the pelton wheel in the civil engineering
hydraulics lab. The team will design, plan, and implement an alternate breaking and torque
measurement system in the form of an electrical generator. Additional features will be implemented by
the client and provided there is sufficient time to complete the task.
Section 2: Membership
Membership on this team includes the following people: Ian Haynes, Phillip Spinden, Kenneth Fletcher,
and Jennifer Jones. Civil engineering students assigned to this project may join at the discretion of the
Civil Engineering Department. Others may join or leave this team in accordance with the dates and
policies set forth by the University.
Members of this team shall be responsible to Dr. Joe Law and Dr. Jim Liou.
Section 3: Roles and Responsibilities
Roles are assigned on agreement at team meetings. Time will be allocated for each task as is required to
satisfactorily complete the task. Tasks will be assigned based on strengths and qualifications of
members’ abilities. In the event of a role vacancy, the team will have alternates that will perform the
task that will be defined with the role itself.
3a.
Team Leader: Kenneth Fletcher
Alternate:
Ian Haynes
The team leader is to maintain group focus and efficiency of meetings. The team leader shall: hold
members accountable to task assignments, and direct and assign tasks if consensus cannot be agreed
upon. In the event that an informal meeting is needed, the team leader shall set up and conduct the
meetings with the project stakeholders.
3b.
Treasurer:
Phillip Spinden
Alternate:
Jennifer Jones
The treasurer is to manage the budget and keep a detailed record of project expenditures. The
treasurer will also research project costs, materials, and options. In the event that a financial decision
cannot be agreed upon by the team or stakeholders, the treasurer will make the final decision.
3c.
Schedule/Progress Manager: Jennifer Jones
Alternate:
Phillip Spinden
The schedule/progress manager will maintain and update the project master schedule and timeline. In
the event that the weekly meeting cannot be held, the progress manager will determine the reschedule
time. The progress manager will also determine when to hold extra meetings if progress is behind.
The progress manager will be representative of the team when meeting with stakeholders.
3d.
Minute Keeper:
Ian Haynes
Alternate:
Jennifer Jones
The minute keeper will document and keep official records of events and plans for each meeting.
Section 4: Team Relationships
Relationships among team members must support full and respectful engagement of all members for
the benefit of the entire team. Team members will constructively criticize while maintaining a
respectful and professional demeanor. Team members will defer from alienating or excluding any or all
members. All team members will be treated equally.
Section 5: Joint Work
5a. Purposes of Joint Work
Team members will work together to establish collective goals and to produce decisions and work
products that advance teamwork and project success. When working together, members will strive to
complete the tasks in a timely fashion. Members will also strive to promote and complement each
others’ skill sets.
5b. Team Meetings
Team meetings are an important example of working together. Meetings of the entire team (including
stakeholders) will be held on Tuesdays at 11:30 AM in the ECE conference room. In order to make team
meetings productive and rewarding for all members, project members will meet on Fridays at 3:30 PM
in BEL 207, or as otherwise agreed upon. Team meetings will be held to track progress, assign project
tasks as required, and to ensure preparedness for the stakeholder meetings.
Section 6: Individual Work
Team members are expected to work alone in many cases to complete work important to the team.
Work assignments will be made at team meetings by agreement of team members. Assignments will
include definitions of expectations that include deadlines, task requirements, and, if necessary,
scheduled checkpoints.
Work quality, alignment with team needs, and timeliness are vital to the success of the team. To ensure
that team member contributions provide value desired by the team, tasks will be reviewed by the team
members upon completion. Individuals failing to meet expectations will face the following
consequences: inform member of deficiency, formal documentation, and at the discretion of team
members, if there is a pattern of misconduct, take to stakeholders.
The team will assist members in their success by identifying root causes of deficiencies or failing to meet
deadlines.
Section 7: Documentation and Communication
The team must maintain timely and accurate documentation of its individual and collective
achievements, while also communicating needed information to one another and key project
stakeholders.
7a. Documentation
Team members will maintain the following records of their work: logbook records and completed work.
Important records may be duplicated.
7b. Communication among Members
Team members will keep one another informed about work assigned and completed, problems that
arise from tasks, and if unable to attend a meeting.
7c. Communication with Outside Stakeholders
Outside persons, including stakeholders and potential sponsors, will be kept informed about project
progress and planning, major design decisions, and any potential problems.
Section 8: Conflict Resolution
The team will strive to resolve conflicts quickly and to the satisfaction and benefit of everyone involved.
To this end, the team will maintain an informal and open forum to resolve any conflicts. If a resolution
cannot be made, the team will communicate with the stakeholders.
Section 9: Amendments
Amendments to this team contract may be made with the approval by all members of the team.
Proposed amendments must be approved unanimously. The amended contract must be distributed to
all members and submitted to the instructor before becoming effective.
Section 10: Affirmation of Compliance
We, the members of this team, affirm that we have established this contract with the input and
consensus of all members. By our signatures, we commit to compliance with the contract for the
benefit of all members and the team as a whole.
Team Member 1 Signature
Date
Team Member 2 Signature
Date
Team Member 3 Signature
Date
Team Member 4 Signature
Date