Metrics grade on your definitions (6.44)

1. Grade on your own thresholds

The six Delivery Signals cutoffs are now organisation-configurable from Configuration.

• Six thresholds, set where you configure everything else

  Throughput, carry-over, cycle time, time to start, flow efficiency and blocked items each have their own cutoff, and every one of them is now editable from Configuration. Grade a sprint against what "good" means for your teams, not a fixed number baked into the product.

• Defaults stay exactly as they were until you touch them

  The built-in cutoffs are unchanged, and every organisation keeps seeing the grades it already sees today unless an admin opens Configuration and edits a threshold. Nothing shifts as a side effect of this release shipping.

• One click back to the built-in defaults

  If a custom threshold turns out to be the wrong call, a single reset returns every Delivery Signal to its original cutoff. Trying your own definition is never a one-way decision.

2. Story points where they matter

Investment Allocation and Epic Analytics can now weight by story points instead of item count, when that is how your teams plan.

• Investment Allocation: Count or Story Points, your choice

  A new toggle lets Investment Allocation weight its breakdown by story points instead of item count. Count stays the default, and the view remembers whichever choice each person makes, so switching it for yourself never changes it for a colleague.

• Unestimated work is counted honestly

  When story points weighting is on, an item with no estimate counts as zero, and the view says so plainly rather than quietly rounding it into the total. What you see is what the data actually supports.

• Epic Analytics gets a story-points progress basis

  Epic progress can now be measured by story points completed, alongside the existing item-based view, so a programme with widely different epic sizes can track completion the way its planning already works.

• Both views now explain their own math

  The epic and feature views carry a "how this is calculated" note describing exactly what feeds the number on screen, including that delivery forecasts always count stories regardless of the weighting chosen elsewhere. A grade you can question is a grade you can trust.

3. Grades you can defend

DORA and Monte Carlo now say plainly when a grade or forecast is standing on incomplete ground.

• DORA deployment frequency stops grading too early

  While DORA is still counting every pipeline run as a deployment, it no longer hands out an Elite or High performance band on top of that number. The count stays visible the whole time, and a one-click link takes you straight to choosing which pipelines actually represent a deployment.

• The pipeline picker is honest about where pipelines live

  Choosing deployment pipelines now tells you when a selected pipeline belongs to a different project, instead of leaving that unstated. Selections are always kept on save, in either case.

• Monte Carlo says when its history is thin

  A forecast built on fewer than four sprints of history now says so plainly, so a wide-looking range reads as "not enough data yet" instead of as a confident prediction.

4. Admin quality of life

A handful of changes make day-to-day administration faster and harder to get wrong.

• Bulk-approve pending access requests

  Approve a batch of pending access requests as User in one action, instead of working through them one at a time.

• Every CSV export is in the activity log

  Exporting a CSV from anywhere in the admin views is now recorded in your organisation’s admin activity log, and the log says plainly when an entry could not be recorded rather than leaving a silent gap.

• Concurrent edits to access control are protected

  If two admins edit access control settings at the same time, the second save can no longer silently overwrite the first. A conflict is caught rather than one admin’s change quietly disappearing.

• Locked settings show what your organisation enforces

  A setting your organisation has locked now displays the organisation’s enforced value wherever it appears, rather than a stale personal value that no longer applies. Unlocking it restores each person’s own setting exactly as they left it, untouched by the time it spent locked.

5. A friendlier first run, and small polish everywhere

These apply to everyone using Agile Analytics, whether or not your organisation uses any of the features above.

• A short, skippable tour for new teammates

  Anyone opening Agile Analytics for the first time now gets a four-step tour of the essentials, and can skip it at any point. It works at any window size and in both light and dark theme.

• Leadership report trend lines

  The leadership report now shows a trend line alongside its headline numbers, so a stakeholder can see direction of travel, not just a single snapshot.

• Aging & Blocked links straight to the multi-team view

  Following through from Aging & Blocked now lands directly on the multi-team view it is describing, instead of a stop that requires another click to get there.

• Sprint Summary loads large team lists smoothly

  Opening Sprint Summary on a large team list no longer stalls the view while everything loads at once.

• Export filenames use your local date

  CSV and report exports now stamp their filename with the date as it reads in your own timezone, so a file you save at the end of your day is not dated tomorrow.

• A number of smaller fixes across the extension

  Alongside the above, this release carries a set of smaller corrections found while preparing it, covering wording, layout and edge cases across several views.

6. Getting started

If you plan to set your own Delivery Signals thresholds, start from the built-in defaults and change one at a time, watching how it reclassifies your most recent sprint before moving to the next. A threshold set without checking it against real data first can grade every team against a target nobody discussed.