Workflow mapping

Almost every figure Agile Gauge shows depends on knowing which of your team's Azure DevOps states mean "not started yet," which mean "actively being worked," and which mean "done." Workflow mapping, in Configuration, is where that's set.

The six stage categories

Every Azure DevOps state your team uses is mapped into one of six stages, or explicitly marked as not applicable:

• New
• Queued
• In Progress
• Test
• Review
• Done

Marking a state N/A is a deliberate, first-class choice for a state your team doesn't actually use for tracked work — it does not create an "unmapped" warning anywhere.

How mapping gets set

On first use

Agile Gauge makes its own best guess automatically, recognising the states from Azure DevOps' built-in process templates (Agile, Scrum, CMMI, Basic). You don't have to configure anything before the views show numbers.

Provenance is always shown

Configuration tells you plainly whether the mapping shown is one your organization actually saved, or still just Agile Gauge's own inferred guess that nobody has confirmed yet. If Agile Gauge couldn't even read your current settings, it says so and falls back to its defaults rather than letting you save over a mapping it never actually saw.

What happens if mapping is incomplete

A state that exists on your work items but isn't covered by the mapping (and wasn't marked N/A) causes those items to be counted as not started wherever "in progress" or "done" matters — which understates how much is actually finished, rather than simply leaving a number blank.

Which views depend on it

Every view that measures timing or progress reads from the same workflow mapping: Cycle Time, Flow Metrics, WIP Monitor, Aging & Blocked, Delivery Signals, Sprint Summary, Flow Health, and Retro Snapshot. Getting this right once, up front, is the single highest-value setup step.