Teams Overview

How are all your teams tracking?

Purpose

The teams overview gives you a quick glance at some key statistics for each team and how they are tracking in the aggregate. This report helps you to detect anomalies across teams and allows you to drill down further for investigation. This overview assists you in prioritising when to spend your time and management effort.

Improvement Actions: Logilica's teams overview helps to get insights across teams. Teams with outlier KPIs might need your help or additional resourcing.

Explanations

Some of the information in this report includes aggregated information such as:

Active Developers: The number of engineers who were opening a PR. If the headcount stays the same, you expect a roughly even trend.

Cycle time: The PR lifecycle time from the first commit to being merged/closed averaged out across all teams.

Work Focus: The predominant type of code changes — adding new code, reworking recently written code (your own or others'), or maintaining older, established code.

Besides this, there is a breakdown for each team with statistics including:

Active Developers: The number of engineers who were opening a PR.

WIP: Work in progress about opening PRs in the reporting period, but not yet merged/closed.

Done: Number of PRs closed in the reporting period.

Cycle time: The PR lifecycle time from the first commit to being merged/closed.

Breakdown: The lifecycle breakdown of each PR showing its Coding, Response, Review, and Integration time.

Work Activities: The predominant type of code changes — adding new code, reworking recently written code (your own or others'), or maintaining older, established code.

Risk: This counts risks, including:

• Stale: A PR that has been opened but did not progress from one stage to another within a pre-defined time.

• Long Running WIP: A PR that has been opened but not merged within a pre-defined time. This PR might be stuck or forgotten.

• Risky Change: A PR that potentially deserves more attention because it is unusually large or far-reaching — for example changing a high number of lines, spanning many commits, or touching many files.

• Complex Review: A PR that potentially deserves more attention because its review involved unusually high effort — for example a high volume of review comments, multiple review cycles, or several active reviewers.

• Merged Outside Process: This identifies PRs that are merged, but did not follow a standard quality process and were not reviewed or not approved.

Good to Know

A degree of caution should be applied when comparing teams by aggregated numbers. Different teams have likely different work styles and tasks. For instance, backend and frontend teams often have different cadences and a different focus. As such this should be taken as a team performance comparison, but rather to glean signals for follow-up actions.