Measure
People, teams, and Scorecard
Map contributors to teams and compare delivery systems with appropriate context.
- Audience
- engineering leaders, managers
- Required role
- Manager or administrator with people and team management capability.
- Product access
- Measure
- Navigation path
- Measure > People, Measure > Teams, and Measure > Scorecard
Outcome
Create reliable team groupings and compare delivery systems with the context required for interpretation.
Before you begin
- Imported GitHub identities
- A defined team ownership model
Confirm identity mapping
Review unmatched or duplicate contributor identities before relying on team totals. Link aliases only when you can verify they represent the same person.
Create teams
Create teams that match stable delivery ownership, then add people and repositories according to the organization model. Revisit membership after reorganizations.
Read the Scorecard
Use the Scorecard to view delivery, quality, AI attribution, and operational signals together. Open a metric to inspect the underlying period and evidence.
Choose a useful comparison
Compare a team with its own prior baseline or with a peer doing similar work. Record differences in on-call load, platform responsibility, repository maturity, and release process.