Player card: Track individual progress

Tags: Flow

The player card report helps facilitate one-on-ones (1:1s) between a developer and their manager by plotting some of the most-used Flow metrics for a user, all in one graph.  This makes it easy to see all the important data for a manager or developer in one place. The player card shows you recent work as well as long-term data. That way you can identify recent problem spots, historical patterns, and areas for growth.

In this report, view long-term trends for an engineer on key Flow metrics, so you can identify areas for growth and see historical patterns.

Use the player card to identify Flow data points where you'd like to seek additional context Combine data-driven insights with the context your users have about their work to make your 1:1s more productive.

If you're a manager, scrum master, or team lead, the player card report helps you:

  1. Understand an individual's strengths in relation to their teams.
  2. Identify areas of improvement for your engineers.
  3. Plan how you can support the individuals on your team to do their best work.

If you're an engineer, this report helps you:

  1. Understand how your work relates to others on your team.
  2. Have a data-driven conversation with your manager about where you're excelling and what your blockers might be.
  3. Track your progress over time.

What data does the player card show?

There are five key sections of data on a player card report: Code fundamentals, Submit fundamentals, Review fundamentals, activity, and pull requests.

Each of these sections highlights different metrics and ways to look at an engineer's work. Between all these sections, the player card tracks many of the most essential Flow metrics. Check out a full overview of Flow metrics and how they're calculated.

Player card fundamentals

The fundamentals sections show a user's metrics. These sections show a user's metrics in relation to their team by displaying them broken down by quartile. Hover over the metrics on the left to see a chart of the data.

There are currently sections for Code fundamentals, Submit fundamentals, and Review fundamentals. Each of these sections features metrics from their respective fundamentals reports.

The Code fundamentals section features metrics like:

  • Coding days
  • Commits per day
  • Impact 
  • Efficiency

The Submit fundamentals section includes metrics like:

  • Responsiveness
  • Percentage of comments addressed
  • Receptiveness percentage
  • Unreviewed pull request percentage

The Review fundamentals section includes metrics like:

  • Reaction time
  • Involvement percentage
  • Influence percentage
  • Code coverage percentage

Player card Work Log view

The Work Log view in the activity section helps you spot patterns and trends within your users' activity. Choose what type of activity you want to appear by using the Show filter to select which commit types, PR activity, PR comments, or Ticket activity you'd like to see.

Use the Weekends toggle to choose whether the chart displays activity from weekends. You can look at activity from prior weeks by clicking the back arrow on the left.

Hover over an icon to view detailed information about that activity. When you click on the icon, a menu will appear. This menu provides the ID number and additional functionality, like accessing your git host.

Player card pull requests

The pull request (PR) section shows the PRs open during the time frame you're looking at. To narrow down which PRs you see, chose a Sort by option, like Recently opened, Biggest, and Least activity. Then chose which PR status to include. You can choose from All, Opened, Merged, or Closed. Using these filters means you can see exactly which pull requests you're interested in.

Hover over a pull request to view more information about it, such as recently committed code or comments. Click on a pull request to see the pull request's number and a link to view the pull request itself.

How do I choose which information the player card shows?

To customize the information in the player card, use the provided filters: Repo, Date Range, and Targets.

To view activity in a particular repo or set of repos, click Repo and select the repo(s) you're interested in. Use the search feature to select repos based on their name, or select from a group of tagged repos.

Use the player card to see a developer's progress over time. Click Date range to only see data for a specific period of time.

On the Date range tab, select form a trailing 14 day period, year to date, trailing 90 day, or other provided date ranges. You can also set up a custom date range using the provided calendar.

Use the Sprints Tab to show activity during a specific sprint. Learn more about setting up custom date ranges, calendars, and sprints.

Choose whether or not to view the custom targets that have been set for the fundamentals sections by clicking on or off next to Targets.

Tip: You know targets are on if you see dotted lines on the charts in the fundamentals sections.

Settings for Repos, Date ranges, and Targets do not change if you switch which user you're looking at.

How do I find a specific user and filter their data?

To find a user's player card, click on the name of the current user, and scroll through or type a new one in the search bar that appears. You can also find your user by cross-linking them from another report.

Once you've chosen your user, use the compared to field to select which team you want to compare your user to. Then, choose whether or not to include nested teams in the calculations by clicking Included or Excluded.

Note: The player card does not compare a user to the whole organization. It's intended to be used to talk about how a user is performing in relation to their team. If you'd like to understand how a user relates to all engineers in the organization, create a team that contains all of those engineers.

back to top


If you need help, please email support@pluralsight.com for 24/7 assistance.