Team Size

Description

The complexity of team management grows as team size increases. Communication between team members and the integration of concurrently developed software becomes more difficult for large teams, as described by Brooks. Small teams, relative to the size of the project, may be resource-constrained. Therefore, we track the number of people engaged in software development for the project, categorized by project role. To enable normalizing effort and calculation of productivity, we record average hours per week for each person in their primary role.

The four roles defined for SP-EF are:

• Manager (e.gr. Project Management, Requirements Engineer, Documentation, Build Administrator, Security),

• Developer (Designer, Developer),

• Tester (Quality Assurance, Penetration Tester, External Penetration Tester),

• Operator (User, Systems Administrator, Database Administrator),

Data Collection

Count managers, developers, and testers dedicated to the project under study.
Survey project team to establish each member’s time commitment to the project.

Count When working with a project in progress, count people currently engaged on the project, noting roles and whether they are full-time or part-time on the project. When working with historical project data, sort participants by their number of commits (or bug reports) and count participants contributing the first 80% of commits (bug reports) to estimate development team size and testing team size.

Per team member data:

• Project Role Values: Manager, Developer, Tester, Other.
• Average Hours Per Week: 0.0 - 99.9

Team size: Summary by Project Role, Count, Average Hours Per Week