Free tool · runs in your browser
X-ray your delivery in 60 seconds.
Drop in a Jira, Linear or Azure DevOps export. The Delivery X-Ray measures how long work really takes, how predictable you are, where work gets stuck and how much of your capacity goes on bugs, then shows you what to fix first.
Run your Delivery X-Ray
Three steps, about a minute. Want to see it first? Use our sample data.
1Export your work items
Include every open item plus everything finished in the last six months. Titles and descriptions are ignored.
- Open Filters → Search (advanced/JQL mode) and paste this, with your project key:
project = ABC AND (statusCategory != Done OR resolved >= -180d) ORDER BY created DESC - Choose Export → Export CSV (all fields).
- Jira exports up to 1,000 rows at a time. For a big project, run it per team or shorten to
-90d.
- Open Settings → Import / Export and choose Export CSV. Linear emails you a download link.
- Or, from any team view, filter to the issues you want and use the view's export option.
- Linear exports include a Started date, so you'll get true cycle time.
- In Boards → Queries, create a flat query for your area path: State <> Closed OR Closed Date ≥ @Today - 180.
- Under Column options, add Work Item Type, State, Created Date, Activated Date, Closed Date, Assigned To, Iteration Path.
- Run it, then use ⋯ → Export to CSV.
Any CSV works if each row is one work item and it has a created date and a done date (blank when not done). A status, type, start date, assignee and sprint column each unlock more metrics. You can match the columns in step 3.
2Drop the file here
Step 3: check how we read your columns · auto-detected
arham-tech.com/delivery-x-ray · info@arham-tech.com
✓Your Delivery X-Ray
Your three biggest issues
Fix these first
Work started vs work finished, week by week
Last 12 weeks
Show the numbers
What we'd recommend
Want a practitioner to check these numbers?
Usman will review your X-Ray with you on a free 30-minute call and tell you what he'd fix first, even if you don't hire us.
How the score is calculated
- Every number comes straight from your export. The "as of" date is the latest date in your file, so an older export still reads correctly.
- Flow metrics use items finished in the last 12 weeks. Items closed as won't do, duplicate, cancelled or removed are left out.
- Each metric scores 10 (healthy), 7 (watch), 4 (problem) or 1 (critical) against practitioner rules of thumb for software teams. Your score is the average of the metrics your export supports, out of 100.
- The thresholds are our judgement, not an industry standard. Teams doing large, regulated or hardware work will naturally score lower on time-based metrics.
What the X-Ray measures
Nine signals that predict whether releases land on time. Each one comes from data your tool already records.
Time to deliver
How many days a typical item takes from start (or creation) to done, and how long the slow ones take.
Predictability
How far your slow items are from your typical item, and how much your weekly output swings.
Work in progress
How many things each person is juggling, and how much started work has gone stale.
Sprint carry-over
How much finished work had to be dragged through more than one sprint.
Bug load
How much of your team's output goes on fixing defects rather than building.
Backlog and intake
How old your backlog is, and whether new work arrives faster than you finish it.
Frequently asked questions
Is my data uploaded anywhere?
No. The X-Ray reads your CSV inside your browser. The file is never sent to Arham Tech or anyone else. If you unlock the full report, we receive only your email, company, role and the summary scores shown on screen.
Which tools does it work with?
Jira (Cloud and Data Center), Linear and Azure DevOps exports are recognised automatically. Any other CSV with a created date and a done date works too: you match the columns yourself in step 3.
Why are some metrics marked "not in this export"?
Some tools don't export everything. Jira's CSV has no start date, so we measure time from creation instead of cycle time, and Linear and Azure DevOps only record one sprint per item, so carry-over can't be measured. Your score only averages the metrics your file supports.
How accurate is the score?
The numbers are calculated exactly from your export. The thresholds that turn them into a score are practitioner rules of thumb, not an industry standard, so treat the score as a starting point for a conversation rather than a verdict. That's what the free review call is for.
What happens after I unlock the report?
You see the full report straight away. Usman may send you one follow-up email. If you'd like to talk it through, request a free 30-minute review from the report.
The X-Ray shows where it hurts. We fix it in four weeks.
Our Digital Delivery Tune-Up turns these numbers into a redesigned process your teams keep. Fixed scope, fixed fee.