Understanding Project Delivery Trackers

LinearB’s Project view is a business alignment dashboard that provides visibility into the investment allocation and progress of engineering projects over time. Project Delivery Trackers are defined using your project management platform (Trackers are currently supported for customers who use Jira), and are highly configurable and can be adjusted at any time, allowing you to monitor multiple PM boards, specific epics, tags, and labels, or even specific fields within your PM platform. LinearB will visualize this information differently for Scrum or Kanban projects. 

Tracker View Features 

Dashboard Overview

From the main page of your Projects dashboard, you can see the list of projects in your organization as well as get an at-a-glance update into team allocation, investment breakdown, and planning accuracy.

  • Click on the "Last 3 months" dropdown to edit the length of time the dashboard displays.
  • To dig deeper into an individual project, click on the project itself to open the Expanded View. 

Expanded View 

From the expanded view you can view your project's metrics. A detailed breakdown of the metrics included can be found lower on this page. Edit the date range you would like to view from the main page before clicking into the expanded view. The left side of this view will display overall performance, you can hover over and click into specific iterations or calendar weeks (depending on if you're viewing a Scrum or Kanban board) in order to see specific metrics for these segments.

Scrum View
Kanban View

Note the Delivery metric is a cumulative flow diagram, you can click on different issue statuses to change the display of this diagram. Removing the "done" status will give you a clear view of any growing backlog or workload spikes.

What metrics are included in Project Delivery Trackers?

Active People / People Effort

In the people effort row of the project’s expanded view users will discover four key data points: 

  • Percent of team members invested
    • This percentage is calculated based on the total number of team members who have contributed across all projects in your projects dashboard.
      • It may be advisable to build a "master project" including all of your active boards. This will give the percent of team members metric an accurate count of your full workforce.
  • The average number of team members active per iteration 
  • Most active team members 
    • Click "View all" to see all team members who have worked on this project's issues and the number of iterations in which each member has contributed. You can also see any team members who are excluded.  
  • People effort over time 
    • Click on any week or iteration to the right to see a list of which team members contributed to that specific segment.

Investment Profile

The investment profile view uses data from your project management platform to visualize the investment being made by issue type. Issue types are highly configurable to the PM platform. LinearB will display all of your Jira issue types as a percentage of all active issues.


The Delivery row will be visualized differently depending on whether the project is Scrum or Kanban. 

Scrum projects will use story point or issue count to display Planned, Added, Completed and Not Completed issues. These numbers are tracked over time to show accuracy trends. 

  • Planned issues: Issues created just prior, or within 24 hours of your iteration beginning. (Contact your CSM to customize this window)
  • Added Issues: Issues added to your Jira board over 24 hours after your iteration began.
  • Completed Issues: Issues in "done" status.
  • Carryover: Issues from your previous iteration which have not yet been completed.

Kanban projects often use Issue Counts grouped based on their progress. Instead of Planning Accuracy, Kanban projects use a Cumulative Flow Diagram to display project progress and health over time. 

Planning Accuracy  (Scrum)

Planning accuracy measures the ratio between planned issues or story points and what was in fact delivered from that list. Accuracy < 70% indicates potential over-commit. Accuracy > 95% indicates potential under-commit. Elite teams are usually in the range of 90-95% There a

Velocity (Kanban)

Velocity measures the number of issues or story points your team delivers week over week. Team velocity can help you predict delivery time and capacity.

What Can I Include in Project Delivery Trackers?

Jira Boards

You can include multiple Jira boards in one project. Use additional filters such as epic, labels, or your custom fields to refine and filter your results.


Combining multiple epics from various boards can give insights into how cross-functional projects are progressing.


You can collect issues from multiple boards that use the same label. Track all issues created for specific features, or web apps, and see how much effort and human capacity these issues generate.


Any custom field in Jira can be used to gather issues into your Project. Find out how much work and capacity is being taken up by issues marked as "infrastructure" or "technical debt", for example.

You can learn more about building Projects here: How to Create and Edit LinearB Project Delivery Trackers

How did we do?

Powered by HelpDocs (opens in a new tab)