Team Hub
Features
Team Hub
The gist
Every special ops team needs a map - this is it. Run your sprint retrospectives or investigations with key data on processes & codebase health:
Team members;
List of modules (codebase assets) assigned to the team;
Where team has applied it's effort in the selected period;
What other team have made changes to our modules;
Cycle time, throughput, autonomy and confidence metrics;
Map
Selected team
Team Hub Map is constructed from a perspective of a selected team (Green color card on the image above).
Team card lists all your team members (in case something is odd, navigate to Org. chart to make changes in your team).
Lines that originate on the team card and point to modules or repositories represent WIP & Merged feature branches observed in the selected period. Line color and percentage displayed correlate with autonomy widget and help understand if we mess with code owned by other domains and teams or not.
Clicking on View button will redirect to Effort Trace Map where you will be able to investigate changes made by the team on a lower, more detailed level.
Other teams
In case other teams have changed modules of the selected team, they will be displayed on the map. Click on the team card to see their impact.
Other teams are sorted based on organizational structure. Teams from the same domain will be displayed on the left, and teams from other domains will be displayed on the right.
Module groups
All modules and codebase elements are organized into groups according to ownership. The source of truth for ownership can vary, i.e. CODEOWNERS files or assigned through Codigy.
Depending on the selected map filter, module cards can either display the throughput or cycle time of the selected team. Click on the module to access Module Insights Map.
Effort in the unmodularized codebase
In case a team is doing work in the files that are not part of modules, the map will organize files according to ownership. Source of truth for ownership in CODEOWNERS file. In case you don't have such a file, all files will be marked as "Files not in CODEOWNERS".
Map Filter
You can switch between feature count and cycle time displayed on the module cards using a filter toggle in the bottom right corner of the map.
Team hub widgets
The team hub map visualizes the relationships between the team and the codebase. Widgets give you total key metrics for the team. This way you have the whole context for your sprint retrospectives or investigations. Widgets can be hidden if you want to focus on the map only.
Autonomy widget
This simple numerical value helps you understand if the team is able to achieve its goals only by working with the code that is assigned to them. In case they need to change files that belong to other teams or domains, you will be able to see the extent of this issue.
Why is this important?
Low autonomy means lower efficiency and a higher risk of defects:
Changing the code that belongs to other teams usually requires their review and approval, which takes longer;
Stepping on each other's work and doing changes in code that you are not familiar with increases the chance of defects;
How does this work?
All files are grouped into categories based on ownership. Files that belong to modules use owners assigned in Codigy, files that are not part of any modules use CODEOWNERS file if it is available.
All team changes are sorted into categories with a breakdown available in the interface. Team autonomy is then calculated, it is a sum of activity in modules and files where the team is mentioned as an owner.
Confidence widget
It plays an important role in helping you assign the most experienced team for each area of the code (file, folder, repository, or module).
Why is this important
1. If a team has high confidence in the modules & files that are assigned to them - it is a great sign that shows you have picked the right team to maintain and protect this code.
2. If a team has high confidence in modules & files that are assigned to other domains - it is an indicator that either owner was not assigned correctly or files are shared between teams and need to be decoupled.
In case you spot something odd in the Confidence score, you can click on the "View on map" to see Team confidence patterns on an interactive Ownership map.
How does this work
Similar to the Autonomy widget, Confidence looks into the activity patterns of the team in files grouped by ownership. However, Confidence:
Is based on observing patterns in a rolling period of 6 months which evens out data volatility and works well with the limitation of human memory;
Takes rewrites into account (i.e. if a file was originally authored by the team 1 month ago, but was completely rewritten by another team afterwards, the confidence of the initial authors will drop to 0%);
Cycle time widget
Learn how long it took for a team to complete a feature on average in the selected period. Delta compares the cycle time with the previous period of the same length. Click on the details to see the stage breakdown (Development, Review, Integration).
Codigy takes into an account work-in-progress features, as well as completed in the selected period. Stale & ignored bracnhes are excluded.
Depending on the selected scope, Codigy will show Team Cycle time across all repositories or a specific one.
Use cases:
1. Drive your Team sprint retrospective meetings with data & visualizations (Engineering teams & Engineering managers);
2. Highlight inefficiency hotspots and get refactoring and decoupling targets.
3. Understand how teams interact with each other and the codebase (Staff & Principal engineers);
Have a question?
Need a more detailed explanation about any of the Codigy metrics or mechanics? Fire away in our community chat on Discord, or Slack channel (in case your organization is using our Slack Connect support) 👌
This page was last revised on July 10, 2023
Back to main