Skip to main content
Sign in
Deutsch (Deutschland) Español Français Italiano Português

Project Delivery Tracker

Heather Hazell
  • Updated

Project Delivery Tracker (PDT) gives you a high-level, real-time view of how projects are progressing in LinearB. It pulls structure and status directly from your project management boards (Jira) so you can see planning accuracy, delivery breakdown, investment patterns, and people effort for Scrum and Kanban teams.

TL;DR

  • Provides a single view of project health across initiatives.
  • Supports both Scrum and Kanban workflows.
  • Shows Planning Accuracy, Capacity Accuracy, and Velocity.
  • Includes Investment Strategy and People Metrics for each project.
  • Highly configurable: boards, epics, labels, fix versions, and custom fields can all be included.

Before You Begin

  • Required access: Admin or Editor (to configure trackers)
  • Required integrations: Jira (connected under Project Management)
  • Teams & boards: Relevant Jira boards should be connected and in use

Where to Find Project Delivery Trackers

  • Go to the Projects area in LinearB.
  • Select the Delivery / Project Delivery Tracker view.

The Projects dashboard shows a card for each Project Delivery Tracker you’ve configured, including key metrics and high-level project information.

Overview of the PDT Dashboard

Main Dashboard – What You’ll See

The dashboard provides a high-level snapshot of every tracked project:

  • General Information: Project name, methodology (Scrum or Kanban), cadence.
  • Active People: Contributor count and effort over time.
    • A contributor is considered active if they were assigned to an issue moved to Done.
  • Investment Strategy: Work distribution by issue type.
  • Delivery Performance: Indicators aligned to project methodology.
  • Planning Accuracy: Planned vs. completed work for iterations.

Key Metrics in Project Delivery Trackers

Planning Accuracy (Scrum)

Planning Accuracy measures how reliably the team delivers what they planned at the start of an iteration.

  • Definition: Ratio of planned issues or story points that were actually completed.
  • Formula: (Completed Planned Issues ÷ Total Planned Issues) × 100%
  • Signals:
    • < 70% – Indicates potential over-commitment.
    • > 95% – May indicate under-commitment.
Capacity Accuracy (Scrum)

Capacity Accuracy compares how much work (planned + unplanned) the team actually completes in an iteration against what was originally planned.

It helps answer: “Is the team taking on a reasonable amount of work relative to their capacity?”

Throughput (Kanban)

For Kanban projects, Project Delivery Tracker shows Throughput/strong>:

  • Definition: Average number of completed issues (or story points) per week.
  • View: Week-by-week breakdown to spot trends and changes in delivery efficiency.

Expanded Project Delivery Tracker View

What you get when you open a tracker

Clicking into a Project Delivery Tracker opens a detailed view for that project, including:

  • Planning Accuracy scores (Scrum).
  • Velocity trends (Kanban).
  • Delivery breakdown for Scrum or Kanban.
  • Investment Strategy breakdown (by issue type).
  • People Effort and contribution analysis.
  • Iteration/week breakdown – click into a sprint or week for granular detail.
  • Date range controls – adjust the timeframe (e.g., last 3 months).
     

Delivery Breakdown – Scrum

For Scrum projects, the Delivery section shows how work was planned and completed:

  • Planned Issues / Story Points – Defined at the start of the sprint.
    • Hover segments to see completed vs. incomplete planned work.
  • Added Issues / Story Points – Added before or within 24 hours after the start of the sprint.
    • Hover segments to see completed vs. incomplete added work.
  • Average Completed / Added Work – Average completed and added work per iteration.
  • Switchable Views – Toggle between planned work and overall completion.
  • Scrum Accuracy Scores – Planning accuracy per iteration.

Note: The 24 hours grace period applied to planned work is also applied to issues removed. There for any issue removed before the first 24 hours after the start of a sprint will not appear in that sprint.

 

Delivery Breakdown – Kanban

For Kanban projects, the Delivery section uses a Cumulative Flow Diagram:

  • Shows issue or story point distribution across Jira swimlanes.

  • Data is pulled directly from the Jira boards included in the Project Delivery Tracker.

     

Considerations for Data Accuracy

How PDT data is scoped

  • Trackers can span multiple iterations and use a custom date range that may differ from Jira’s default views.
  • A single tracker can pull from multiple Jira boards, epics, and labels.
  • Issue counts in PDT may differ from a single Jira board because you’re aggregating across multiple sources.
  • Unplanned tickets left open and not closed during an iteration are excluded – PDT focuses on completed work.

Investment Profile in PDT

How Investment Profile appears in Project Delivery Tracker

The Investment Profile section in PDT shows a visual breakdown of work by issue type, using data from your project management platform.

  • Displays all Jira issue types found in the boards linked to the tracker.
  • Shows percentage of work per issue category.
  • Can toggle between issue count and story points.
  • Includes an “Investment Over Time” view that shows how issue-type mix changes across iterations.

People Metrics

Active People & People Effort

PDT includes people-focused metrics to show who is actively contributing to project delivery:

  •  FTE - FTE (per engineer, per period) = total allocated days in the period ÷ X, where X = number of calendar days in the selected period.
  • Most Active Team Members – Highlights contributors active in the most iterations/weeks.
  • People Effort Over Time – Trend graph of unique users completing work per iteration/week.
  • People Breakdown – Click into a specific iteration to see individual contributor details.

Contributors working in multiple projects can appear in multiple trackers. When you sum percentages across all projects, totals may exceed 100% due to overlap.

Customizing Project Delivery Trackers

You can build a new Project Delivery Tracker by selecting Add Project

Selecting what to track

Each Project Delivery Tracker can be configured to include Jira data that best represents your project:

  • Jira Boards – Combine multiple boards in a single tracker.
  • Epics – Track cross-functional work spanning several boards.
  • Labels – Group issues across boards using shared labels.
  • Fix Versions – Align project tracking with release versions.
  • Custom Fields – Use Jira fields (e.g., “Infrastructure”, “Tech Debt”) for deeper analysis.
Searching for a tracker

Use the search box to quickly find a specific project:

  1. Type at least two characters from the project name.
  2. Review matching projects and select one to open its details.

Search behavior:

  • Case-insensitive.
  • Matches any part of the project name.
Additional features
  • Drill into a single iteration or week for detailed metrics.
  • Export charts as PNG snapshots for stakeholders by selecting Share on the top right -> Export to PNG
  • Admins can create, edit, and delete Project Delivery Trackers as reporting needs change.
  • Switch between views focused on planned work vs. completion.

Troubleshooting

Counts don’t match Jira boards
  • Check whether the Project Delivery Tracker includes multiple boards, epics, labels, or custom fields.
  • Confirm your date range – PDT may be aggregating a different period than the Jira board view.
People metrics look off
  • Remember that contributors can appear in multiple trackers if they work across projects.
  • Verify that issues have assignees; if not, the reporter/creator is used as the active contributor.

Related Features

Related articles

Comments

0 comments

Article is closed for comments.