How to work with a team dashboard

How to work with a team dashboard

A team dashboard is the "home" of the team. 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.

Team dashboard breakdown

The team dashboard has two different views. The first is "real time" view that represents the activity of the team in the current "active" iteration. This view is very focused on operational and real-time problem solving issues. The second view is a retrospect view for past iterations. In this view the focus is on analytical data that helps the team understand its points for improvement and points to preserve. This view is aimed for the retrospect process that a team is doing when the iteration ends.

Current Iteration view

In current iteration view we show team and team members information about current iteration:

  1. Team Cycle Time - The cycle time widget shows the cycle time for all the branches that were done by the team members during the current iteration. The colors of the different steps indicates how the times of the team compares to the industry benchmark times.

  1. Team Work Breakdown - The work breakdown widget shows the ration of new work, rework and refactor for all the code changes that were done by the team members during the iteration. This widget also shows the total code changes done by the team members during the iteration.

  1. Team Members - The team members widget shows the activity summary for all the team as well as each member of the team. This widget shows the WIP, Done, Reviews and active days for each team member and for the team. Members that are "spread too this" (Have 10 or more active branches in work) and members that are idle (have 0 active branches in work) will be noted. For reviews number for each member will also have a background circle that indicates the review depth for the member. For "Done" number there will be a background circle that indicates the total number of code changes in these branches.
    1. WIP: Work in Progress. The number of branches this user currently has open.
    2. Reviews: The number of reviews this user has submitted.
    3. Done: The number of merged/deployed PRs this user has submitted.
    4. Active Days: The number of days during a sprint that a team member has shown activity. This can be commits, comments, or reviews.

  1. Notifications - The notifications widget displays real-time notifications about quality and delivery risk events. Each notification will include the type of the notification, the relevant entity (including link to the actual GIT entity), The date the notification was added and the following actions:
  • What Should I do? - Opens a help article with specific available action items for the notification type.
  • View all - takes the user to the "Activity" page and shows all the entities that have the same risk category as the notification.
  • Pin - Pins the notification to the top of the list to make it visible
  • Dismiss - Removes the notification from the list and moves it to dismissed notifications.

  1. Teams Dropdown - Allows the user to move between different teams dashboards
  2. Iteration time picker - Allows the user to change the iteration context of the dashboard

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 include more metric summaries and metric trends as well as information about the ended iteration.

  1. Team Cycle Time - Same
  2. Team Work breakdown - Same
  3. Team Members - In team members view in retrospect we are showing metrics related to the relevant iteration. Metrics including Done tasks, Reviews Activity days, and Carryover.
  1. Review Depth - Shows the average comments per review during the relevant iteration. This metric can also be viewed in longer prism showing the trends for the last five iterations.

  1. Deployment Frequency - Shows the average deployments per day for the relevant iteration. This metric can also be viewed in longer prism showing the trends for the last five iterations.

How did we do?

Powered by HelpDocs (opens in a new tab)