An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004 Stephen R. Schach [email protected] 12Chapter OverviewTeamsTeam OrganizationTeam Organization (contd)Slide 7Slide 8Slide 9Slide 10Brooks’s LawBrooks’s Law (contd)Slide 13Slide 14Slide 15Traditional Chief Programmer TeamsTraditional Chief Programmer Teams (contd)Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23Slide 24Modern Hierarchical TeamsModern Hierarchical Teams (contd)Slide 27Slide 28Slide 29Slide 30Slide 31Slide 32Slide 33Slide 34Slide 35Other Ways of Organizing TeamsSynchronize-and-Stabilize TeamsSynchronize-and-Stabilize Teams (contd)Slide 39Slide 40Slide 41Slide 42Slide 43Slide 44Slide 45Slide 46Slide 47Extreme Programming TeamsExtreme Programming Teams (contd)Slide 50Slide 51Slide 52Slide 53Slide 54Pair ProgrammingPair Programming (contd)Slide 57Slide 58Slide 59Slide 60Slide 61Slide 62Slide 63Slide 12.1Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. An Introduction toObject-Oriented Systems Analysis and Design with UML and the Unified Process McGraw-Hill, 2004Stephen R. [email protected] 12.2Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. CHAPTER 12TEAMSSlide 12.3Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter OverviewTeam OrganizationTraditional Chief Programmer TeamsModern Hierarchical Teams Other Ways of Organizing TeamsSlide 12.4Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. TeamsEvery information system development project needs competent, well-trained information technology professionalsHaving the right people is not enough–Teams must be organized so that the team members work productively in cooperation with one anotherSlide 12.5Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Team OrganizationMost information systems are too large to be completed by a single information technology professional within the given time constraints–The work must be assigned to a group of professionals organized as a teamSlide 12.6Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Team Organization (contd)Suppose that the analysis workflow has to be performed within 3 monthsSuppose further that 1 person-year of analysis is involved–(A person-year is the amount of work that can be done by one person in 1 year)Slide 12.7Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Team Organization (contd)The solution is apparently simple: –If one systems analyst can perform the workflow in 1 year–Four systems analysts can do it in 3 monthsIn practice, however,–the four systems analysts may take nearly a year, and –The quality of the resulting information system may be lower than if one systems analyst had coded the entire information systemSlide 12.8Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Team Organization (contd)Some tasks can be shared, but others must be done individually–If 1 farmhand can pick a strawberry field in 10 days,–The same strawberry field can be picked by 10 farmhands in 1 dayHowever–One elephant can produce a calf in 22 months, but–Twenty-two elephants cannot produce a calf in 1 monthSlide 12.9Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Team Organization (contd)Tasks like strawberry picking can be fully sharedTasks like elephant production cannot be shared at allSlide 12.10Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Team Organization (contd)Unlike elephant production–It is possible to share analysis tasks between members of a teamUnlike strawberry picking–Analysis team members have to interact with one another in a meaningful and effective waySlide 12.11Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Brooks’s LawKeith, Lisa, and Mary are working on the projectA deadline is rapidly approaching, but–The task is not nearly completeThe obvious thing to do –Add a fourth professional (Norman) to the teamSlide 12.12Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Brooks’s Law (contd)Communication channelsSlide 12.13Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Brooks’s Law (contd)When Norman joins the team–The other three to explain in detail what has been accomplished to date and what is still incompleteThat is, adding personnel to a late information system project makes it even later–This principle is known as Brooks’s Law –Fred Brooks observed it in the 1960s while managing the development of OS/360»An IBM mainframe operating systemSlide 12.14Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Team Organization (contd)In large organizations, teams perform every workflow–But especially the implementation workflow–Programmers work independently on separate modulesIn some smaller organizations–One individual performs the requirements, analysis, and design workflows–The implementation workflow is performed by a team of two or three programmersThe implementation workflow is therefore a prime candidate for task sharingSlide 12.15Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Team Organization (contd)Teams are most heavily used for the implementation workflow–The problems of team organization are most acutely felt during implementationIn the rest of this chapter, team organization is presented within the context of implementation–However, the problems and their solution are equally applicable to all the other workflowsSlide 12.16Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Traditional Chief Programmer TeamsThere are eleven 2-, 3-, and 4-person communication paths in this four-person team–(See textbook for details)Slide 12.17Copyright © 2004 by The McGraw-Hill Companies, Inc. All rights reserved. Traditional Chief Programmer Teams (contd)A team organized this way is unlikely to be able to perform 24 person-months of work in 6 months–Many hours are wasted in meetings involving two or more team members at a time»(A person-month is the amount of work one person can do in one month)Slide 12.18Copyright © 2004 by The McGraw-Hill Companies, Inc. All