Getting started

What happens after Agile Gauge is installed: where to find it, who can open it, and how the trial and licensing are meant to work.

Install and open the hub

Agile Gauge installs as a single tab inside Azure Boards. It contributes one hub named "Agile Gauge" to the Boards work hub group, so it appears alongside Boards, Backlogs, Sprints and Queries: not as a separate top-level section in the Azure DevOps sidebar. Open it from any project: Boards → Agile Gauge.

The first screen you land on is the Dashboard: a snapshot of the current team's sprint health, with links out to every other view.

Who can see it

Anyone who can already open Azure Boards for a project can open the Agile Gauge tab: there is no separate Azure DevOps permission for the extension itself. Agile Gauge only ever reads; it requests no write permissions and cannot create, update or delete anything in your Azure DevOps organization. See Privacy & permissions for the exact scopes it requests and why.

The 14-day trial

Every organization gets a 14-day trial automatically, with every view unlocked, and no card required. The trial is per organization, not per person: everyone in the org can use every view during the trial window.

Activation and seats

Who can activate

An Azure DevOps organization admin, not a project admin: a license covers the whole organization, so activation is scoped the same way.

How activation works

Buy a subscription on the pricing page; the license key arrives by email. The organization admin pastes it into Configuration → License. Once activated, it applies to the whole organization. The License tab then shows the seats purchased and in use, and when the current period ends.

Assigning seats

After activation, an admin assigns the purchased seats to named people, by name or email, under Configuration → Access. Seats only matter once the trial is over: during the trial everyone can use Agile Gauge. Anyone without a seat sees a plain "no seat assigned, ask your admin" message rather than a broken or degraded product.

Languages

Agile Gauge ships in five languages: English, Spanish, Portuguese, Italian and German. It detects your language automatically when you first open it: first from Azure DevOps' own reported locale, then from your browser's language, falling back to English if neither is one of the five (for example, a browser set to French falls back to English, and a browser set to Swiss Italian falls back to plain Italian). The hub's top bar also has a Language dropdown so you can change it yourself at any time, independently of that detected default: each language is listed by its own name (Español, Português, Italiano, Deutsch), not a translated one, so it stays readable to someone who has landed in a language they don't read.

Theme

The same top bar has a Theme dropdown with three choices: Match Azure DevOps (the default: it reads the light or dark theme your Azure DevOps organization is using and follows it, so there's nothing to set up), Light, and Dark. Choosing Light or Dark overrides the default with your own preference, remembered separately from the organization's theme and from anyone else's choice.

Workflow mapping: do this before judging the numbers

Most of what Agile Gauge measures, cycle time, flow metrics, WIP, aging, delivery signals, depends on knowing which of your Azure DevOps states count as "in progress" and which count as "done." Agile Gauge makes its best guess automatically from your process template, but it's worth checking. See Workflow mapping.