See your sprint's velocity, forecast, and flow — inside Azure DevOps

Open Azure DevOps. Click "Agile Analytics" in any project's sidebar. See your last 6 sprints' velocity, cycle time, and a Monte Carlo delivery forecast on one screen — in under 60 seconds, with no Azure DevOps PAT, no setup, and nothing leaving Azure DevOps.

Agile Analytics is a sprint reporting tool and agile metrics dashboard that runs entirely inside Azure DevOps — velocity tracking, cycle time analytics, flow metrics, and Monte Carlo delivery forecasting for Scrum and Kanban teams.

See it in action

The Dashboard: cycle time bands, work in progress, flow efficiency, lead time, throughput and a 30-day "How many?" forecast on one screen.

Monte Carlo forecasting: 10,000 simulations on your team's own throughput show how many items you are likely to finish by a date, at 95%, 85%, 70% and 50% confidence.

Aging work in progress: every in-flight item plotted by days in flow against your team's own p50 and p85, then ranked by urgency.

Cycle time: every completed item on a scatterplot with p50, p70, p85 and p95 lines from your own history, plus a histogram view.

What you get

• Monte Carlo forecasting — P50/P85/P95 delivery date estimates from 10,000 simulations on historical throughput.
• Cycle time analytics — interactive scatterplot with P50/P85 percentile lines, plus flow efficiency and a cycle time heat map.
• Aging WIP and blocked items — see what is stuck before it hurts, with WIP limits and Teams/Slack alerts.
• Sprint burndown, velocity and sprint report — Dashboard KPIs, Sprint Summary, Sprint Capacity and Next Sprint Planning.
• Scrum and Kanban — sprint-based and flow-based views side by side, including Cumulative Flow and Flow Metrics.
• DORA metrics — deployment frequency, lead time for changes, change failure rate, and time to restore, computed from your work items and pipelines.
• Azure DevOps dashboard widgets — companion tiles in the widget catalog under the "Agile Analytics" category.
• Exec Report — a stakeholder-ready delivery-health summary you can print to PDF, or schedule as an email digest.
• 30+ analytics views in a single project hub, with full dark mode.

Questions it answers

Azure DevOps has powerful raw data but no built-in answers for the questions that matter in sprint planning and retros:

• "When will we be done?" — Monte Carlo simulation on your actual throughput history.
• "What should we commit to next sprint?" — Next Sprint Planning combines capacity, Monte Carlo on the team's last 6 sprints, cycle time per bucket, and historical commitment reliability into a single recommendation.
• "Why is this sprint struggling?" — commitment reliability, scope churn, and carryover rates in one view.
• "How long does work actually take?" — cycle time scatterplot with P50/P85 percentile lines.
• "Are we flowing or are we stuck?" — flow efficiency, lead time, and WIP trends over rolling windows.
• "Which team needs attention?" — a cross-team health grid with configurable goals and coaching prompts.

Who it is for

• Scrum Masters — live sprint health, commitment reliability, scope churn, and sprint capacity planning.
• Engineering managers — team benchmarks, cycle time trends, flow efficiency, DORA metrics, and investment allocation.
• Agile coaches — configurable health thresholds, prioritised action items, and a retro snapshot you can copy or export in one click.
• Product owners — Epic and Feature completion with child story rollups, and Monte Carlo forecast dates.

Why teams choose it: no infrastructure to run (no Azure Function, no database, no service connection), WIP alerts that reach you through a Teams or Slack webhook, role-based access control with Azure DevOps directory search, and retro-ready sprint summaries in one click.

★★★★★ "The graphs and charts are easy to read and understand and can be shown to any company member without having to give any further explanation. I would recommend for any team size."

"Even for a small team (we have 5 devs and a Scrum Master) this gives us quick and easy access to progress and planning. There is a great support team who actively engage with us and respond very quickly to our feedback, suggestions and ideas." — Mark Pickering, Azure DevOps Marketplace review

Your work-item data never leaves your Azure DevOps tenant

Every analytics view runs in your browser, against the Azure DevOps REST API, using your existing ADO session. Sprint contents, work-item titles, PRs, code, comments, attachments, customer PII — none of it is sent to a Baytek server.

Agile Analytics installs as an Azure DevOps Marketplace extension — it lives in your tenant, your admin controls it, and your security team can audit it through the Marketplace publisher record.

What Baytek does receive: an org ID, the extension version, and operational event names (e.g. "sprint view opened", "error observed") — no titles, no content, no PII. Used to fix bugs and bill seats. Full detail in our Privacy Policy.

Four read-only ADO scopes. vso.project, vso.work, vso.graph, vso.build. No vso.code. No vso.analytics. No write scopes. The extension cannot modify your work items.

What stays in your tenant: Azure DevOps work item content and any AI adoption credentials you enter. Baytek never sees any of this.

What Baytek's backend receives: licence records (organisation name, plan, expiry, activation tokens); a lightweight install/heartbeat ping (organisation name, extension version, event type, timestamp); anonymous usage events (view navigation, configuration completion, trial-day milestones, and a pseudonymous per-user ID used to count active users and enforce seat limits; opt out at Configuration → Privacy); and, on Team/Business plans, a mirror of your Access Control list (person + role) so seat limits can be enforced. Plus, later in a trial, the signed-in admin's ADO email address, captured from your existing session to send trial milestone reminders — shown in-product with a short window to undo it, and every reminder carries a one-click unsubscribe link. If you schedule an Exec Report or opt into Industry Benchmarks, that feature's own project/team/sprint or aggregate-metric data reaches Baytek too.

Optional integrations: when you connect GitHub Copilot for AI Metrics or set up webhook notifications, requests go from your browser directly to that source (api.github.com for GitHub Copilot) or webhook URL (Microsoft Teams / Slack) — never via Baytek.

Accessibility: WCAG 2.1 AA achieved, checked by an axe-core regression suite in CI on every release.

What's New in Version 6.58

v6.58.0 — Security hardening and a clearer privacy page (October 2026)

A security release. Pipelines the extension generates for you (WIP monitor, delivery digest, report digest, sprint alerts) now carry your team, project and state names in an encoded form, so no name can ever be read as a command. Configuration export no longer includes Teams or Slack webhook addresses, and the GitHub Copilot setup now recommends a read-only token. The extension also confirms which Azure DevOps organization it is running in, once per session, and Data & Privacy explains exactly how. Your dashboards, settings and data are unchanged.

What's New in Version 6.57

v6.57.2 — Flow efficiency counts every state the same way on every view (October 2026)

Flow Metrics and Delivery Signals now treat a state that is not in your Workflow Mapping the way the Flow Efficiency view and the Dashboard already did: a state that sounds like active work counts as active, and any other unmapped state counts as waiting. Before, those days were added to the step before, which could make flow efficiency read 100%. Dashboard tiles show "No data" in grey instead of red when a team has no sprints yet, and the smallest Team Health tile no longer shows a scrollbar.

v6.57.0 — Every view now shares one header, one filter toolbar and one empty state, with larger small text and a faster first load (October 2026)

Every view starts with the same header: the title, a one-line description, and a single help "?" where one exists. Filters sit in one strip directly under it, with the actions (Run, Refresh, Snapshot, Export) on the right. Views that had no title now have one. Labels, captions and pills that were 9 to 11px are now at least 12px, buttons and pills are at least 24px tall, and titles, section headings and card labels follow one scale. When a view has nothing to show, it says so in one line with one action instead of zeros or a red verdict; Flow Metrics, Delivery Signals and the Retro Snapshot show a dash for reliability and carryover when nothing was committed. Chart labels no longer overlap, a suspicious flow efficiency is amber with a caution pill, and sample cards on the AI views carry a SAMPLE stamp with placeholder names.

The hub's first render downloads about 120 KB less, and a view loading for the first time shows an outline of the page instead of "Loading…". Multi-Team Aging has one scope picker (All, Active, Selected) with the other options under "Advanced" and a "?" that explains the Risk score; your saved scope is unchanged. Monte Carlo shows one card when all four confidence levels land on the same date. On a narrow window the sidebar collapses by itself and comes back when the window is wider. Customize shows "Saved ✓" after a change. In Configuration, each form sits in its own card with its Save button, leaving a tab with unsaved edits asks first, and Workflow Mapping shows one project at a time with a single "How mapping works" note.

Getting started in under 2 minutes

1. Install the extension into your Azure DevOps Services organisation from this listing.
2. Open any project and find Agile Analytics in the left navigation bar under your project name. If you don't see it yet, refresh the page once. It appears in every project automatically.
3. Review Workflow Mapping under Tools → Configuration to check the auto-discovered states, so cycle time and flow metrics are accurate for your process.

Requirements: Azure DevOps Services (cloud), Project Contributor access or higher, and a modern browser. Azure DevOps Server (on-premises) is not supported in this version.

Pricing. A 30-day free trial activates automatically on install — no credit card. Annual per-seat plans: Team — $300/year (2 seats), Business — $1,200/year (6 seats), Premium — $2,000/year (unlimited seats). Each licence covers one Azure DevOps organisation, and every plan includes every feature. See pricing.

Learn more

Full documentation, install guide and support live at ado-analytics.baytekdev.com.

Getting Started Guide  |  Support & Feature Requests  |  Privacy Policy  |  Terms of Service