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.

★★★★★ "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.

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.

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.

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. 30+ 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. Four read-only Azure DevOps 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.
• 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

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
• "Where does our engineering time actually go?" — Investment Allocation: completed work classified into features vs. bugs vs. maintenance per team, plus an unplanned-work share
• "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

Delivery & Investment

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.

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, multiple teams, or a security-reviewed enterprise rollout.

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/

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.
5. Exec Report scheduled digests (added in v6.26.1, only if you schedule one). When you schedule an Exec Report email digest, Baytek's backend relays the email on your chosen schedule. Recipients confirm by email before anything is sent (double opt-in), and every email carries a one-click unsubscribe link. Stored: the subscription record (recipient email address, schedule, confirmation status). Report content is never stored on our servers.

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.31

v6.31.1 — Service Level Expectations find work you categorize with a field or a tag (July 2026)

Fixed: an SLE for a category you track with a custom field or a tag showed "No data." Service Level Expectations read "X% of type finish in Y days" and matched the name only against ADO work-item types. Teams that track a category another way — a "Spike" that is really a User Story whose custom "Category" field is set to "Spike", or a story tagged "Spike" — saw "No data" on that target even when the work existed and had breached the window.

New: a "Work category field" setting on the SLE configuration. Point it at the field that sub-categorizes your work (Configuration → SLEs) and an SLE target matches that field's value when no work-item type matches — org-wide, so one admin sets it and the whole team's Dashboard agrees. Targets named after a tag work with no setup at all. This is fallback-only: any SLE that already matched a real work-item type is untouched, so no working number changes. And because SLEs always evaluate the trailing sprint window, your past sprints count immediately — if a "No data" SLE starts showing results after this update, that is the work it was always meant to measure.

v6.31.0 — See throughput and WIP in story points, not just item counts (July 2026)

New: a Count / Points toggle on Flow Metrics and the WIP Monitor. Some teams measure delivery in items finished; others in story points. Both views now carry a Count / Points switch: in Points mode, Flow Metrics shows throughput as points per sprint across the trend, histogram, and sprint table, and the WIP Monitor shows each team's in-progress load in points. Points are read from your existing estimates — Story Points, or a numeric Size/Effort field, or a T-shirt size (XS–XXL) — nothing new to configure. The default stays Count, so nothing changes unless you switch, and your choice is remembered per view. Items with no estimate are excluded from the Points total and the view tells you how many ("N of M items have no estimate"), so a missing estimate never quietly reads as zero. WIP limits, delivery forecasts, and CSV exports stay item-based by design.

More representative DORA numbers for large organisations. For orgs with more than 200 completed items in a window, the DORA detail metrics (lead time for changes, time to restore) sampled the 200 oldest items rather than a representative spread — an artefact of how the work-item query returned results. They now draw a genuine random sample across the window. If your organisation is past that size, your DORA lead-time and restore-time figures may shift after this update — the new numbers are the more representative ones, not a change in your delivery. Separately, imported work items that were "born done" with no recorded completion date now carry a small "estimated date" note in the Cycle Time views, so a derived date is never presented as an exact one.

What's New in Version 6.30

v6.30.0 — A delivery forecast that was reading backwards is fixed, and every chart got a clearer redesign (July 2026)

Your delivery forecast was reading backwards. The Monte Carlo "How many items will we finish?" cards pair a confidence level with a number — but the two were inverted: the 95%-confidence row showed the 95th-percentile outcome (a number you'd reach only about 5% of the time) while the 50% row showed an easy target. Higher confidence now correctly maps to a lower, safer commitment — "95% = we'll almost certainly finish at least this many." If you use these figures for sprint commitments, expect them to change with this update; the new numbers are the honest ones.

A clearer look across every chart. Flow Efficiency now shows the healthy 15–40% band as a gauge with your team's marker on it, states a plain verdict, and flags a suspicious near-100% score as likely missing wait data — so a data gap no longer looks like a perfect process. WIP Monitor replaces its wall of team cards with a sorted load chart where the busiest team and anyone over their limit float to the top. The Flow Trend chart no longer squeezes throughput and cycle-time days onto one shared axis — each measure now has its own panel. Delivery Signals collapses its duplicated metric rows into one card per signal. Live Stats, Aging & Blocked, Cycle Time, DORA, Cumulative Flow, Process Behaviour and the rest all get the same consistent palette and denser, more scannable layouts. These are visual changes — the underlying numbers are unchanged.

Two views read more truthfully. The Cycle Time Heat Map's rows were inverted, putting the slowest band on top; the fastest delivery times now read at the top. And Aging & Blocked tints an item's risk by how long it has been flowing against your cycle-time percentiles, rather than time in a single stage — so where an item's colour shifts, that is the more accurate read, not new movement.

What's New in Version 6.29

v6.29.0 — Truer numbers for imported work and unmapped workflows; the whole product in six languages (July 2026)

Two classes of misleading numbers are corrected. Work items migrated into Azure DevOps already completed (the shape Jira and CSV imports produce) took their completion time from the import moment, inflating cycle times into the hundreds of days while burnup claimed nothing was finished — they now use their real completion dates. And for teams without a saved workflow mapping, items in Resolved, Completed, or Ready for Release states read as eternally in progress in some views while others counted them delivered; every view now gives the same answer (your Workflow Mapping remains the boss if Resolved means "awaiting verification" for your team). Confidence labels also now use one ruler product-wide, so a small sample reads consistently as Low, and low-sample caveats follow your numbers into the digest, exec summary, and retro views.

The full product now renders in all six supported languages: dashboard widgets, Team Benchmarks — including its bottleneck findings and recommendations — and blocked-state tracking, which previously counted blocked days as zero for non-English state names. Also fixed: the single-item timeline no longer accrues phantom "sitting in Done" days, and duplicating a browser tab lands on the view you were on instead of resetting to the Dashboard.

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 Copy any sprint summary in one click, or open the new Exec Report as a print-ready PDF for stakeholders. 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.

Frequently Asked Questions

Does Agile Analytics need a Personal Access Token (PAT)? No. It runs in your browser using your existing Azure DevOps session and four read-only scopes. There is no PAT to create, rotate, store, or leak — and no service connection to configure.

Does my work-item data leave Azure DevOps? No. Every analytics view is computed in your browser against the Azure DevOps REST API. Sprint contents, work-item titles, code, comments, and PII are never sent to a Baytek server. This is the key difference from SaaS engineering-metrics platforms that pipe your data into their own warehouse.

How is this different from the built-in Azure DevOps dashboards and Analytics views? Azure DevOps gives you raw widgets and OData feeds — you still have to build velocity, cycle-time, flow, and forecasting reports yourself. Agile Analytics ships 30+ ready-made views — Monte Carlo forecasting, cycle-time percentiles, flow efficiency, DORA metrics, investment allocation, and sprint-capacity planning — with zero query-building.

Do I need to configure anything before I see data? No. On first open the hub auto-discovers your workflow states and renders your active sprint immediately. You can fine-tune the state-to-stage mapping later under Configuration → Workflow Mapping; a live preview shows exactly which states will count.

Which processes does it support — Scrum, Kanban, SAFe, or a custom process? All of them. It reads your team's own workflow states, so custom Azure Boards processes and renamed columns work out of the box.

Can it forecast when we'll finish? Yes. The Monte Carlo view runs thousands of simulations on your real throughput history to answer "how many will we finish?" and "when will this be done?" with P50/P85 confidence bands — no story-point estimation required.

Does it work with Azure DevOps Server (on-premises)? Not in this version — Agile Analytics supports Azure DevOps Services (cloud) only.

Is there a free trial, and how does pricing work? Yes — a 30-day free trial starts automatically on install, no credit card. After that it is per-seat: Team ($25/month, 2 seats), Business ($100/month, 6 seats), or Premium ($2,000/year, unlimited seats). Every plan includes every feature. A seat is one user who opens the extension in a 30-day window.

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