Team work
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
701
On Slideshare
701
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
8
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. CE 203 Working in Teams This presentation on Working in Teams was found at: http://www.ccee.iastate.edu/courses/ce203/ce203_start.htm
  • 2. Teamwork …
    • is becoming a more and more common mode of operation in business
    • is replacing top-down, chain-of-command
    • helps to improve:
      • internal processes
      • external relationships with customers and suppliers
  • 3. WHY ?
    • Complexity of problems requires more varied expertise than one person possesses
    • People working together rather than individually generate more and better ideas
    • Diversity results in more widely acceptable solutions
    • Buy-in of whole organization more likely
  • 4. Some things to consider about teaming
    • There are many examples of very successful “team” or “group” work
    • (But) teams don’t guarantee success
      • Most of us are more comfortable working on our own than in a team
      • Most of us are initially apprehensive about “group work”
      • The whole can be “more” or “less” than the sum of its parts
  • 5. Team Success
    • Two primary aspects of teamwork:
      • The Task-the work to be done!
      • The Relationships-interpersonal connections
    • BOTH NEED TO GO WELL FOR SUCCESS!
  • 6. Signs of Successful Teams
    • Meetings start on time
    • Brief meeting minutes are distributed
    • Motivations of team members are known
    • Tasks are clearly understood by all
    • Changes are developed collaboratively
    • Meetings are informal but productive
    • Meetings do not drag on
    • Discussions are focused
  • 7. Signs of Successful Teams (cont’d)
    • Everyone participates
    • Everyone listens - ideas have a fair hearing
    • Independent critical thinking is encouraged
    • Criticism is frequent, open, and frank
    • Disagreements are settled openly
    • Team leader (or other) does not dominate
    • Tasks are completed on schedule
  • 8. Signs of Non-successful Teams
    • Most or all of the work is done by one or two
    • Jobs are segmented and simply assembled
    • Record keeping is poor
    • Communication is sporadic
    • Respect for fellow team members is lacking
    • Conflicts are left unresolved
  • 9. Team Formation Stages (see course packet)
    • Forming
    • Storming
    • Norming
    • Performing
    • Adjourning
  • 10. Team Make Up
    • In the “real world”, often all stakeholders involved in the process or problem
    • In this class, 4/5 class members “randomly” selected
    • In terms of roles (see course packet):
      • Facilitator
      • Leader
      • Recorder
      • Editor
      • Assistant
  • 11. Duties of Different Roles
    • For some common roles and responsibilities, see
      • Course Packet
      • CCE Communication Guide
    • In any case, it is important to assign each of basic responsibilities to SOMEONE!
  • 12. Suggested roles for CE 203 teams
    • Facilitator (temporary - first name on team list?)
      • Oversees the selection of the team leader
      • Often, in “real life”, is not a stakeholder and serves to help the team follow good teaming rules
    • Facilitator (if permanent)
      • Keeps team focused
      • Encourages participation from all
      • Protects members from personal attack (but remains neutral)
      • Suggests alternatives when team is stalled
      • Plays role of “critical evaluator” to avoid groupthink
  • 13. Suggested roles for CE 203 teams
    • Leader
      • Prepares meeting agendas
      • Runs team meetings
      • Keeps the team on track and on schedule
      • Ensures that all report sections have primary authors
      • Assists any/all team members as necessary
      • Mediates conflicts between team members
      • Contributes to the development of the discussion section
      • Picks up all the slack
  • 14. Suggested roles for CE 203 teams
    • Recorder
      • Takes notes at meetings
      • Sends short e-mails with meeting minutes and action items
      • Sends e-mail reminders
      • Provides meeting minutes for inclusion in the report
      • Assumes the role of leader if necessary
      • Contributes to the development of the discussion section
      • Works with the assistant to produce the final plots and tables
  • 15. Suggested roles for CE 203 teams
    • Editor
      • Assembles the draft report
      • Contributes to the development of the discussion section
      • Does the final proof reading and final editing of the report
      • Makes report copies
      • Turns in the report on time
  • 16. Suggested roles for CE 203 teams
    • Assistant (2?)
      • Contributes to the development of the discussion section
      • Assists the editor with the first draft
      • Proof reads and edits the draft report
      • Produces final plots and tables
      • Assists editor with final draft and proofing
  • 17. Features of Effective Team Meetings
    • Introductions
    • Location
    • Attendance and Promptness
    • Agenda
    • Review
    • Goals
    • Minutes/Action Items
      • Tasks
      • Responsibilities
      • Schedule
  • 18. Team Ground Rules
    • Reach decisions by consensus (not by majority vote)
    • Listen to what others have to say
    • Come to meetings prepared
    • Arrive at meetings on time
    • Expect contributions from everyone, domination by no one
    • Keep good records of your work
    • Treat everyone with respect and deal openly and intelligently with conflict
  • 19. Techniques for generating ideas
    • Brainstorming
      • a.k.a. Itemized Positive Response or IPR
      • short time limit often specified (5-10 min.)
      • ideas spoken (and recorded) as they occur
      • criticism/evaluation not allowed during idea-generating session
      • evaluation period often follows (break first?)
    • Synectics (adapting an idea or solution from one field to solve a problem in another field)
    • Check-off list (modify existing solution)
  • 20. Avoid “groupthink”
    • Only a few alternatives are ever considered
    • Initial decisions are never re-examined
    • No time taken to improve rejected alternatives
    • Experts outside the group are not consulted
    • Potential difficulties are not discussed
  • 21. More information on teaming…
    • Course packet websites, including:
      • http://www.analytictech.com/mb021/teamhint.htm (good summary, keen and sometimes humorous observations)
      • http://www.cba.neu.edu/~ewertheim/steams/ovrvw2.htm (thorough, fairly long)
    • Personality types
      • http://www.humanmetrics.com/cgi-win/JTypes1.htm (Jung-Myers-Briggs typological approach to personality)
  • 22. Team Assignments
    • Several team “projects” this semester
    • Roles should be rotated
    • Grading
      • Each member gets the team grade unless, based on peer evaluation, they do not “contribute”