Getting StartedFebruary 5, 2026· 6 min read

Getting Started with Agile Analytics: Installation and First Steps

A step-by-step guide to installing Agile Analytics from the Visual Studio Marketplace, configuring it for your Azure DevOps project, and getting your first sprint metrics in minutes.

#installation#setup#azure devops#getting started#configuration

Getting Agile Analytics up and running takes under 5 minutes. Because the extension runs entirely inside Azure DevOps with no external backend, there is no server to configure, no API key to manage, and no data pipeline to set up. This guide walks you through installation and your first dashboard experience.

Step 1: Install from the Visual Studio Marketplace

Go to the Visual Studio Marketplace and search for "Agile Analytics" by Baytek, or follow the direct link from the button at the top of this page. Click "Get it free" and select the Azure DevOps organization where you want to install it. The Starter plan is free with no time limit — you can use sprint velocity, burndown, and basic flow metrics at no cost.

Step 2: Open the Extension in Your Project

After installation, navigate to any project in your Azure DevOps organization. In the left sidebar you will see a new "Agile Analytics" hub. Click it to open the main dashboard. You should see the Sprint Health view by default.

Step 3: Select Your Team and Iteration

At the top of each view you will find Team and Iteration Path dropdowns. These are populated from your existing Azure DevOps configuration:

  • Team — select the team whose sprints you want to analyze
  • Iteration Path — select the sprint or iteration to focus on, or choose "All" for a cross-sprint view
  • Date range — available on flow metric views to set the analysis window

Step 4: Explore the Dashboards

Here is a suggested exploration order for first-time users:

  • Sprint Velocity — look at the last 6 sprints and check your commitment reliability percentage
  • Sprint Burndown — review the most recent sprint burndown for scope creep or late completion patterns
  • Cycle Time — run through the scatter chart and note the 85th percentile value for your team
  • WIP Monitor — see how many items are currently in progress and compare to your team size
  • Monte Carlo — enter your remaining backlog count and get a probabilistic delivery forecast

Step 5: Configure Access Controls (Pro+)

On Pro and Business plans, you can control which Azure DevOps users and groups can access each section of the analytics. Navigate to Settings within the extension to configure role-based access. This is useful for restricting sensitive forecasting data to managers while giving all team members access to sprint health metrics.

Next Steps

Once you have explored the basic dashboards, consider these next steps to get more value from Agile Analytics:

  • Share the Sprint Velocity and Burndown views in your next sprint retrospective to ground the conversation in data
  • Set WIP limits in the WIP Monitor configuration and discuss them with your team
  • Run a Monte Carlo forecast for your current quarter's roadmap and share the probability dates with stakeholders
  • Enable the AI Agile Coach (Business plan) to get automated sprint health summaries and improvement suggestions
  • Set up the Background Monitor to receive alerts when WIP limits are exceeded or items become blocked

Ready to move from reading to rollout?

Use the install guide for the shortest path into Azure DevOps, then compare plans when you need more than Starter.

Related reading