Team Dashboards

Updated 6 months ago by Betsy Rogers

This dashboard provides teams with a set of operational tools to manage their day-to-day tasks. Use these dashboards to identify and mitigate quality and delivery risk in real-time in order to constantly improve delivery and quality of the team and each team member.

You can switch between teams and iterations by clicking on the menus at the top of your dashboard page.

Team dashboards display top-level individual metrics of your team members. You can set these dashboards to just display team-level metrics by enabling Team Only Mode. You can learn more here: Enabling Team-Only Mode

Current Iteration View

The team dashboard has two different views. The default represents the activity of the team in it's current active iteration. This view is very focused on operational branches your team is working on. The second view is a retrospective view for previous iterations. In this view, the focus is on data that helps the team understand points for improvement and points to preserve. This view is aimed at the retrospect process that a team is doing when the iteration ends.

Work Breakdown

This graph dissects the lines of code added or changed during this iteration or week. Click on the graph icon to see changes in your work breakdown over the past few iterations. Click on the button to see all active branches in the activity tab.

New Work - Newly added lines of code.

Refactor - Changes to code that is over 21 days old.

Rework - Changes to code that is less than 21 days old.

Cycle Time

Cycle time will be displayed as an average or percentile based on your account settings. Click on any segment of cycle time to see the branches that contributed to each segment of time. Click on the button to see all active branches in the activity tab. You can learn more about how LinearB calculates cycle time here: How is Cycle Time Calculated?

Team Members

Team members included in your team will be listed in this center module. You can edit your team lineup by clicking on the pencil icon at the top of this module.

Burnout Alert A team member has worked 90% of the days in a current sprint (we start monitoring for burnout at 6 days into a sprint).

WIP Overload If a team member has over 6 active branches, this alert will appear.

WIP (Work in Progress)

The number of branches this user currently has open.

Reviews

The number of reviews this user has submitted.

Done

The number of merged/deployed PRs this user has submitted.

Active Days

The number of days during a sprint that a team member has shown activity. This can be commits, comments, or reviews.

Goals Notifications

Notifications related to your team goals can be sent to your team Slack or MS Teams channel, they will also appear on your dashboard here. Click on the gear icon in this module to customize your team goals, or view the team goals report. You can click on any individual goal to see more branches that may be in danger of breaching this goal.

Retrospect Iteration View

The retrospect provides is less operational and more analytical its purpose is to provide the team with tools to perform a retrospect review and get insights about the ended iteration. For that reason, the retrospect view includes metric summaries and metric trends as well as information about the ended iteration.