Nave for Azure DevOps

Turn your Azure DevOps data into evidence about delivery

Nave connects to Azure DevOps and turns your existing work history into flow analytics, delivery forecasts and dashboards for teams and leadership.

Start Free with Azure DevOps

14 days, no credit card.

Cumulative Flow Diagram in Nave for Payments Mobile, June 30 to September 30, 2026, with one band per workflow stage and dotted trend lines showing arrivals at 0.42 items per day and throughput at 0.46 items per day.

Azure DevOps delivery analytics

What can you learn from your Azure DevOps data?

  • Where is work slowing down?

    See cycle time by workflow stage, including waiting and blocked time, to find where work is being held up.

  • Is delivery becoming more predictable?

    Track cycle time, throughput, work in progress, flow efficiency and variability over time.

  • What is aging now?

    See work in progress against your team's own delivery percentiles and identify items that need attention.

  • What can we realistically deliver?

    Use Monte Carlo forecasting based on actual Azure DevOps throughput, without story points or estimates.

How it works

From Azure DevOps board to delivery evidence

Connect a board, map its columns to your workflow and use the resulting evidence to decide where to act next.

  1. 1

    Azure DevOps board

    Choose the board and area path whose delivery flow you want to understand.

  2. 2

    Nave dashboard

    Map board columns to workflow stages and mark the stages where work waits.

  3. 3

    Delivery evidence

    Nave computes flow metrics from the board's existing work item history.

  4. 4

    Decision

    Use the evidence to address constraints, forecast delivery and track improvement.

Diagram

Azure DevOps board columns

  1. To do
  2. In Development
  3. Code Review
  4. Ready for SITWaiting stage
  5. SIT
  6. UAT
  7. Awaiting ReleaseWaiting stage
  8. Done

Nave workflow stages

  1. Not started
  2. In progress
  3. Done
Map Azure DevOps columns to workflow stages, marking waits so Nave can separate active time from waiting time.

Start with the history you already have.

Connect your Azure DevOps board and Nave turns its existing delivery history into flow metrics, so you don't have to wait weeks to start learning from your data.

Keep managing work in Azure DevOps. Use Nave to understand how that work flows.

Azure DevOps

Manage work items, boards, area paths and team workflows where your teams already work. Azure DevOps remains where the work is managed.

Nave

Use Azure DevOps delivery history to investigate flow, predictability, aging and bottlenecks, forecast delivery and track improvement without changing how teams manage work.

Find constraints

Find where delivery slows down

For Payments Mobile from June 30 to September 30, 2026, the Process Metrics table shows when 50%, 85% and 95% of work items left each stage. Across the whole process, those percentiles were 22, 28 and 31 days. At the 85th percentile, In Development took up to 10 days, Ready for SIT took 12 and Awaiting Release took 8. Ready for SIT and Awaiting Release are waiting stages.

Explore Cycle Time Breakdown 
Process Metrics table in Nave for Payments Mobile, June 30 to September 30, 2026, showing days within which 50%, 85%, and 95% of items left each stage: Process, 22, 28, 31; In Development, 7, 10, 12; Code Review, 2, 4, 4; Ready for SIT, 3, 12, 14; SIT, 3, 6, 6; UAT, 2, 4, 5; Awaiting Release, 4, 8, 8.
Process Metrics for Payments Mobile, June 30 to September 30, 2026.

Current work

Know what needs attention

The AI Investigator reads your computed flow metrics and points you to the stages and work items behind a problem. Here, it identifies two items stalling in SIT, an inconsistent Ready for SIT handoff, and another item approaching its normal Awaiting Release threshold.

The numbers are computed, not generated. The AI only reads them, so swap the model and the numbers don't change.

Explore AI Investigator 
Nave AI Investigator findings for Payments Mobile: urgent, “1111” and “1113” are stalling in SIT well past the 85th percentile, with near-identical timing suggesting a shared dependency; monitor, Ready for SIT spans p50 at 2 days to p85 at 11 days, and “1112” is approaching the Awaiting Release 85th percentile with no visible release date; celebrate, current WIP is 6, below the period average of 8.89, with steady throughput.
AI Investigator findings for Payments Mobile during the same period.

Plan realistically

Forecast what you can realistically deliver

Monte Carlo runs 10,000 trials using Payments Mobile's daily throughput from June 30 to September 30, 2026. For 50 items starting on September 30, it forecasts completion by January 20, 2027 at 50% confidence, February 23 at 85% confidence and March 17 at 95% confidence. The forecast uses no story points or estimates.

Monte Carlo: Delivery Date in Nave for Payments Mobile, showing 10,000 simulated completion dates for 50 items starting September 30, 2026, based on throughput from June 30 to September 30, 2026. Confidence lines mark 50% at January 20, 2027, 85% at February 23, and 95% at March 17.
Monte Carlo delivery date forecast using Payments Mobile's daily throughput.

Explore Continuous Forecasting 

Scale the view

Show leadership whether performance is improving

Roll Azure DevOps team dashboards into Services and Portfolios, including Services that contain Azure DevOps teams alongside Jira teams. Executive Dashboards compare performance over time across teams and Services.

In the Retail Banking portfolio, Cycle Time Trends show Digital Payments moving from 20 days in July to 25 in August and 16 in September. Mobile Banking holds at 20 days in July and August, then falls to 16 in September. Each Service contains teams working in Azure DevOps and Jira, and Payments Mobile belongs to Digital Payments.

Diagram

Portfolios

Retail Banking

Services

Digital Payments
Mobile Banking

Team dashboards

  • Payments APIJira
  • Payments WebJira
  • Payments MobileAzure DevOps
  • Mobile AppAzure DevOps
  • Mobile PlatformJira
Teams using Azure DevOps and Jira roll up into two Services within one Retail Banking portfolio.
Cycle Time Trends in Nave for the Retail Banking portfolio by Service, July to September 2026. Digital Payments moves from 20 days in July to 25 in August and 16 in September; Mobile Banking stays at 20 days through August, then falls to 16 in September.
Cycle Time Trends for the Retail Banking portfolio by Service, July to September 2026.

Services & Portfolios Executive Dashboards 

Analytics trusted by 7,000+ delivery teams worldwide

Explore Azure DevOps analytics in Nave

Connect Azure DevOps

Choose your Azure DevOps edition and connect

  • Azure DevOps Services

    1. Select Log in with Microsoft Entra and sign in on Microsoft’s page.
    2. An administrator grants one-time consent for Nave across the organization.
    3. Team members then log in through Microsoft Entra.

    Microsoft’s consent screen lists requested permissions before approval. Nave proves its identity with a certificate-signed assertion, not a shared secret.

    Connect Azure DevOps 

  • Azure DevOps Server

    If your Azure DevOps Server is not exposed publicly, export your data to a .json file and upload it to Nave. Contact Nave to set up the connection together.

    Contact Nave 

Each connected Azure DevOps board counts as one subscription board; the 14-day trial includes every feature, with no credit card. See pricing 

Reading and handling data from Azure DevOps

What comes across

Nave syncs work items from the board columns and area path mapped to a dashboard. A selected root area path includes its child paths. Nave keeps the work item ID, title, work item type, created date, due date, area path, link back to the item and every column change with its date. It brings in only the custom fields you select. Assignee names are stored only when the Assignees field is turned on, and that field is off by default. Descriptions, comments and attachments are not stored or shown, and attachment files are never downloaded.

Columns become stages

Each dashboard maps one Azure DevOps board. Map its columns to not started, in progress and done, then mark waiting stages so flow efficiency separates active time from waiting time. Doing and Done sub-columns can be mapped separately. Teams using the CMMI or Scrum process template can use the built-in Blocked field; any team can use a boolean custom field.

Filters

Filter dashboards by work item type, tags, area paths and the custom fields you select. The Assignees filter is optional.

Your existing history

A new dashboard loads the last three months by default. Choose an earlier date range and Nave loads work items changed since that date, each with its full history.

What Nave never does

Nave never creates, changes or deletes anything in your Azure DevOps organization. It only reads. Nave does not add webhooks or service hooks. It checks for changes every 30 minutes on Nave's servers, whether or not anyone has Nave open.

Sign-in, access and assignee data

Nave never has access to your Microsoft password because you sign in on Microsoft's page. A person sees a dashboard only if they are invited, log in through Microsoft Entra and have access to that data in Azure DevOps. Assignee names are stored only when the Assignees field is turned on. It is off by default.

Security and compliance

  • SOC 2 Type II
  • GDPR
  • Microsoft Entra sign-in
  • Data hosted in the EU

See frequently asked questions 

Connect Azure DevOps and start with your own data

Start a 14-day trial with every feature and no credit card, or book a demo to discuss your Azure DevOps setup.

Connect Azure DevOps Book a Demo