Metrics
Definition, calculation and interpretation for every metric in Leanmote.
51 articles
- Pull Request ActivityVolume of PRs created, merged, and currently open during the selected period.
- Flow EfficiencyRatio of active time to total time on completed tasks — how much of an item's life is real work.
- Median Time to Market (TTM)Time from task ideation to release in production — end-to-end delivery duration.
- Total Active TimeTeam-level total time spent actively working on tasks during the period.
- Avg Age of Work in Progress (team-level)How old, on average, the team's currently in-progress items are.
- Unassigned TasksTasks in progress or in the backlog that don't have an owner yet.
- Submitter metricsThe four sub-metrics that show how efficiently submitters move pull requests toward merge: Iterated PRs, PR Iteration Time, Responsiveness, and Time to Merge.
- Reviewer metricsThe four sub-metrics that show how reviewers pick up, engage with, and approve pull requests: Reaction Time, Sharing Index, AVG Pickup Time, and TT First Approval.
- Reworked TasksTasks that moved backward in the workflow — quality and clarity signal.
- PRs Created (per member)Total pull requests opened by a single team member in the period.
- Reviews Count (per member)Total PR reviews submitted by a single team member in the period.
- Commits Count (per member)Total commits a single team member pushed during the period.
- PR Comments Count (per member)Total comments a single team member made on others' pull requests.
- Avg Member Time to MergeAverage time from PR open to merge for a single team member's PRs.
- Avg Member Review TimeFrom the reviewer side: average time a member takes to act on PRs they're reviewing — first comment, commit, or approval.
- Avg Member Time to First ApprovalAverage time from a member's PR being opened to its first approval.
- AI Governance metrics overviewHow AI Governance measures AI tool adoption and impact across your engineering team.
- AI Lead Time ComparisonLead Time for AI-tagged PRs vs non-AI PRs across the four sub-stages: Coding, Waiting for Review, In Review, Ready to Deploy.
- AI-assisted PRsPull requests with at least one AI-tagged commit, counted against total PRs in the period.
- AI-assisted CommitsCommits tagged as AI-authored, alongside the share against total commits in the period.
- AI Lines of CodeLines changed (additions + deletions) sourced from Copilot telemetry and PR-level diff data. No content-type exclusions today; AI and non-AI cohorts use the same formula.
- AI IntensityA composite per-day score combining AI activity, active users, AI commits, and AI lines of code. Used as the X-axis on AI-vs-delivery scatter plots.
- AI Tool CostMonthly estimated AI tool cost — Copilot from billing seat data, Claude Code and Cursor from active users × seat price. Includes utilization view and notes on default rates.
- AI User Engagement SegmentsPower, Casual, Idle, and New user segments — plus distinct weekly users and daily PR-merge intensity.
- Team ConnectivityHow Leanmote classifies team interactions into low, moderate, and high engagement levels using normal distribution to optimize collaboration patterns.
- DORA metrics overviewThe four DORA metrics, why they matter, and how Leanmote calculates each.
- Deployment FrequencyHow often production deployments happen — and how to interpret the trend.
- Lead Time for ChangesTime from code change to production deployment — and where the time goes.
- Mean Time to Recovery (MTTR)Average time to restore service after a production incident.
- Change Failure RateShare of deployments that fail or need a corrective change — and where the failure signal comes from.
- Flow metrics overviewThroughput, cycle time, WIP, and waiting time — the operational-flow metric set.
- ThroughputNumber of completed work items per period — your team's baseline capacity signal.
- Cycle TimeTime from active start to completion — the core flow-friction signal.
- Work in Progress (WIP)Items actively in flight — early warning for context-switching and overload.
- Waiting TimeAccumulated time items spend in non-active workflow states.
- Team Overview tab — what each metric tells youField guide to the per-member execution table on the Performance Delivery dashboard.
- Assigned TasksTotal items currently assigned to a team or member, regardless of state.
- Avg Member Cycle TimeAverage cycle time of items completed by a single team member.
- Avg Member WIP AgeHow old, on average, a team member's currently in-progress items are.
- Done Active TimeTotal active-state time accrued by items the team or member completed.
- Working TimeTotal elapsed wall-clock time across active workflow states.
- Active DaysDays the team or member transitioned at least one item in the period.
- Estimated HoursSum of estimates on items completed in the period.
- Estimated vs ExecutedHow estimates compared to actual time spent on completed work.
- Invested HoursTotal hours invested by the team or member across the period.
- Story PointsSum of story points on completed items.
- Sprint EfficiencyThe share of tasks completed during a sprint, counted at the task level. Includes important caveats about denominator scope.
- Team Collaboration Network — overviewHow review activity and cross-team collaboration get measured.
- Review participationShare of teammates who regularly review each other's pull requests.
- Review latencyTime from PR open or first review request to first substantive review.
- Activity distributionHow commits, reviews, and comments distribute across team members.