Skip to content

Team Overview

Find team activity that needs closer review.

Open Team → Team Overview for a combined view of the Teams you can read. This scope may be smaller than the whole organization: Teams you cannot read are left out, and the screen says how many.

  1. Check the selected period and any data-availability notice.
  2. Read the Team summary: completion rate, active users, cost per completion, spend, and the score of each Team with its trend over the last six periods.
  3. Compare Output this period, Risk signals, and People worth a look, and read Tasks in progress.
  4. Follow a Team or a person link to its detail view or to Team Performance or Team Usage & Cost.

Risk signals identify values meeting the screen’s reference criteria: a waste signal, rework, throttling, and spend. They do not establish that an employee is at risk or performing poorly. Review the underlying tasks and available sample before taking action.

Combined views state how a person who belongs to several Teams is counted. A Team scored under a different definition is not shown beside the others, and the screen says so. A Team’s score is a number with no letter or word band. Some totals remain unavailable until the required team data is present. A missing value is not a zero total, and a missing signal section is not proof that no issue exists.

Use the activity and usage figures to identify questions to investigate. Code-change and commit counts describe captured activity, not shipped value. Check team access and visibility when interpreting member information.