Teamwork

1
Teamwork

• Robotic Systems and Science
• Wed 22-Feb-06
• Prof Charles P Coleman, MIT AA

2
Systems

• People,
• Product,
• Process
• Deliver
• functionality

3
Teamwork Systems

• Groups of people
• conceive
• design
• implement and
• operate
• systems

4
Teamwork Systems

• Getting groups
• of people to
• conceive
• design
• implement and
• operate
• systems isnot easy

5
Keys for Success

• Project Mgmt
• Time
• Resources
• Risk

• Teamwork
• Communication
• Coordination
• Roles Responsibilities
• Motivation!

• Design
• Process
• Analysis

• Tools
• Functional Requirements
• Trade Studies

• Tools
• WBS
• Gantt Chart

• Tools
• Comm Plan
• Roles Resp
• Ground Rules
• Effective Mtgs

6
Teamwork Communication Plan

• Communication Plan
• Where is everyone?
• How can I contact you?
• What is the best way to contact you?
• When are you available?
• How are we all going to keep in touch?
• Where is our project information going to be
  stored?

7
Teamwork Roles ResponsibilitiesGround Rules

• Roles Responsibilities
• Who is doing what?
• Ground Rules
• How do we interact with each other?
• How are we going to treat each other?
• Any undisclosed assumptions about behavior?
• How would I like for you to communicate with me?
• Roles decided at beginning of meeting
• Be on time for arrival and breaks
• Be prepared for discussion and decisions
• Dont shoot the messenger
• Turn your cellular phone off

8
Teamwork Effective Meetings

• Effective Meetings
• Never meet without an agenda!
• If you are meeting w/o an agenda make one up
  first thing!
• Try facilitation.
• Assign facilitator, note taker, and timekeeper
  for every meeting.
• Rotate responsibilities!
• Keep it simple!!

9
2001 Requirements and Resources

• Develop a system to participate in an aerial
  competition
• System must be ready by early May 2001
• Fly four laps two empty and two with payload
• Complete laps in shortest time
• Carry as much weight as possible
• 5 people, 9 weeks, 4hrs/person/week, kit,
  supplies, flight training

10
2002 Requirements and Resources

• Develop a system to participate in an aerial
  competition
• System must be ready by late April 2002 - early
  May 2002
• Fly two laps empty and then as long as possible
  with egg payload
• Dont crack or break egg during handling,
  loading, flight, landing
• 5 people, 9 weeks, 4hrs/person/week, kit,
  supplies, flight training

11
2003 Requirements and Resources

• Develop a system to participate in an aerial
  competition
• System must be ready by late April 2003 - early
  May 2003
• Endurance flight with operations and egg payload
• Dont crack or break egg during handling,
  loading, flight, landing
• 5 people, 9 weeks, 4hrs/person/week, kit,
  supplies, flight training

12
Expectations

• We decided we'd try doing without a
  "facilitator", "time-keeper", and "note-taker"
  for now and see how it goes. If meetings aren't
  being productive, we can always add them in
  later, but we don't think we'll need them for
  now.
• The main expectation/assumption we came up with
  was that everyone should show up on time to our
  meetings.

13
Expectations

• We expect from each member not only to put in the
  required amount of work each week but to follow
  through with what they say they will do, respect
  team members, and be able to trust each member of
  the team.
• We decided as a team that winning isnt
  everything, we will give winning a fair shot, but
  do not expect to say up nights, and burn
  ourselves out in order to win.

14
Ground Rules in Action

• Communication
• Youre ugly.
• I feel that you are communicating in an
  insulting manner.
• Okay, I feel that you are ugly.
• Thats much better.

15
Teamwork
Which one was your team? Why?
16
When its good

• I am so proud of our plane and my group! We made
  an excellent plane that actually flew and we were
  able to keep our sanity throughout it all. We
  didnt fight (too much) and I made some really
  great friends. ? So our plane didnt carry as
  much payload as we expected it to, but it flew
  happily and I was happy with it.

17
When its good

• Yes Im proud of the system, especially the
  ability of our team to work together to
  accomplish what we set out to do. We could have
  spent a little more time but instead we decided
  to stay sane. That was also a primary goal, and
  Im glad we ended up not being at each others
  throats.

18
When its good

• I believe that as a team we worked extremely well
  together. We were tolerant with each other,
  always trying to maintain constructive criticism
  and respect each others opinion, in every
  situation. We learned to depend on each other
  very much and had to pull each other out of the
  hole

19
When its bad

• Uh, you have to ask? Group dynamics.

20
When its bad

• There were frustrating momentsThe dynamic of my
  group when we sat together to do a System Problem
  did not work the way I like. Basically it was a
  disorganized meeting, with everybody giving ideas
  but without really reaching a consensus. We could
  spend 1 or 2 hours without doing any productive
  work

21
When its bad

• When we had to divide up the work on the design
  problems, it seemed like we all just did our
  stuff and attached it in one ugly mess to turn
  itAnother period of unorganization was
  building the plane. We never knew exactly when we
  were going to meet.I guess thats more of a
  problem of communication, though

22
When its bad

• Trying to get our group together to work on the
  plane/assignments earlier than the Thursday night
  before it was due. Nobody was willing to work on
  Friday night (especially me). Saturdays were
  filled with other commitments people had such as
  sports, sleep, etc. Sunday, we worked on the
  Unified problem set, which took all of that day
  and Monday. Tuesdays were always shot because of
  a 16.070 problem set due the next day. Wednesdays
  were usually used to study for the usual Unified
  test on Thursday. This left Thursday nights to
  complete the entire assignment.

23
Teamwork
Which one was your team? Why?
24
(Mis) Communication
25
(Mis) Communication
26
(Mis) Communication
27
Communication

• What was the most gratifying or professionally
  satisfying part of the project?
• Winning, especially when no one else believed we
  could.

28
Active Learning Self Reflection

• 3 important ideas you learned about teamwork
• 2 concerns you still have about teamwork
• 1 step you will take related to teamwork

29
Project-based Learning

• Backup

30
Kit Diversity Aircraft Dragonfly
http//www.flydma.com/old/planes.html
31
Project-based Learning

• Comments and Data

32
2001 - 2003 Performance
33
2001-2003 UAC Performance
34
Spring 2002System Problem Schedule
35
Spring 2003System Problem Schedule
36
2001 Metric

• Metric
• L1 L2/(1mp/ma)L3
• L1 empty lap time sec
• L2 weighted lap time sec
• mp/ma mass of payload/mass of empty aircraft
• L3 pit crew time and/or repair time. 3min max
  regardless of actual. sec

37
2001 Performance
38
2001 Performance
39
2002 Performance
40
2003 Performance