1. Slide 1 Teams l Most products are too large to be completed by a single software professional with the given time constraints l You will work within a team of professionals

2. Slide 2 Teams l From Brooks’ Mythical Man Month, any successful team needs: A goal A division of labor A leader

3. Slide 3 Programming Teams l A product must be completed within 3 months, but 1 person-year of programming is still needed l Proposed Solution If one programmer can code the product in 1 year, four programmers can do it in 3 months l Reality Four programmers will probably take nearly a year The quality of the product is usually lower

4. Slide 4 Task Sharing l If one farm hand can pick a strawberry field in 10 days, ten farm hands can pick same strawberry field in 1 day l One woman can produce a baby in 9 months, but nine women cannot possibly produce that baby in 1 month

5. Slide 5 Task Sharing l Unlike baby production, it is possible to share coding tasks between members of team l Unlike strawberry picking, team members must interact in meaningful and effective way Leads to communication problems

6. Slide 6 Communications Problems l Example: There are three channels of communication between 3 programmers working on project. The deadline is rapidly approaching but the code is not nearly complete l “Obvious” solution: Add a fourth programmer to the team

7. Slide 7 Team Organization l Teams are used throughout software production l Especially used during implementation phase

8. Slide 8 Team Organization l Two extreme approaches to team organization Democratic teams Chief programmer teams

9. Slide 9 Democratic Team Approach l Problem: programmers can be highly attached to their code l Proposed solution: egoless programming

10. Slide 10 Democratic Team Approach l Proposed solution: egoless programming Restructure the social environment Restructure programmers’ values Encourage team members to find faults in code A fault must be considered a normal and accepted event The team as whole will develop a group identity Modules will “belong” to the team as whole

11. Slide 11 Democratic Team Approach l A group of up to 10 egoless programmers l Group working for a common cause with no single leader l Emphasizes team identity and mutual respect

12. Slide 12 Strengths of Democratic Team Approach l Democratic teams are enormously productive and produce high-quality code l They work best when the problem is difficult l They function well in a research environment

13. Slide 13 Weaknesses of Democratic Team Approach l Management issues l Egos still involved l Number of communication channels involved

14. Slide 14 Weaknesses of Democratic Team Approach l A 6-person team has fifteen 2-person communication channels

15. Slide 15 Chief Programmer Teams l Six programmers, but now only 5 lines of communication

16. Slide 16 Chief Programmer Teams l Two key aspects Specialization Each member of team carries out only those tasks for which he/she has been trained Hierarchy The chief programmer directs all actions of the other members of the team and is responsible for every line of code

17. Slide 17 Roles of Classical Chief Programmer Teams

18. Slide 18 Roles of Classical Chief Programmer Teams l Chief programmer Successful manager and highly skilled programmer Does the architectural design Allocates coding among the team members Writes the critical (or complex) sections of code Handles all the interfacing issues Reviews the work of the other team members Is personally responsible for every line of code

19. Slide 19 Roles of Classical Chief Programmer Teams l Back-up programmer Must be in every way as competent as the chief programmer Must know as much about the project as the chief programmer Does black-box test case planning and other tasks that are independent of the design process

20. Slide 20 Roles of Classical Chief Programmer Teams l Programming secretary (librarian) A highly skilled, well paid, central member of the chief programmer team Responsible for maintaining the program production library (documentation of project) Programmers hand their source code to the secretary who is responsible for Conversion to machine-readable form, Compilation, linking, loading, execution, and running test cases

21. Slide 21 Roles of Classical Chief Programmer Teams l Programmers work on detailed design and coding under the direction of the chief programmer All other aspects are handled by the programming secretary

22. Slide 22 The New York Times Project l Chief programmer team concept first used in 1971 by IBM to automate the clippings data bank of The New York Times l Chief programmer—F. Terry Baker

23. Slide 23 The New York Times Project l 83,000 source lines of code (LOC) were written in 22 calendar months, representing 11 person- years l After the first year, only the file maintenance system had been written (12,000 LOC) l Most code was written in the last 6 months l 21 faults were detected in the first 5 weeks of acceptance testing l 25 further faults were detected in the first year of operation

24. Slide 24 The New York Times Project l Principal programmers averaged one detected fault and 10,000 LOC per person-year l The file maintenance system, delivered 1 week after coding was completed, operated 20 months before a single failure occurred l Almost half the subprograms (usually 200 to 400 lines of PL/I) were correct at first compilation

25. Slide 25 Why Was the NYT Project Such a Success? l Prestige project for IBM First real trial for PL/I (developed by IBM) IBM, with superb software experts, used its best people l Very strong technical backup l F. Terry Baker Superprogrammer Superb manager and leader His skills, enthusiasm, and personality “carried” the project

26. Slide 26 Strengths of Chief Programmer Team l Proven success l Numerous successful projects have used variants of Chief Programmer Team

27. Slide 27 Weaknesses of Chief Programmer Team l Chief programmer must be a highly skilled programmer and a successful manager l Back-up programmer must be as good as the chief programmer l Programming secretary does only paperwork all day

28. Slide 28 Beyond CP and Democratic Teams l We need ways to organize teams that Make use of the strengths of democratic teams and chief programmer teams, and Can handle teams of 20 (or 120) programmers

29. Slide 29 Beyond CP and Democratic Teams

30. Slide 30 Larger Projects

31. Slide 31 Extreme Programming Teams l Pair programming All code is written by two programmers sharing a computer

32. Slide 32 Advantages of Pair Programming l Test cases drawn up by one member of team l Knowledge not all lost if one programmer leaves l Inexperienced programmers can learn l Centralized computers promote egoless programming

33. Slide 33 Team Organization l There is no one solution to the problem of team organization l The “correct” way depends on The product The outlook of the leaders of the organization Previous experience with various team structures