Gregory M. Kapfhammer
Key Concept
Corresponding Diagram
In-Class Discussion
In-Class Activity
Details in SETP or MMM
May be big differences between extremes
Large teams go slowly because of communication
Small teams of sharp engineers move rapidly
So, why not always use small teams?
Small teams may not be able to build big systems!
A key factor is the time-to-market for software!
Chief Programmer: Designs, codes, tests, and documents
Co-pilot: Supports the Chief Programmer in all tasks
Administrator: Handles money, people, and space
Editor: Revises and improves all documentation
Assistants: Handles all correspondence and files
Program Clerk: Maintains all of the technical records
Toolsmith: Ensures that technical tools are available
Tester: Creates, runs, and reports on test suites
Language lawyer: Understands the programming language
How can we apply these roles in our projects?