Project timeline: Compare work output against code focus for a release cycle

The project timeline report provides overviews of different work types for each engineer. These overviews allow team leads, managers, and executives to compare work types and see where engineers are contributing. 

Use project timeline to:

  1. Visualize your teams’ work trends with data on multiple levels

  2. Gain insights into the engineering teams’ volume and focus of work

  3. Compare code and commit volume with Impact and compare it with Code Focus

How do I use Project timelines?

Executives may want a 90-day view to get a sense of longer term trends for their organization. Managers can use project timelines to view sprint-over-sprint data. 

Executives and managers can:

  • Analyze productivity

  • Ensure their team is on track

  • Use this data to communicate with stakeholders

  • View sprint-over-sprint data 

  • Spot roadblocks and debug development lifecycles

  • See when their team is working on a big release, older areas of the code base, or writing new code

  • Demonstrate how their team's work is disrupted by late-stage changes to a spec from a product manager or other stakeholder

View work volume in project timelines

The first graph in project timeline shows you the aggregate work volume for your team. Use the filters to modify the data in the work volume graph.

  1. Use the filters at the top of the report to select which users, teams, repos, and dates are captured in the work volume graph.

  2. Use the work volume filter to select which volume type appears in the graph. You can show commit volume, code volume, commits per active day, and total impact.

  3. Select what data type you want to see. You can view trends, moving averages, or daily averages for a period of time. 

  4. Hover over a bar in the bar graph for more details about that data event. 

Add events to the project timeline

You can add events to the project timeline to provide context as you look back through historic data. For example, you may want to look back on hackathons, planning days, or offsites. 

You can also create an event for new hires. This can help a team lead understand ramp-up and explain spikes in code/commit volume.

You can also import or create sprint calendars to provide quick filtering by team or organization. Learn how to create a calendar.

To add an event:

  1. Click Add event.

  2. In the pop-up modal, select the calendar you want to add and click Next.

  1. Enter the event name, date, time, repeating, and event type parameters and click Create

  1. Review the event and click Done or click Add event to add another event.

View work trends

Work trends show the breakout of work focus over time.

  1. Use the work trends filter to define the work trends you wish to see. You can see absolute, relative, and stacked work trends. 

  2. Hover over the data graph to view details on the work trends for a specific point. These details are broken down by work type and color coded accordingly. 

  3. Use the work type key to understand the work type details data.

  4. Use the LoC toggle to view total lines of code by percentage or integer.

Work type break down

At the bottom of this report, you can find the code focus leaderboards. These graphs surface the top individual contributors for four different work types: new work, legacy refactor, helped others, and churn. 

Learn more about Flow metrics and view the work type definitions.

  1. The date range filter allows you to change the date range for the report.

  2. Click on the icon next to an engineer’s name to dig into the engineer’s data.

  3. Total lines of code shows the total lines of code for the date range. 

  4. Hover over the data point to view the exact number of lines of code written by each engineer in the selected date range.

Note: Typically, the leader of New Work is also near the top of Churn. The more experienced devs tend to do the most Legacy Refactor and Help Others.

back to top


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