What do the different quadrants mean in the Snapshot report?

Tags: Flow

The Snapshot report highlights work patterns of individual users, relative to the team. 

What is important in this report is not an engineer's position at any specific moment, but how their position changes over time. (We recommend 2 week time-spans). Developers who make contributions one week might be contributing in other ways the following week.

The chart intelligently plots an engineer's contributions across 2 axes: 

  • Impact (severity of edits to the codebase, as compared to repository history)

  • Churn (code which was thrown away shortly after being written)


The bottom two quadrants usually are typical for part-time engineers, team leads, managers, QA, etc. If you have full time developer fall in the bottom two quadrants—especially the bottom-left ‘could be stuck’ quadrant—they may need some help.

Exploring (a.k.a. discovery)

Developers in this quadrant might be working with a new language or experimenting, a new type of feature, or trying out many implementation paths. Occasionally engineers in this quadrant haven't been provided with clear specs or requirements, which is why they have high churn.

Prolific

Developers in this quadrant are making exceptional contributions. So long as the developer has the correct requirements (i.e. building the right thing), interrupting them might be costly. They are building impactful code that doesn't churn.

Could be stuck

If an engineer is in this quadrant they might need some help on a feature. It might be worth checking in, especially if you see them in this quadrant week over week. You don't want full time engineers to be here for very long, so you can use this report to check in and help before it's too late. Sometimes Q/A and Product Managers appear in this quadrant. If you'd like to exclude these irregular Users here's how to hide someone from appearing in the reports. 

Perfectionism

This is a quadrant you might expect managers, team leads, and other senior roles who are familiar with the codebase. They tend to have lower throughput because they are helping others or leading a team. A full time engineer wouldn't typically want to hang out in this quadrant since they are not making a huge impact to the codebase. However most of the work checked in is sticking around.

For more info on how the developer feedback works, check out how does the feedback work in the Snapshot report.

back to top


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