COP2271 – Computer Programming for Engineers

C o d e o f C o o p e r a ti o n

In COP2271 you will develop the design project as a team.

A common way to promote more constructive and productive teamwork is to develop and
maintain a set of guidelines for the team. These guidelines can include behaviors, attitudes, and
roles and can focus on individual team members or the team as a whole. In COP2271, we call
this set of guidelines a Code of Cooperation.
The Code of Cooperation (COC) will be used as follows:
 It establishes guidelines for teamwork, expectations for team interaction, and
consequences for violations of these guidelines.
 Teams can refer to their COC if issues arise during the semester related to teamwork.
 In Canvas you will find a follow-up assignment with the name Code of cooperation
update. In that assignment each team will revisit their COC to review it and make any
necessary changes.

Part 1: Names & Signatures

1. Fill in your instructor and team number below.
2. Type each team member’s name in the left column in the table below.
3. Once you complete activate the track control and share it with your team members. Every
student type its name from their computer.
Instructor John Mendoza-Garcia
Team Number 2
COP2271 – Computer Programming for Engineers Code of Cooperation for design project

Team Members
Type your name in this
column for your first
submission of the Code of
Name Cooperation (use Track
changes to see different
contributors).
Karl Moody JrKarl Moody
Karl Moody Jr
Jr
Type your name again in this
column in the week in which
you are asked for the
updated version of this
document, and submit it
(make sure you activate
track changes)
Karl Moody Jr

Tuoxin Li Tuoxin Li Tuoxin Li

Camila Del Sol PinaCamila Camila Del Sol Pina

Cami Del Sol Pina
Del Sol Pina

Kamila Hernandez Kamila Hernandez Kamila Hernandez

Part 2: Individual Guidelines

1. Review the individual guidelines provided in the table below. These guidelines must
remain in your Code of Cooperation!
2. Add up to 3 additional individual guidelines in the table below.
 Write each guideline so it completes the sentence “I agree to…”

I AGREE TO…

1 Complete assignments on time.

2 Constructively criticize ideas, not individuals.

3 Resolve conflicts promptly and constructively.

4 Attend all team meetings, be on time, and be prepared.

5 Encourage team members and allow everyone to participate.

6 Take responsibility for my team’s goals, progress, and success.

7 Be an active listener and show respect for the contributions of other team

Page 2 of 6
COP2271 – Computer Programming for Engineers Code of Cooperation for design project

members.

Complete this column on the second

Complete this column on the first submission of this document, and
submission of this document submit the updated version
(add any new or revised individual
guidelines)

Communicate with my team

8 members if something comes up that Reply to messages in time
conflicts with the assignment(s)

10

Page 3 of 6
COP2271 – Computer Programming for Engineers Code of Cooperation for design project

Part 3: Team Guidelines

1. Create at least 5 (but not more than 10) team guidelines. These guidelines should address
topics such as the following; also see the example guidelines below:
 How team roles will rotate
i. Possible roles: coordinator (not the boss!), recorder, timekeeper,
encourager, devil’s advocate
 How meeting times will be determined and communicated
 How the team will accomplish and communicate its work
 How the team will ensure team assignments are turned in on time
2. Type each guideline into the table below.
 Write each guideline so it completes the sentence “Our team agrees to…”

Example team guidelines:

 Have a pre-determined agenda (list of discussion topics) developed before each meeting.
 Meet on a weekly basis at a set location and time that works for all team members.
 Put cell phones on quiet and do not have other distracters, such as Facebook, open during
team meetings.
 Set project dues dates one day before the actual due date so that all team members can
review the final document before submission.

Team Guidelines

OUR TEAM AGREES TO…

Complete this column for the second
Complete this column on the first submission and submit the updated
submission of this document version
(add any new or revised team guidelines)
Complete majority of our portions
1 before team meetings so we can get
accurate feedback.
2 Choose portions that suit our abilities.
Delegate roles in accordance with each
3
member’s strong suit
4 Be respectful of each member’s time
Meet on Tuesdays at 12:30 pm to
5
discuss team material.

Page 4 of 6
 COP2271 – Computer Programming for Engineers Code of Cooperation for design project

10

Part 4: Team Effectiveness Check

Check your team effectiveness throughout the semester by asking the following questions:

Goal Actions

 Did the team establish a common understanding of the goals in the beginning and refer
back to the goals for clarification during the meeting?
 Did the team establish a timeline in the beginning, track time, and make process
adjustments when necessary?

Relationship Actions

 Did everyone have a fair opportunity to participate and were everyone’s ideas
considered?
 Did the team acknowledge contributions, hard work, and good ideas and show gratitude
towards each other?

Learning Actions

 Did the team develop new understanding through discussions of new information
obtained from each other and external resources?
 Did the team use visual representations (pictures, charts, models) and examples to
communicate ideas?

Challenge Actions

 Did the team identify possible challenges and discuss how they can be tackled?
 Did the team make decisions based on data, evidence, calculations, and a systematic
evaluation rather than opinions?

Page 5 of 6
COP2271 – Computer Programming for Engineers Code of Cooperation for design project

Page 6 of 6