<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: AndonPulse</title>
    <description>The latest articles on DEV Community by AndonPulse (@andonpulse).</description>
    <link>https://dev.to/andonpulse</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4251403%2F0ca0068e-a4ec-4e4d-a1c6-31e6773290ae.png</url>
      <title>DEV Community: AndonPulse</title>
      <link>https://dev.to/andonpulse</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/andonpulse"/>
    <language>en</language>
    <item>
      <title>Software Engineering Intelligence Platforms Under the Hood: DORA, Cycle Time, and the Definitions Behind Them</title>
      <dc:creator>AndonPulse</dc:creator>
      <pubDate>Fri, 20 Nov 2026 17:47:49 +0000</pubDate>
      <link>https://dev.to/andonpulse/software-engineering-intelligence-platforms-under-the-hood-dora-cycle-time-and-the-definitions-1c46</link>
      <guid>https://dev.to/andonpulse/software-engineering-intelligence-platforms-under-the-hood-dora-cycle-time-and-the-definitions-1c46</guid>
      <description>&lt;p&gt;Software engineering intelligence platforms all promise the same things: DORA metrics, cycle time, PR flow, sprint health. Under the hood, each of them takes raw events from your issue tracker and Git host and runs them through a set of definitions. Change one definition, such as which status means "done" or which deployment counts as a failure, and the number on the dashboard changes with it.&lt;/p&gt;

&lt;p&gt;This post walks through how the common metrics are calculated, where the numbers usually go wrong, and how eight tools document their configuration. The list opens with AndonPulse, a &lt;a href="https://andonpulse.com/" rel="noopener noreferrer"&gt;software engineering intelligence platform&lt;/a&gt; that builds metrics on each team's own workflow rules. Facts about the other tools come from their public sites and docs as of November 2026.&lt;/p&gt;

&lt;h2&gt;What these platforms compute from your events&lt;/h2&gt;

&lt;p&gt;An engineering intelligence platform works on timestamps. A Jira issue moves from "To Do" to "In Progress" to "In Review." A pull request is opened, reviewed, approved, and merged. A deployment hits production, and sometimes an incident or a rollback follows. Gartner describes the category as platforms that "provide visibility of team activities with customizable dashboards and support metrics frameworks like DORA and SPACE" (&lt;a href="https://www.gartner.com/en/documents/5276563" rel="noopener noreferrer"&gt;Gartner&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;Every metric is a calculation over those timestamps: a difference between two events, a count in a time window, or a ratio of two counts. The math is simple. The hard decisions are which events mark the start and the end, and which records get excluded.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Table 1. Common metrics, how they are calculated, and what breaks them&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Metric&lt;/th&gt;
&lt;th&gt;How it's calculated&lt;/th&gt;
&lt;th&gt;What breaks the number&lt;/th&gt;
&lt;th&gt;What you should be able to configure&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Change lead time&lt;/td&gt;
&lt;td&gt;Time from a code change (commit or merge) to a successful production deployment&lt;/td&gt;
&lt;td&gt;Treating staging deploys as production; counting reverted changes&lt;/td&gt;
&lt;td&gt;Which environment is "production" for each service&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Deployment frequency&lt;/td&gt;
&lt;td&gt;Count of production deployments per period&lt;/td&gt;
&lt;td&gt;Config-only or infrastructure deploys mixed with app deploys&lt;/td&gt;
&lt;td&gt;Which pipelines and services count&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Change fail rate&lt;/td&gt;
&lt;td&gt;Deployments that needed immediate intervention ÷ all deployments&lt;/td&gt;
&lt;td&gt;Hotfixes not linked to the failed deploy; only rollbacks counted&lt;/td&gt;
&lt;td&gt;What counts as a "failure" (rollback, hotfix, incident label)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Failed deployment recovery time&lt;/td&gt;
&lt;td&gt;Time from a failed deployment to recovery&lt;/td&gt;
&lt;td&gt;Incidents closed late in the tracker; no link between incident and deploy&lt;/td&gt;
&lt;td&gt;Which incident source and which "resolved" event to use&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Deployment rework rate&lt;/td&gt;
&lt;td&gt;Unplanned deployments made in response to a production incident ÷ all deployments&lt;/td&gt;
&lt;td&gt;No way to tell planned from unplanned deploys&lt;/td&gt;
&lt;td&gt;Labels or issue types that mark unplanned work&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Cycle time&lt;/td&gt;
&lt;td&gt;Time from first "in progress" status to "done"&lt;/td&gt;
&lt;td&gt;Each team uses a different "done" status; tickets reopened&lt;/td&gt;
&lt;td&gt;Start and end status per team, handling of reopened items&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PR pickup / review / merge time&lt;/td&gt;
&lt;td&gt;PR ready for review → first review → approval → merge&lt;/td&gt;
&lt;td&gt;Bot PRs, draft PRs, and self-merges in the sample&lt;/td&gt;
&lt;td&gt;Bot exclusion, draft handling, which repos count&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Sprint scope change&lt;/td&gt;
&lt;td&gt;Work added or removed after the sprint started ÷ committed scope&lt;/td&gt;
&lt;td&gt;No fixed moment when the sprint scope is "committed"&lt;/td&gt;
&lt;td&gt;Scope freeze time, issue types, subtasks&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;The five DORA definitions above follow the current DORA guidance, which groups change lead time, deployment frequency, and failed deployment recovery time as throughput, and change fail rate and deployment rework rate as instability (&lt;a href="https://dora.dev/guides/dora-metrics/" rel="noopener noreferrer"&gt;dora.dev&lt;/a&gt;).&lt;/p&gt;

&lt;h2&gt;DORA: five metrics, five definitions you have to choose&lt;/h2&gt;

&lt;p&gt;DORA metrics are easy to state and hard to calculate consistently, because "production" and "failure" mean different things in different teams. A monorepo with ten services and three deploy pipelines needs a rule for each one.&lt;/p&gt;

&lt;p&gt;Here is the same month of deployments with two definitions of failure.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Table 2. Change fail rate with two definitions of failure (Demo data)&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Input&lt;/th&gt;
&lt;th&gt;Definition A: rollbacks only&lt;/th&gt;
&lt;th&gt;Definition B: rollbacks + linked hotfixes&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Production deployments&lt;/td&gt;
&lt;td&gt;40&lt;/td&gt;
&lt;td&gt;40&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Rollbacks&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hotfix deployments linked to a failed change&lt;/td&gt;
&lt;td&gt;not counted&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Failed deployments&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Change fail rate&lt;/td&gt;
&lt;td&gt;4 ÷ 40 = 10%&lt;/td&gt;
&lt;td&gt;7 ÷ 40 = 17.5%&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;em&gt;Demo data. Illustrative numbers, not from a real team.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Neither number is wrong. They answer different questions, and the team has to choose one and keep it stable. A tool that hard-codes one definition makes that choice for you, and you may not notice until two teams compare their scores.&lt;/p&gt;

&lt;p&gt;On a &lt;a href="https://andonpulse.com/dora-metrics-platform/" rel="noopener noreferrer"&gt;DORA metrics platform&lt;/a&gt;, check three things: whether you can define production and failure per service, whether you can drill from the metric to the deployments and PRs behind it, and whether lead time is broken down by stage so you can see where the time went.&lt;/p&gt;

&lt;h2&gt;Cycle time is a sum of stages&lt;/h2&gt;

&lt;p&gt;A single cycle time number hides where the work waited. Split it into stages and the bottleneck usually becomes obvious.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fntqcp7di6wl1o6m10v6c.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fntqcp7di6wl1o6m10v6c.png" alt=" " width="800" height="298"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 1. Cycle time broken into stages.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The pull request part has three timers. Pickup time runs from the moment a PR is ready for review to the first review. Review time runs from the first review to approval. Merge time runs from approval to merge. A team with slow pickup needs a different fix than a team with long review threads.&lt;/p&gt;

&lt;p&gt;Two details change these numbers more than people expect. Bot accounts (dependency updates, release bots) can make up a large share of PRs and pull the median down. Draft PRs can start the clock before anyone is meant to look at the code. Good &lt;a href="https://andonpulse.com/pull-request-analytics/" rel="noopener noreferrer"&gt;pull request analytics&lt;/a&gt; exclude bots, link each PR to its task, and show reviewer load by person and team, so you can see whether review is slow everywhere or stuck on two people.&lt;/p&gt;

&lt;p&gt;This matters because "review is slow" is one of the most common complaints in growing teams. A thread on r/ExperiencedDevs asks exactly that: "&lt;a href="https://www.reddit.com/r/ExperiencedDevs/comments/1rjfo06/why_does_code_review_take_forever_once_teams_hit/" rel="noopener noreferrer"&gt;Why does code review take forever once teams hit 15-20 engineers&lt;/a&gt;". With stage-level data, you can answer it for your own team.&lt;/p&gt;

&lt;p&gt;One AndonPulse customer example: a B2B SaaS company with 40 engineers in 5 teams, on Jira and GitHub, measured the wait for the first review and spread review load more evenly. Over four months, the median wait for first review went from 2 working days to 1, and median task cycle time went from 8 to 6 working days (&lt;a href="https://andonpulse.com/customers/b2b-saas-code-review/" rel="noopener noreferrer"&gt;B2B SaaS code review case&lt;/a&gt;). Their VP of Engineering put it this way: "Now when someone says review is slow, I can open the data and see if it's true."&lt;/p&gt;

&lt;h2&gt;Sprint scope change depends on when you freeze the scope&lt;/h2&gt;

&lt;p&gt;Sprint metrics compare what the team committed to with what it finished. The catch is the word "committed." If tickets are still being added on the first afternoon of the sprint, is that planning or scope creep?&lt;/p&gt;

&lt;p&gt;Most teams need a scope freeze point: for example, the scope at sprint start plus a one-day grace period. Everything added after that counts as added scope. You also need to decide whether subtasks count, which issue types are in scope, and how unplanned work is marked.&lt;/p&gt;

&lt;p&gt;Here is what a status and scope mapping can look like. This is not any product's configuration format, only a way to show which decisions a team has to make.&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;# Illustrative example, not product syntax
team: payments
workflow:
  
in_progress: ["In Progress", "In Review", "In QA"]
  
done: ["Done", "Released"]   # "In QA" is NOT done for this team
  
reopened: count_as_new_cycle
sprint:
  
scope_freeze: sprint_start + 1 working day
  
include_issue_types: [Story, Bug, Task]
  
count_subtasks: false
  
unplanned_work_label: "unplanned"
dora:
  
production_environments: ["prod-eu", "prod-us"]
  
failure: [rollback, hotfix_linked_to_deploy]
pull_requests:
  
exclude_authors: ["dependabot[bot]", "release-bot"]
  
start_review_clock: ready_for_review   # ignore draft time&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;&lt;em&gt;Illustrative example, not product syntax.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://andonpulse.com/sprint-analytics-software/" rel="noopener noreferrer"&gt;Sprint analytics software&lt;/a&gt; built on such rules can show committed scope against scope added or removed since the sprint started, forecast sprint completion as a range, and list carryover with the reasons behind it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd61pbnf03qvf57rorjgq.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fd61pbnf03qvf57rorjgq.png" alt=" " width="800" height="383"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 2. One event stream, two team definitions (Demo data).&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;Same data, two numbers: a worked example&lt;/h2&gt;

&lt;p&gt;Take five tickets from one sprint. The team's workflow is In Progress → In Review → In QA → Done.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Table 3. Cycle time with two end statuses (Demo data)&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Ticket&lt;/th&gt;
&lt;th&gt;Days to "In QA"&lt;/th&gt;
&lt;th&gt;Days to "Done"&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;PAY-101&lt;/td&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PAY-102&lt;/td&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PAY-103&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PAY-104&lt;/td&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;PAY-105&lt;/td&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Median&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;3&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;&lt;strong&gt;6&lt;/strong&gt;&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;&lt;em&gt;Demo data. Illustrative numbers, not from a real team.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;If the platform stops the clock at "In QA," the median cycle time is 3 days. If it stops at "Done," the median is 6. The difference is QA wait time, which is exactly what a manager may need to see. A dashboard with the first definition would hide it.&lt;/p&gt;

&lt;h2&gt;How 8 software engineering intelligence platforms handle definitions&lt;/h2&gt;

&lt;p&gt;The table below shows what each vendor documents publicly about configuration. "Not documented" means the item was not found in public docs as of November 2026; the product may still support it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Table 4. What each platform documents as configurable&lt;/strong&gt;&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Platform&lt;/th&gt;
&lt;th&gt;Documented configuration&lt;/th&gt;
&lt;th&gt;Source&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;AndonPulse&lt;/td&gt;
&lt;td&gt;Done status, scope freeze, subtasks, unplanned work, issue types per team; DORA production and failure definitions; status-to-stage mapping; capitalization rules by task type, status, and label&lt;/td&gt;
&lt;td&gt;andonpulse.com&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Swarmia&lt;/td&gt;
&lt;td&gt;Initiatives from labels and custom fields; custom PR inbox views; custom reports; working agreements&lt;/td&gt;
&lt;td&gt;swarmia.com&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Waydev&lt;/td&gt;
&lt;td&gt;Custom Metrics, Studio module, custom reports&lt;/td&gt;
&lt;td&gt;waydev.co, docs.waydev.co&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Jellyfish&lt;/td&gt;
&lt;td&gt;Custom dashboards and AI-powered queries; Scenario Planner for what-if planning&lt;/td&gt;
&lt;td&gt;jellyfish.co&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Haystack&lt;/td&gt;
&lt;td&gt;Alerts on delivery metrics; formula settings not documented&lt;/td&gt;
&lt;td&gt;usehaystack.io&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Hatica&lt;/td&gt;
&lt;td&gt;Custom dashboards (Business plan), custom metrics (Enterprise plan)&lt;/td&gt;
&lt;td&gt;hatica.io&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Codacy (Pulse docs)&lt;/td&gt;
&lt;td&gt;Documented formulas for lead time, cycle time, time to open, and time to merge&lt;/td&gt;
&lt;td&gt;docs.pulse.codacy.com&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Typo&lt;/td&gt;
&lt;td&gt;Rules configuration (Pro plan); Jira field mapping&lt;/td&gt;
&lt;td&gt;typoapp.io&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;h3&gt;AndonPulse&lt;/h3&gt;

&lt;p&gt;AndonPulse builds metrics on your own statuses, work types, labels, and rules, set up together with the AndonPulse team during onboarding. The &lt;a href="https://andonpulse.com/engineering-management-platform/" rel="noopener noreferrer"&gt;engineering management platform&lt;/a&gt; maps each initiative down to deliverables, issues, and workflow stages, so a forecast date or a risk flag can be traced to the task and stage that caused it. All five DORA metrics use your definitions of production and failure. PR review time is split into pickup, review, and merge, with bot accounts excluded.&lt;/p&gt;

&lt;p&gt;The same status mapping feeds finance: the &lt;a href="https://andonpulse.com/r-and-d-capitalization/" rel="noopener noreferrer"&gt;software capitalization platform&lt;/a&gt; applies rules by task type, status, and label, with an audit trail from hours to task and rule. Data comes in through &lt;a href="https://andonpulse.com/integrations/" rel="noopener noreferrer"&gt;read-only integrations with Jira, GitHub, GitLab, Linear, and HR tools&lt;/a&gt; (40+ in total). Pricing as of November 2026: free for up to 10 members, €20 per member per month for one module or €35 for everything, billed annually.&lt;/p&gt;

&lt;h3&gt;Swarmia&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://www.swarmia.com/" rel="noopener noreferrer"&gt;Swarmia&lt;/a&gt; covers code, issue, and DORA metrics and PR flow. Configuration is centered on how work is grouped: initiatives can be created from labels and custom fields, PR inbox views can be customized, and custom reports are available. Working agreements let a team set its own targets, such as review time, and track them. Free for up to 9 developers; Standard €42 per developer per month, billed annually (as of November 2026).&lt;/p&gt;

&lt;h3&gt;Waydev&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://waydev.co/" rel="noopener noreferrer"&gt;Waydev&lt;/a&gt; documents a dedicated metric builder: Custom Metrics, a Studio module, and custom reports are documented, alongside DORA, cycle time, and PR insights. It supports DORA, SPACE, DX, and CAFE(S) frameworks and a wide range of Git hosts, including Bitbucket, Azure DevOps, and Gerrit. Pricing is a custom quote, billed annually (as of November 2026).&lt;/p&gt;

&lt;h3&gt;Jellyfish&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://jellyfish.co/" rel="noopener noreferrer"&gt;Jellyfish&lt;/a&gt; supports DORA and SPACE metrics, AI metrics, and DevEx surveys. Its customization documented on the site is at the reporting layer: custom dashboards with AI-powered queries, plus Scenario Planner for modeling delivery trade-offs. Public docs do not describe editing the formulas behind workflow metrics. Pricing is quote-based (as of November 2026).&lt;/p&gt;

&lt;h3&gt;Haystack&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://www.usehaystack.io/" rel="noopener noreferrer"&gt;Haystack&lt;/a&gt; focuses on Git-based delivery analytics: DORA, cycle time, PR analytics, and alerts that notify a team when a metric drifts. It also runs developer surveys on sentiment, engagement, and burnout risk. It connects to GitHub, Bitbucket, and GitLab, and its pricing page says it works with metadata. Growth plan: $20 per member per month with an annual commitment, 14-day free trial (as of November 2026).&lt;/p&gt;

&lt;h3&gt;Hatica&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://www.hatica.io/" rel="noopener noreferrer"&gt;Hatica&lt;/a&gt; covers DORA, velocity, throughput, sprints, PR and cycle-time analytics, SPACE metrics, and a wellbeing view. Custom dashboards come with the Business plan and custom metrics with Enterprise. The free plan includes developer surveys and automated stand-ups with one month of history. Pro is $19 and Business $29 per member per month (as of November 2026).&lt;/p&gt;

&lt;h3&gt;Codacy (Pulse docs)&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://www.codacy.com/" rel="noopener noreferrer"&gt;Codacy&lt;/a&gt; sells code quality and security for AI-assisted engineering, with AI guardrails, merge gates, SAST, and coverage reports. Its engineering metrics live in the &lt;a href="https://docs.pulse.codacy.com/" rel="noopener noreferrer"&gt;Pulse documentation&lt;/a&gt;, which is useful reading even if you never buy the product: it publishes how lead time, cycle time, time to open, and time to merge are calculated. That level of formula transparency is rare in this category. Codacy's Team plan starts at $18 per developer per month billed yearly; separate Pulse pricing is not published (as of November 2026).&lt;/p&gt;

&lt;h3&gt;Typo&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://typoapp.io/" rel="noopener noreferrer"&gt;Typo&lt;/a&gt; combines delivery metrics (DORA, sprint metrics, cycle time) with automated PR reviews and code health analysis. Rules configuration is available on the Pro plan, and the Jira setup guide documents how fields are mapped. Starter is $20 and Pro $28 per developer per month, billed annually, with a 14-day free trial and no credit card (as of November 2026).&lt;/p&gt;

&lt;h2&gt;Process, not people&lt;/h2&gt;

&lt;p&gt;Metrics built from Git and Jira events describe how work flows through a system. When they are used to rank individuals, people start optimizing the number instead of the work. Developers say this openly; one r/ExperiencedDevs thread is titled "&lt;a href="https://www.reddit.com/r/ExperiencedDevs/comments/1wec6ba/is_gaming_developer_productivity_metrics_really_a/" rel="noopener noreferrer"&gt;Is gaming developer productivity metrics really a worthwhile battle?&lt;/a&gt;".&lt;/p&gt;

&lt;p&gt;Research on developer experience points in the same direction: productivity depends on feedback loops, cognitive load, and flow state, which no single activity count captures (&lt;a href="https://doi.org/10.1145%2F3610285" rel="noopener noreferrer"&gt;DevEx, ACM Queue, 2023&lt;/a&gt;).&lt;/p&gt;

&lt;p&gt;A few practical rules help. Look at teams and stages first. Use drill-down to a person to find a blocked review or an overloaded reviewer, and say so up front. Keep the metric definitions visible to the team, so people can see how a number was built and question the rule if it looks wrong. Baselines and common pitfalls are covered in more detail in the AndonPulse &lt;a href="https://andonpulse.com/blog/how-to-measure-developer-productivity/" rel="noopener noreferrer"&gt;guide to measuring developer productivity&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;A test you can run in any trial&lt;/h2&gt;

&lt;p&gt;The top software engineering intelligence platforms all show DORA and cycle time on a demo dataset. To see how a tool handles your workflow, run one test during the trial:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Pick one team and one recent month.&lt;/li&gt;
&lt;li&gt;Write down your definitions: done status, production environments, what counts as a failure, scope freeze.&lt;/li&gt;
&lt;li&gt;Ask the vendor to configure them, then change one rule (for example, "In QA" is not done) and watch whether the number recalculates.&lt;/li&gt;
&lt;li&gt;Open the metric and drill down to the tickets, PRs, and deployments behind it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you can't change the rule, or can't see the records behind the number, you will end up defending numbers you can't explain. Among software engineering intelligence platforms, the ones worth shortlisting are the ones that pass this test on your data.&lt;/p&gt;

</description>
      <category>devops</category>
      <category>productivity</category>
      <category>analytics</category>
      <category>software</category>
    </item>
  </channel>
</rss>
