...

Team Productivity
Overview of these metrics:

1. Epic Focus

Determine which efforts are getting the most focus from the engineering team.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. Issues by Activity State

   1. Description:

   2. How is it calculated?

   3. What questions can I answer from this data?

   4. What should I take away from this data?

   Issue Bouncebacks

Looking at Issue Activity by Card Type can show you how your team is managing each aspect of the development process. You can see where your team is spending the most time, and there they might need help, training, or additional resources.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. Issue Creations Over Time

   1. Description:

   2. How is it calculated?

   3. What questions can I answer from this data?

   4. What should I take away from this data?

   Issues Created vs Completed

   Bouncebacks

See when an issue is returned to a previous state which usually indicates a quality issue such as a failure or a bug that needs rework.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. Issues Worked On

   1. Description:

   2. How is it calculated?

   3. What questions can I answer from this data?

   4. What should I take away from this data

1. Items Worked On

   Issue Creations Over Time

The rate of new issues created can show you trends in the amount of work coming in and indicate if you are planning too much work for your dev team.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. Velocity

   1. Description:

   2. How is it calculated?

   3. What questions can I answer from this data?

   4. What should I take away from this data?

Work Patterns
Overview of these metrics:

1. Active Contributors

   Issues Created vs Completed

This will show you the rate of completing issues compared to how many issues are being created. This can be an indicator of potential quality or capacity challenges due to a growing backlof.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. Active HoursIssues Worked On

Understand team bandwidth by seeing the number of issues they are working on.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

   All Team Coding Activity

1. Items Worked On

Understand productivity trends and capacity by viewing the number of items an individual has worked on.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

   Overtime Hours Worked

2. Description:

How is

1. Velocity

Understand how long work takes to get completed to improve planning and understand trends in performance.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

Work Patterns
Overview of these metrics:

1. Active Contributors

The number of team members contributing to the codebase over time.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. Active Hours

Overtime is a major contributor to employee burnout. Tracking how many hours team members are working can ensure they are engaged but not getting burnt out so you can reduce flight risk.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. All Team Coding Activity

Understanding when your team is working is key in planning new projects or understanding bandwidth. If your team is working most weekends it could really hurt morale and lead to burnout.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. Overtime Hours Worked

Overtime is a major contributor to employee burnout. Tracking how many hours team members are working can ensure they are engaged but not getting burnt out so you can reduce flight risk.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. PM Activity by Day of WeekActivity by Day of Week

Looking t when your team is working on project management-related tasks can help you understand when people are most productive, how timezones affect your project status, and even if team members are working unhealthy schedules.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

...

Communication
Overview of these metrics:

1. Chat Messages

See if team members are engaged in company communication tools to determine the level of engagement as a signal of satisfaction and collaboration.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

1. Team Sentiment

Look at the sentiment of your team in all unstructured communication can help you understand if an employee is becoming unhappy or disengaged.

1. Description:

   1. How is it calculated?

   2. What questions can I answer from this data?

   3. What should I take away from this data?

...