Upload
others
View
9
Download
0
Embed Size (px)
Citation preview
• Work in pairs
• Play tic-tac-toe for 3 minutes, scoring each game as follows:
win : 5 pointstie : 0 pointslose : -1 point
• Your goal is to win 30 points
Tic-Tac-Toe
Fall 2004 SE 101 Introduction to Software Engineering 2
Today’s Lecture1. Intro to Software Engineering2. Inexact quantities3. Error propagation4. Floating-point numbers5. Design process6. Teamwork - no web review7. Project planning - no web review8. “To Engineer is Human”9. Professional Engineering10. Software quality - no web review11. Software safety12. Intellectual property
Fall 2004 SE 101 Introduction to Software Engineering 3
Agenda
• Teamwork
• Building a team
• Group decision making and conflict management
Fall 2004 SE 101 Introduction to Software Engineering 4
Teams
A team is a group of people who are working towardsa common goal and whose production is greater thanthe sum of its parts.
Fall 2004 SE 101 Introduction to Software Engineering 5
Effective Teams
Have you ever been a member of a really effectiveteam?
• School project• Athletic team• Work project• Community volunteer project
What was it about the team that made it so effective?
Fall 2004 SE 101 Introduction to Software Engineering 6
Ineffective Teams
Have you ever been a member of an ineffective team?
• A team that completed its mission, but whosemembers hated each other at the end
• A team whose members had a great time workingtogether, but that did not finish the project
What was it about the team and its members thatmade it so ineffective?
Fall 2004 SE 101 Introduction to Software Engineering 7
Characteristics of Teams (vs. Groups)
Discusses, decides,does real work
together
Discusses, decides,delegates
Work Styles
Collective workproducts
Individual workproducts
Deliverables
Team purposeExternal pressure,organizational mission
Motivation
Mutual accountabilityIndividualaccountability
Accountability
Shared leadershiproles
Strong, focussedleader
Leadership
TeamGroup
Fall 2004 SE 101 Introduction to Software Engineering 8
Characteristics of Teams (vs. Groups)
Discusses, decides,does real work
together
Discusses, decides,delegates
Work Styles
Collective workproducts
Individual workproducts
Deliverables
Team purposeExternal pressure,organizational mission
Motivation
Mutual accountabilityIndividualaccountability
Accountability
Shared leadershiproles
Strong, focussedleader
Leadership
TeamGroup
Fall 2004 SE 101 Introduction to Software Engineering 9
Characteristics of Teams (vs. Groups)
Discusses, decides,does real work
together
Discusses, decides,delegates
Work Styles
Collective workproducts
Individual workproducts
Deliverables
Team purposeExternal pressure,organizational mission
Motivation
Mutualaccountability
Individualaccountability
Accountability
Shared leadershiproles
Strong, focussedleader
Leadership
TeamGroup
Fall 2004 SE 101 Introduction to Software Engineering 10
Fall 2004 SE 101 Introduction to Software Engineering 11
Guidelines for team behaviour
Mutual respect, mutual responsibility• Let everyone participate, no one dominate• Listen to other team members; don’t be disruptive• Ask questions when you do not understand• Constructively criticize ideas, not people
Individual responsibility• Complete assignments on schedule• Attend all team meetings; be on time• Keep promises (remember your contract?)
Have fun
Fall 2004 SE 101 Introduction to Software Engineering 12
Building an Effective Team
How would you choose team members to work on aproject with you?
Fall 2004 SE 101 Introduction to Software Engineering 13
Decision Making
In your experience as a member of a group, how didthe group make a group decision?
Fall 2004 SE 101 Introduction to Software Engineering 14
Decision type and quality
Individual Average ofIndividuals
MinorityControl
MajorityControl
ConsensusLow
High
Qual
ity
of
dec
isio
n
Smith, Karl, Project Management and Teamwork, McGraw Hill, 2000.
Fall 2004 SE 101 Introduction to Software Engineering 15
Decision type and time needed
Individual Average ofIndividuals
MinorityControl
MajorityControl
ConsensusLow
High
Tim
e nee
ded
Smith, Karl, Project Management and Teamwork, McGraw Hill, 2000.
Fall 2004 SE 101 Introduction to Software Engineering 16
Conflict
On complex projects, highly talented and motivatedpeople routinely disagree on the best way toaccomplish tasks and how to set priorities.
Its resolution can set the team on either a constructiveor a destructive path.
Fall 2004 SE 101 Introduction to Software Engineering 17
Suppose that one of your group members, Ralph,criticizes all of your ideas in team meetings. Nowyou’ve just learned that he is also saying nasty thingsabout your competency behind your back. You areworried that some of your team members might beinfluenced by him. You are terribly upset and angry.
What would you do?
Conflict Exercise
Fall 2004 SE 101 Introduction to Software Engineering 18
Conflict ManagementHigh Importance
Low Importance High ImportanceRelationship
Go
al
Force
Withdraw Smooth
Confront
Compromise
Smith, Karl, Project Management and Teamwork, McGraw Hill, 2000.
Fall 2004 SE 101 Introduction to Software Engineering 19
Conflict ManagementHigh Importance
Low Importance High Importance
Force
Withdraw Smooth
Confront
Compromise
win-lose win-win
lose-lose
lose-winlose-win
Relationship
Go
al
Fall 2004 SE 101 Introduction to Software Engineering 20
Negotiation is a conflict resolution process by whichpeople who want to come to an agreement try to workout a settlement.
• Confront only when you have the time to jointlydefine the conflict
• Seek to understand the other person’s position andfeelings about the conflict.
• Present your position calmly, rationally, factually.
• Have good insight into your own position (in termsof problems to be solved, not desired solutions)
Confrontation
Fall 2004 SE 101 Introduction to Software Engineering 21
Suppose that one of your group members, Stanley, isnot contributing to the group project:
• Coming late to meetings
• Not coming to meetings
• Not doing work
Conflict Exercise II
Fall 2004 SE 101 Introduction to Software Engineering 22
Summary
An effective team is a small number of people who
• Have complementary skills
• Have a common purpose
• Have common performance goals
• Hold themselves mutually accountable