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 PAT, no setup, no data export.

What you'll see in your first minute. After install, Agile Analytics adds a sidebar entry to every project in your organisation. Click it once. The hub reads your existing sprint history through your ADO session and renders the Dashboard view above — velocity, burndown, WIP, and delivery grade — for the active sprint. No configuration screen first. If you've never set up a workflow mapping, the hub auto-discovers your column states; you can adjust later.

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.

This is structurally different from SaaS analytics platforms (Jellyfish, LinearB, Plandek, Allstacks, Athenian) that require you to grant a PAT or OAuth scope and pipe your ADO data into their warehouse. 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.

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

Where to find it after install

Agile Analytics adds a new entry to the left sidebar of every Azure DevOps project in your organisation — directly under the project name, alongside Boards, Repos, Pipelines. If you've just installed and don't see it yet, refresh the project page once. The extension is organisation-wide, so it shows up in every project automatically — you do not need to install it per project.

Most installers never come back to this listing — they go straight to Azure DevOps. If a teammate installed Agile Analytics for your team and you're trying to find it: open any project in your organisation, then look in the left sidebar for Agile Analytics.

At a glance

• What it is. A sprint-intelligence and flow-analytics hub embedded in Azure DevOps Services. 15+ analytics views and 3 native ADO dashboard widgets, delivered as a single project hub extension.
• Built for. Engineering managers, agile coaches, scrum masters, and product owners running 1–50+ Scrum, Kanban, or SAFe teams in Azure DevOps Services. Useful from a single team to enterprise rollouts.
• Pricing. Per-seat tiers. Team — $25/month (2 seats) · Business — $100/month (6 seats) · Premium — $2,000/year (unlimited seats). Every plan includes every feature. 30-day free trial activates automatically on install — no credit card.
• Security & privacy. All analytics run in your browser against the Azure DevOps REST API using your existing ADO session. Your work-item data never leaves your Azure DevOps tenant. Baytek's backend stores only licence records and lightweight install telemetry — never work-item content.
• Compliance. WCAG 2.1 AA accessibility achieved (verified by an axe-core regression suite in CI on every release). SOC 2 Type 1 evidence collection in progress. GDPR-aligned data handling — see Privacy Policy.
• Permissions. Three read-only Azure DevOps scopes: vso.project, vso.work, vso.graph. No vso.code, no vso.analytics, no write scopes. The extension cannot modify your work items.
• Quality bar. Every release passes 500+ automated tests (vitest unit + Playwright E2E + 5-view accessibility regression baseline + visual regression baseline) before publication. TypeScript strict mode end-to-end.
• Infrastructure required. None. No Azure Function, no database, no service connection, no PAT. Install, map workflow states once, done.
• Where it runs. Azure DevOps Services (cloud). Azure DevOps Server (on-premises) is not supported in this version.
• Publisher. Baytek. Support and feature requests: ado-analytics.baytekdev.com/support

Pricing & Licensing

30-day free trial — no credit card. Paid plans from $25/month after. The Marketplace install gives you the full extension, fully unlocked, for 30 days. To keep using it past day 30, an Azure DevOps organisation admin activates a paid plan below. There is no "free forever" tier; we tell you this up front so day 31 isn't a surprise.

Three plans, every feature included on each:

• Team — $25/month · 2 seats included. Right for a small Scrum team or a pilot rollout.
• Business — $100/month · 6 seats included. Right for a full delivery team running Scrum or Kanban.
• Premium — $2,000/year · unlimited seats. Best for a whole org or multiple teams.

Team and Business are billed monthly; Premium is billed annually.

A seat is one Azure DevOps user who opens Agile Analytics inside your organisation. Seats are counted over the last 30 days of distinct user activity. If your team grows past your plan's allotment, you'll see a soft in-extension notice — no surprise billing.

30-day free trial activates automatically on install — no credit card required. During the trial every user in your org has full access.

Install from the Azure Marketplace and your trial starts automatically. When you are ready to subscribe, visit https://ado-analytics.baytekdev.com/pricing/. After payment, Baytek emails your licence key and an org admin activates it in Settings → License inside the extension.

Not ready to commit? Schedule a 15-min call — procurement question, security review, missing feature, pricing for an unusual team size. No slides.

Support & Feature Requests: Questions, bugs, rollout help, or missing features? Start here: https://ado-analytics.baytekdev.com/support/

The Gap It Fills

Azure DevOps has powerful raw data but no built-in answers for the questions that actually 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, backlog risk scan, and historical commitment reliability into a single recommendation
• "How much can we realistically commit this sprint?" — Sprint Capacity: velocity-adjusted commitment, factoring in each member's days off
• "Why is this sprint struggling?" — Commitment reliability, scope churn, and carryover rates in one view
• "Which team needs attention?" — Cross-team health grid with configurable goals and auto-generated coaching prompts
• "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
• "Are our engineers actually using AI tools?" — Company-wide GitHub Copilot and Microsoft 365 Copilot adoption dashboard

Agile Analytics answers all of these — without leaving Azure DevOps.

Who Is This For

Views at a Glance

Sprint Health

Flow Analytics

Portfolio

Agile Coach

AI Governance

Dashboard Widgets

Three Azure DevOps dashboard widgets — add them to any project dashboard alongside your other ADO widgets:

Tools

How It Compares

This is positioning, not a benchmark — every team's setup is different. The point is that Agile Analytics fills the analytics layer that ADO ships without, with no data-pipeline work and a flat org price.

Security, Privacy & Compliance

Where your work-item data lives. Every analytics view runs in your browser against the Azure DevOps REST API, authenticated by your existing ADO session — the same session ADO Boards uses to render your work-item list. Baytek does not see, request, or store your work-item content, sprint data, AI prompts, or any user identifiers from your tenant.

What Baytek's backend handles.

1. Licensing. When an org admin activates a paid licence, the backend issues a signed activation token. Subsequent validation calls confirm the token is still valid. Stored: organisation name, plan tier, expiry date, activation token. No work-item data.
2. Install telemetry. A lightweight ping on first install and on subsequent loads (organisation name, ADO org id, extension version, event type, timestamp) lets us count active orgs and detect outages or regressions. No work-item data.
3. Anonymous usage telemetry (added in v6.4.0, opt-out at Configuration → Privacy). A small allow-listed set of events — view navigation, configuration completion, trial-day milestones, feature use — recorded against the ADO organisation ID. Each event carries an enum-valued name and a small structured properties payload. Never includes work-item content, user names, project / team / sprint names, AI prompt content, or webhook URLs. The exact event allow-list is documented in the Privacy Policy.
4. Optional trial nurture emails. If a trial admin opts in by entering their email in the trial reminder card, Baytek sends a Day 7 onboarding email, a Day 14 mid-trial check-in, and Day 23 / Day 28 trial-end reminders. Opt-in only.

Sub-processors.

• Stripe — payment processing for licence purchases.
• Firebase App Hosting — the ado-analytics.baytekdev.com marketing and licence-management site only. The extension itself does not depend on Firebase.
• Zoho Mail — transactional email (licence keys, support replies).

Sub-processors are listed in the Privacy Policy and the compliance/ working evidence record.

Compliance posture.

• Accessibility. WCAG 2.1 AA achieved as of v6.2.4. Every release runs a 5-baseline axe-core regression suite in CI; new violations fail the gate before publication. The single accepted exception is page-has-heading-one, which is structurally inappropriate for an iframe-embedded extension whose host page (Azure DevOps) owns the page-level h1 — adding our own would create competing top-level headings in the user's accessible heading tree.
• SOC 2 Type 1. Evidence collection in progress. Working documentation maintained internally; ask via support for status updates.
• GDPR. Personal data processed by Baytek is limited to the licence record and install telemetry above. Customers acting as data controllers can request deletion via support.

Settings storage. All extension configuration (workflow mapping, WIP limits, AI provider keys, access control, user preferences) is stored at organisation scope in Microsoft's Azure DevOps Extension Data Service — Microsoft-managed infrastructure that Baytek systems do not access. Configuration survives extension upgrades and is removed by Microsoft on uninstall.

Engineering quality bar. Releases are gated through 500+ automated tests:

• Unit tests (vitest) — exercise every analytics calculation against real-ADO captures and synthetic fixtures across all four Microsoft stock processes (Agile, Scrum, CMMI, Basic) plus arbitrary custom processes.
• End-to-end tests (Playwright) — validate the hub shell, navigation, configuration save persistence, trial flows, accessibility, and visual regression baselines.
• Accessibility regression suite — axe-core runs against five baseline views on every release; new WCAG 2.1 AA violations fail the gate.
• Visual regression baselines — five baseline screenshots gated for unintended UI drift.

A failure in any layer stops the release from being packaged.

What's New in Version 6.18

v6.18.0 — One radar for every team you run (June 2026)

Multi-Team Aging is now a full radar board. If you run several teams, keeping every board open to spot stuck work doesn't scale. Multi-Team Aging now ranks every team by aging risk with Act Now / Watch / Healthy buckets, a stand-up mode that jumps straight to at-risk items, per-team drilldowns, and cross-project team selection.

Also in this release: the single-team Monte Carlo "How many?" forecast now takes a target date directly, and Sprint Capacity working-day counts now use the same shared time frame as the rest of the extension — if you're west of UTC, counts may shift by one day on first open; the schedule underneath hasn't moved, the way we read the calendar boundary did.

What's New in Version 6.17

v6.17.2 — Fewer license dialogs during brief network blips (June 2026)

If a license check happened during a momentary network hiccup or backend deploy, the extension used to show a license dialog — even though everything was fine. It now retries quietly for up to three seconds before surfacing anything, so brief blips stay invisible. Real licensing errors still surface immediately.

v6.17.1 — Aging Chart Include/Exclude Weekends dropdown working again (June 2026)

In v6.17.0 (pre-release, not publicly shipped) the per-team working-week plumbing silently overrode the Aging Chart's Include/Exclude Weekends dropdown, so the toggle had no visible effect on day counts. v6.17.1 restores the dropdown as the primary control: pick Calendar Days to count every day, pick Business Days to count only your team's working days. v6.17.0 was caught in pre-release manual testing and was never made available publicly; v6.17.1 is the first public release of this batch and carries all of the v6.17.0 changes below.

v6.17.0 (pre-release, not publicly shipped) — Day counts now agree across time zones (June 2026)

If your team spans more than one country, two teammates looking at the same work item could see the stage duration or "days here" count disagree by a day. Same item, same dashboard — just two browsers reading the calendar boundary from different sides of midnight. As more teams using Agile Analytics work across Europe, the Americas, and Asia, this disagreement became a recurring friction in cross-region standups. The calendar math is now anchored to one shared frame so every viewer sees the same number for the same item. The first time you open after this update, some items' day counts may shift by one in either direction — the data underneath hasn't moved, just the way we read the calendar boundary. A few items hovering on the edge of the "stuck" colour band may change colour to match.

Per-team working week now reads directly from your Azure DevOps team settings. Sun-Thu (Middle East), Sat-Wed (Gulf), and other non-Mon-Fri working weeks now get correct sprint math in the Aging Chart's Business Days mode instead of always skipping Saturday and Sunday. No configuration step on your side; if your team has working days set in Azure DevOps, we read them. Auto-discovery also now reads workflow state names in Polish, Dutch, and Swedish on top of English, Spanish, Portuguese, Italian, German, and French — three languages added to the existing six.

What's New in Version 6.16

v6.16.1 — Removed the duplicate feedback card (June 2026)

The green "What should we improve next?" card on the trial dashboard has been removed. It pointed at the same form as the Ask Henry button in the top bar (shipped in v6.15.6), so customers saw two CTAs going to the same place. Ask Henry stays as the single feedback surface.

v6.16.0 — Trial-reminder signup is now one click less (June 2026)

The trial-reminder email prompt now subscribes you automatically using the email Azure DevOps already knows about you, with a 60-second Undo banner if you'd rather not be reminded. Previously, every trial customer had to retype their own email into the prompt and click Send — a step that customers routinely skipped, leaving the Day 7 / 14 / 23 / 28 reminder emails with no inbox to reach. The Undo button deletes the email server-side and skips re-firing on next session; one-click unsubscribe is included in every reminder email as the long-tail opt-out. If Azure DevOps doesn't have a valid email for you (rare — typically a personal account viewing an org-scoped extension), the original click-Send-to-confirm form still renders as the fallback.

Why Teams Choose Agile Analytics

No infrastructure — ever Everything runs in the browser against your live ADO data. No Azure Function, no database, no service connection to configure. Install, claim admin access, map your workflow states once, and it works across your entire organization.

Sprint Capacity + Monte Carlo together Plan with capacity-adjusted commitments, then validate with a 10,000-run Monte Carlo forecast. The two views are designed to be used together before every sprint.

WIP alerts that actually reach you Set WIP limits per team, connect a Teams or Slack webhook, and get notified the moment a team goes over — with a direct link to their active sprint taskboard.

Background Monitor — alerts without the browser open Configuration generates the Azure Pipeline YAML for you. Your admin adds it to a repo, sets a cron schedule, and WIP alerts run automatically — even when nobody has ADO open. Zero external infrastructure, runs entirely within your tenant.

Retro-ready in one click Export any sprint summary to a branded PowerPoint slide deck. Paste it into your retro without formatting work.

AI that uses your actual data When the AI Assistant is enabled, it reads your live sprint report before answering. Not generic advice — answers grounded in your team's actual numbers. Connect Claude, OpenAI, or GitHub Copilot using your own API key.

Role-based access control Built-in Admin/User role system with ADO directory search. Keep it open to all project users, or switch to assigned-users-only mode for controlled rollouts.

Dark mode Full dark theme — persisted per user, toggled with one click.

Getting Started in Under 2 Minutes

Step 1 — Install Open the Marketplace listing and install the extension into your Azure DevOps Services organization.

Step 2 — Open Navigate to any project → find Agile Analytics in the left navigation bar under your project name.

Step 3 — Claim Admin Access (Required) An Azure DevOps Project Administrator or Organization Administrator must go to Tools → Configuration → Access Control and click Claim Admin Access.

Step 4 — Configure Workflow Mapping (Required) Go to Tools → Configuration → Workflow Mapping and map your board states to analytics flow stages. This is what makes cycle time and flow metrics accurate for your process.

Step 5 — Select your team and explore Use the team selector in the top-left corner, then browse views using the top navigation.

Optional Visit Tools → Configuration to set WIP limits, add Teams/Slack webhook alerts, configure the Background Monitor, and run Readiness checks.

Complete Access Control claim and Workflow Mapping before broad rollout for correct analytics behavior.

Access Control

Agile Analytics includes a lightweight built-in role system — no Azure DevOps group configuration required.

1. An Azure DevOps Project Administrator or Organization Administrator visits Configuration → Access Control and clicks Claim Admin Access
2. Admin chooses whether the extension is open to All project users or restricted to Assigned users only
3. Admin adds users by searching the ADO directory and assigning them Admin or User roles
4. Admin configures which views are visible to User-role members
5. Admins always see every view regardless of settings

Settings are stored at organization scope in Azure DevOps Extension Data Service — one configuration shared across all users in the org.

AI Assistant (Optional)

Disabled by default. When enabled:

• Ask natural language questions: "How did Team Alpha perform this sprint?"
• Reads your live sprint data before answering
• Connect Anthropic Claude, OpenAI, or GitHub Copilot with your own organization-managed API key
• Configure provider, model, per-session request limits, and output token limits
• Admins can disable it org-wide via Configuration → Access Control

Data sent when AI is active: your prompt + sprint name + team name + aggregated metrics (point counts, percentages). Work item titles and user names are never included automatically.

Notification Alerts

Connect to Microsoft Teams or Slack to receive automatic alerts. Seven configurable triggers:

Sprint Health

• Commitment Reliability Low — fires when reliability drops below your threshold
• Scope Churn Exceeded — fires when mid-sprint scope changes exceed your churn threshold
• Carryover Risk — fires when carry-over share is too high
• Sprint End Summary — one-time digest at sprint end

Flow & WIP

• WIP Over Limit — fires when any team exceeds its WIP limit; links directly to their active sprint taskboard
• Stale In-Progress Items — fires when items have been in-progress for more than 5 days

Digest

• Weekly Sprint Digest — once-per-week summary of sprint health and flow status

Configure in Tools → Configuration → Notifications. Paste your webhook URL, select triggers, and save.

In-session vs Background: Alerts above fire when a user has the extension open. For automated alerts without the browser open, use the Background Monitor.

Background Monitor — Alerts Without the Browser Open

Configuration → WIP Settings generates a YAML file for your Azure Pipeline. After your admin adds that file to a repo and creates the pipeline, it runs on your chosen cron schedule, checks WIP limits, and posts to Teams or Slack automatically.

• Zero external infrastructure — runs entirely within your ADO organization
• No PAT required — uses Azure Pipeline's built-in service account
• Fully auditable — YAML file is committed to your repo; inspect or modify anytime

Permissions Explained

We request only what we use. No vso.code, no vso.analytics, no write permissions.

Requirements

• Azure DevOps Services (cloud) — any tier
• Project Contributor access or higher
• Modern browser (Edge, Chrome, Firefox)
• Azure DevOps Server (on-premises) — not supported in this version

FAQ

Does this extension store my data anywhere? Your Azure DevOps work item content, sprint data, and AI prompts stay in your browser and your ADO tenant — Baytek never sees them. The only data on Baytek systems is your licence record (organisation name, plan, expiry, activation token) and a lightweight install/heartbeat ping (organisation name, extension version, timestamp) so we can count active installs and detect outages. Settings, workflow mappings, AI API keys, and access control are stored in your org's Azure DevOps Extension Data Service — Microsoft-managed infrastructure that Baytek does not access. Full details in the Privacy Policy.

Will my settings be lost when the extension updates? No. All settings (WIP limits, workflow mappings, notification webhooks, AI configuration, access control, user preferences) are stored using the ADO Extension Data Service key-value API, which is version-agnostic. Upgrading never resets your configuration.

Does it slow down Azure DevOps? No. The extension makes the same REST API calls you would make manually — one view at a time, only when you navigate to it. No background polling, no persistent connections.

Why do I see no data on Cycle Time, Flow Metrics, or Flow Efficiency? These views require completed sprints with items in a Done/Closed/Resolved state. As of v6.1.0 your project's custom state names are auto-discovered — open Configuration → Workflow Mapping and assign each of your states to a stage (In Progress / Test / Review / Done). The Cycle Time preview panel under each mapping shows exactly which states will count.

How does Sprint Capacity work? Sprint Capacity reads the capacity your team sets in Azure DevOps Boards (the days/hours per member per sprint). It calculates each member's available working days after personal and team-wide days off, computes effective team capacity as a percentage, and multiplies your average velocity by that percentage to suggest a realistic sprint commitment. If capacity hasn't been set in ADO Boards, the view will prompt you to add it there first.

Do I need to configure anything before rollout? Yes. An admin should claim admin access (Configuration → Access Control) and complete workflow mapping (Configuration → Workflow Mapping) before rolling out to the team.

How do I set up the AI Assistant? Go to Configuration → AI Settings. Select Claude, OpenAI, or GitHub Copilot, enter your API key, set usage guardrails, then enable and save.

Can I control who sees what? Yes — through the built-in Access Control. Admins can choose open access for all project users or restrict to assigned users only, and control which views regular users can see.

Does it work across multiple projects? Yes. The extension installs at organization level and is available in every project. The current plan includes unlimited teams and projects across your organization.

Is dark mode supported? Yes. Click the theme toggle in the top-right of the navigation bar. Preference is saved per user.

What happens if I uninstall? Your ADO work items, sprints, and boards are completely unaffected — this extension only reads data, never writes to work items. Extension Data (settings, preferences, access control) is deleted on uninstall.

What is AI Metrics and who can use it? AI Metrics is a company-wide AI adoption dashboard. It is included in the 30-day trial and every paid subscription. When no live AI source is connected, it shows realistic demo data so you can explore the layout. To connect a live source, go to AI Metrics → Settings (admin required) and enter credentials for GitHub Copilot, Microsoft 365 Copilot, or a Custom API endpoint.

What is AIIP? AIIP (AI Improvement & Intervention Panel) is an admin-only companion to AI Metrics. It surfaces automated alerts when users are at risk of disengagement (low usage, high rejection rate, sudden drop), lets admins log interventions and mark them done, celebrates milestones, and can send Teams webhook notifications per team. All actions are written to an audit log.

What are the dashboard widgets? Three Azure DevOps dashboard widgets: Team Health, Cycle Time, and Throughput. Add them to any project dashboard from the widget catalog — they appear under the "Agile Analytics" category. Each widget uses the same team selector and data as the main hub views.

Data & Privacy

What stays in your tenant: Azure DevOps work item content, sprint data, AI prompts and responses, and any AI provider API keys 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), and anonymous usage events (view navigation, configuration completion, trial-day milestones — opt out at Configuration → Privacy). Plus an optional admin email if a trial admin chooses to opt in to milestone reminders.

Optional integrations: when you enable the AI Assistant or webhook notifications, requests go from your browser directly to the AI provider (Anthropic / OpenAI / GitHub Copilot) or webhook URL (Microsoft Teams / Slack) — never via Baytek.

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