Team Dashboards

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.

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.

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?

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 branches that sum up this 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.

Customizing Your Top Widgets

The three widgets in the top right corner of your dashbaord can be customized to show a number of metrics. You may pick three metrics for your team to view and focus on. To edit these widgets, click on the pencil icon on any of these dashboards, and check the metrics important to your team.

Team Members

Team members included in your team will be listed in this center module. If your LinearB instance has individual metrics enabled, you can click on any team member to see the branches they have worked on in your set time-range. You can also click the arrow corner in the top right of this widget to see individual metrics.

Learn more about enabling and disabling individual metrics in LinearB here: Enabling Team-Only Mode

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.

Top Reviewer The team member who has reviewed the most PRs in your current iteration is your Top Reviewer!

Goals and Goals Notifications

Teams can configure goals based on

Goals

Hover over any flag to see which goals your team is meeting. Segments with green flags are goals that are being reached, and orange and red flags are goals that are not yet being reached.

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.

Delivery

Delivery metrics are available once your team has linked their PM boards via your team settings. You can see what percent of your current sprint or kanban board's issues are in progress, done, and yet to do. Click on any segment to view your team activity on these PM tickets in LinearB's Pulse view

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.

Reviews

Shows the number of reviews and the average comments per review over time during the iteration.

Deployment Frequency

Shows the number of deploys per day as well as the total number of deploys detected.