Engineering Teamwork

1. Engineering Teamwork

2. What People Say About Teamwork “Getting” good players is easy. Gettin' 'em” to play together is the hard part.” Casey Stengel(former NY Yankees manager) “Coming together is a beginning. Keeping together is progress Working together is success.” Henry Ford “Everyone has to work together; if we can’t get everybody working toward common goals, nothing is going to happen Harold K. Sperlich (Former President, Chrysler Corporation)

3. What is teamwork…. • A team is a small group of people with complementary skills who are committed to a common purpose, performance goals and approach, for which they hold themselves accountable maketeamworkhappen.com

4. Design Group (Team) • Engineering projects require diverse skills • This creates a need for group (team) work • Select members based on skills • Technical • Problem-solving • Interpersonal

5. Benefits of Working in Teams - overview • Accomplish more in: • Quantity • Complexity • Generate more solutions/brainstorming ideas. • Gain exposure to various points of view. • Develop/use “critical thinking” and “evaluation” skills. • Improve conflict resolution skills • Improve communication skills

6. Benefits – more detail • Accomplish projects an individual cannot do– Most engineering projects are too large or too complex for one individual to complete alone. Imagine trying to build the Golden Gate Bridge all by yourself! • Brainstorm More Solution Options- Different people looking at the same problem will find different solutions. • Detect Flaws in Solutions- A team looking at different proposed solutions may find pitfalls that an individual might miss. • Build Community - Members of effective teams can form personal bonds which are good for individual and workplace morale. In the university setting, students on teams often form bonds that extend beyond the classroom.

7. Benefits – more detail • Exposure to different points of view- You learn different ways of approaching a problem when you are exposed to methods and ideas that other people have. • Critical Thinking and Evaluation Skills– You must use these skills to evaluate the complex issues of team project goals and to formulate appropriate solutions and plans.

8. Benefits – more detail • Conflict Resolution Skills- Yes, teams have conflicts, but you can develop the skills to facilitate solutions to conflicts so that the team remains functional. • Students may do more academic work- Some students may accomplish more in order to keep up with the rest of the team.

9. Benefits – more detail • Communication Skills- A team relies on communication among members. • Actively and effectively listen to their team members to understand their ideas and concerns. • Effectively articulate their ideas or their concerns to others. • Provide genuinely constructive feedback to team members

10. Teamwork Enhances Learning • Teamwork provides the opportunity for collaborative learning. • Teamwork keeps members motivated. • People (students, engineering colleagues) are the best motivators of other people. • Teaching others is the deepest form of learning. • Teamwork helps speed up the solution process. • IT IS how engineering professionals work and learn.

11. Team Skills Listen Question Participate Persuade Share Respect Help Let’s take a closer look…

12. Design Group (Team) • Teams that spend time together tend to be successful teams • Respect each other • Listen actively • Consider your response to others • Constructively criticize ideas, not people • Respect those not present • Communicate your ideas effectively • Manage conflict constructively

13. Team Skills • Listen:Listen to other people's ideas. When people are allowed to freely express their ideas, these initial ideas will produce other ideas. • Question:Ask questions, interact, and discuss the objectives of the team. • Persuade: Individuals are encouraged to exchange, defend, and then to ultimately rethink their ideas. 4. Respect: Treat others with respect and support their ideas. 5. Help: Help one's coworkers, which is the general theme of teamwork. • Share: Share with the team to create an environment of teamwork. • Participate: All members of the team are encouraged to participate in the team. (OSU)

14. Scenario: Anthony worked in an engineering firm before he started at SJSU and knows a bit about design and construction. In his efforts to ensure a good project he appoints himself as team leader and tells all the others what to do. What do you think will happen? • The team will build the best turbine structure in the lab • Team members will appreciate Anthony taking charge • Team members will resent his controlling attitude • Anthony will end up doing all of the work himself • C&D

15. What do I expect to get out of E11 teamwork experience? • Complete a project and earn a top grade • Develop/practice/improve teamwork skills • Satisfaction of achievement • Networking and friendships • Peer performance evaluation

16. Teamwork Evaluation on Projects 5 = we did this all of the time 1 = we did no do this at all

17. Team Organization • Define a common goal for the project. • List tasks to be completed. • Assign responsibility for all tasks. • Develop a timeline. • Develop and post a checklist. • Maintain a central archive for all communications. (Drawings, Photos, Report, Presentation) • Communicate all team meetings. • Send reminders when deadlines approach. • Send confirmation when tasks are completed.

18. What are the E11 Teamwork Basics? • Team Formation • Team members: 4 to 6 per team • Team Name • Team Roster: Name, phone, e-mail • Copy to all members and to class Prof. • Member introduction (“getting to know you” ) • Set Ground Rules-Operational

19. E11 Teamwork Basics - Ground rules • Assign a Group Leader • (Project manager, Project Leader, Facilitator, etc.) • (why)? Do we need a boss??????? • Distribute the work among members • Equivalency-Fairness-Balance • Ability-Training-Experience • Time and Effort • Communicate - FREQUENTLY • Do what you promise to do . . . Be accountable • On time • Your best quality work

20. Design Group (Team) • Develop decision making guidelines • Decision by authority (leader) • Expert Member • Average member opinion • Majority • Consensus

21. Resolving Conflict • Acknowledge the conflict – don’t ignore it • Stick to the facts – don’t get personal • Analyze the situation – encourage different points of view • Focus on a solution – don’t get stuck on things you can’t change • Once you decide on a solution – move forward

22. Scenario: On the first project day, the team divided up project duties. Cynthia designed the robot arm, Juan designed the robot chassis, Tri and Robert started the computer programming, and Calvin volunteered to write the report and make the PowerPoint presentation. On testing day their robot still could not complete the specified tasks reliably and the group’s oral report was disjointed and incomplete. What is the most likely cause? • A couple of people are not very smart and they dragged the team down. • The wrong people chose the wrong tasks • The members worked individually without much communication • They didn’t have a strong enough boss who could tell each person what to do • They were basically not working hard enough

23. Team Dynamics - Communication** • Listen actively. • Don't interrupt. • Ask questions. • Be aware of body language and tone. • Use appropriate humor. • Be patient. • Don't express an opinion as a fact. • Explain your reasons. • Compliment each other's ideas. • Evaluate - Do not criticize. • Restate the original idea to be sure it is understood. • Respond, don't react. • Critique the idea, not the person. • Be courteous. • Avoid jargon.

24. Tip - Running a Good Meeting • Plan the meeting – objectives & agenda • Inform the team – when, where, information they need, what they need to prepare • Conduct effectively – follow agenda, one item at a time, manage discussion, maintain focus and pace • Summarize meeting – summarize decisions and action items, send notes out to team

25. Design Group (Team) • Hold effective meetings • Have an agenda • Show up prepared • Pay attention • Schedule time and place of next meeting • Summarize • Assign tasks and responsibilities

26. Scenario: A bunch of things have come up and you aren’t going to be able to complete the task you were assigned before tomorrow’s team meeting. What should you do? • Skip the team meeting because you have nothing to present • Send an email to everyone and tell them you won’t meet the deadline • Go to the meeting and pretend you have it done but left it at home • Figure out when you will be able to complete it and discuss this with group • B & D

27. Team Dynamics • Full Participation • All team members contribute their time and energy to the project. More importantly, all team members participate in the decision making process. • Having a dominant leader may work for the very short term, but will eventually lead to morale problems.

28. Team Dynamics • Trust • Members trust that each member will add value to the project • Members work to ensure that everybody does contribute and that appreciation is expressed for different contributions.

29. Scenario: One of your team members is not good about answering email. He has missed a meeting and you are waiting for a product from him. What should you do? • Discuss team operations at a team meeting. Reiterate/create the team operating rules. • Go tell the professor. You want him off the team! • Send him a nasty email telling him he is spoiling it for everyone. • Call him and find out what is going on • A &D

30. Team Dynamics • While equal contribution from each member is ideal, a true equal division of work may not be always possible. • Doing more than your ‘fair’ share of the work is an opportunity to demonstrate your ability and commitment. • A team’s success is measured by the achievement of the team as a whole. -- Nothing can justify an intentional act that negatively impact the achievement of the team. Examples: • I don’t want to share that information because I spent a lot of time to find it. • I don’t want to do that because that is his job.

31. Project Management • Work breakdown structure • Hierarchical breakdown of tasks and deliverables need to complete project • Activity • Task – action to accomplish job • Deliverable – e.g. circuit or report

32. Project Management • Define for each activity • Work to be done • Timeframe • Resources needed • Responsible person(s) • Previous dependent activities • Checkpoints/deliverables for monitoring progress

33. Finally - Keep in mind that: • Working in a team does NOT mean that you work as a team. • Teamwork does NOT just happen. • Team skills need practice and development. • A team’s success is measured by the achievement of the team as a whole. • Industry values teamwork more than an individual’s ability to contribute.

34. Acknowledgement This presentation is adopted in part from the following web pages: • Student success: http://www.discovery-press.com/catalog/studyengr/instructorsguide.doc • Team Dynamics: http://tlt.its.psu.edu/suggestions/teams/