University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 1 Lecture 22:!Managing People"Organizational Structures"Building high Performance teams""Discussion: "How to make team assignments work in undergraduate courses?"University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 2 Starting point"You have a project"You have been given a team"a mixed set of skills"a mixed set of motivations"Problem:"How do you get everyone to work together?"…and get the job done?"University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 3 Scaling up…"Communication overhead is exponential"""""Exploit Modularity:"? ? ? ? ? ? ? ? help!!? X University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 4 Team Organization"""Conwayʼs Law:"The structure of the software reflects "the structure of the organisation that built it"filter filter filter filter filter filter pipe pipe pipe pipe pipe pipe pipe pipe object object object object object method invocation method invocation method invocation method invocation broadcast medium agent agent agent agent announce event announce event listen for event listen for event broadcast medium Layer N Layer N-1 Layer 2 Layer 1 blackboard (shared data) agent agent agent agent agent agentUniversity of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 5 Coordination Mechanisms"Direct supervision"simple structure - little formalization"Standardization of work processes"“machine bureaucracy”"e.g. mass production and assembly"Standardization of work outputs"“divisionalized form”" e.g. each division has performance targets"Standardization of worker skills"“professional bureaucracy”"e.g. hospitals, law firms,…"Mutual adjustment"“adhocracy”"e.g. skunkworks, high innovation, open source teams"University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 6 Hierarchical Teams"Team structure = top down decomposition"Disadvantage: vertical communication is ineffective"Project!Manager!OS interface!Manager!Database!Manager!Application!Manager!GUI!Manager!Documentation!Manager!Testing!Manager!Development!Manager!Design!Manager!Mouse!Manager!Screen!Manager!Sound!Manager!GUI Lib!Manager!University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 7 Chief Programmer Teams"Based on hospital surgical teams"Chief programmer is not a manager - concentrates on technical issues"Chief!Programmer!Testers!Librarian!Senior!Programmers!Administration!Assistant!Chief Programmer!Junior!Programmers!Project!database!University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 8 Matrix Organization"Identify specific skill sets"Assign people to projects according to needed skills"People work on multiple projects"real-time program-ming"graphics"data-bases"QA" Testing"Project 1" X" X" X"Project 2" X" X" X" X"Project 3" X" X" X" X"University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 9 Open Source - Onion Model"University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 10 General Principles"Use fewer, better people"Performance of best programmers better by an order of magnitude!"Fit tasks to capabilities and motivations of people"Help people to get the most out of themselves"opportunity to accept new challenges and be rewarded"Balance the team"E.g. team players vs. star performers"Practice “egoless” programming"Remove people who do not fit the team """University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 11 High Performance Teams"Nurture a team culture"A team is not a family"Team members help one another, but donʼt tolerate freeloaders"Instill the right values"Discuss examples"Reward people who uphold the team values"Build trust"All feedback should be constructive"Foster lively & healthy debate about issues and risks"Effective Communication"Use face-to-face whenever possible"Use phone or F2F to resolve email debates"Get everyone using IM"Encourage social events for the team"Physical layout of office space is important"University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 12 Organizational Clarity"Things every team member should know:"What is the mission of the team?"What is the vision for the system to be delivered?"How will you measure team success?"Who are the project stakeholders?"How will you measure project success?"Who is responsible for what?"What procedures should you follow to do the work?""University of Toronto Department of Computer Science © 2012 Steve Easterbrook. This presentation is available free for non-commercial use with attribution under a creative commons license. 13 Who can change the code?"Collective Ownership"Anyone can change any code or model"Works well for small teams"Promotes shared responsibility"(Needs good version management tools)"Change Control"Each sub-team can only change their subsystem"Reduces unexpected problems when code changed by others"Promotes development of expertise"More important on larger
View Full Document
Unlocking...