ECE361 Engineering Practice

ECE361Engineering Practice Team Skills - Meetings “Meetings are gatherings where minutes are kept and hours are lost” Murphy’s Laws Page 1

Team Skills - Meetings • Team Assignments • Team Skills • “Meetings, Bloody Meetings” Video • Assignments Page 2

Team Assignments Page 3

Project Teams Page 4

The vast majority of engineers work in team settings. Often, an engineer is a member of many teams, playing different roles in each team. Understanding teams is a skill that must be learned… Page 5

“…a small number of people with complementary skills who are committed to a common purpose, performance goals, and approach for which they hold themselves mutually accountable.”Smith, p. 33 What is a Team? Page 6

What are some characteristics of an effective team? Good participation Common goal Respect Sense of Purpose Careful listening Good meeting facilitation Leadership Empowered members Constructively-managed Members take conflictresponsibility Fun Effective decision-making Smith, p. 32 Page 7

Team Challenge Diagram the Internet Mail process from creation to reading10 minutes… Page 8

Team Challenge - Reflection • Did you operate as a team? • Did you feel organized? • Did you meet your objective? • Did everyone participate equally? • Was time management an issue? Page 9

Team Skills Must be Developed Team processing Roles and Responsibilities AccountabilityIndividual and team workTeam communication Page 10

Code of Cooperation In order to have effective teams, each team member must be willing to work together as a part of the team. In a sense, this requires each team member to be a good team citizen. Perhaps your team members do not have a common understanding of what a good team citizen is, and so we will develop a team Code of Cooperation Mutual agreement of team Signed and dated by all team members Enforced by team members Revisions if needed Often posted at meeting place Page 11

Should be as concise as possible. Personalize, but do not allow inappropriate behaviors sample available on web page Page 12

Calibrated Peer Review (CPR) • Great way to learn about and improve your writing • Used in a number of classes • Time Schedule is important and unforgiving… • See handout on Angel for details Page 13

Log into CPR now You are a new user! Afterwards, login with userid and password Look at first assignment (Keeping Minutes) CPR Minutes Assignment Page 14

CPR Submissions in HTML • Don’t forget ! • Construct your assignment in Word (or other processor) • Save as HTML File • View and copy the HTML source code • Paste HTML source code into the CPR submission box Otherwise, there will be much weeping and gnashing of teeth Page 15

MEMORANDUM TO: ECE361 ClassFROM: Professor Ferguson DATE: 5 September 2005SUBJECT: Requested Information Each team is requested to meet and decide upon two matters: 1. Team Name and 2. Team Code of Cooperation Submission of this information and the team membership is requested from each team in memo format (angel dropbox) by the end of the day. Any attached documents should have the team name in the filename. Minutes of the team meeting are also to be kept by each individual for a future activity. Page 16

ECE 361 Assignments • INDIVIDUAL ASSIGNMENT – Obtain bound notebook for course/project before next class • TEAM ASSIGNMENT - Prepare and submit a memo including your team’s name, membership, and code of coop. • Primary author must be indicated • Due ASAP, one per team, via angel dropbox • Photocopy signed code and disperse to members and instructor • INDIVIDUAL ASSIGNMENT – Work the CPR assignment “Keeping Minutes” • Submit the minutes you took from the “Code of Cooperation” meeting of your team • Mind the CPR schedule! Page 17

References: • [1] K Smith, Project Management and Teamwork, 2nd ed., McGraw-Hill, 2004 Page 18

ECE361 Engineering Practice