Skill: Metric Render Catalog

Capability Domain: Analytics Communication
Technology Stack: Athena, Streamlit, Jupyter

Purpose

A portable list of ready-made metrics and how to render them. Use during Look until Trusted and mart pages. This catalog does not replace Cost of Delay / impact scoring (people × touch + downstream × wait). The reconstructed cycle remains the opening visual for Tell the Data Story.

When a view is missing

Only chart metrics whose contract views exist. Do not invent joins across sources without an explicit key (issue key, PR number, commit SHA).

Starter mart tabs (Streamlit)

When Present Findings uses Streamlit, instantiate the tab pack in skill Present Findings with Streamlit. Skip a tab whose required views are absent. Map families → tabs:

Tab	Families on that tab
Commits	VCS velocity
Work items	Issue flow
Changes	Merge-request / pull-request flow
Pipelines	CI health
Load	Load signals
Defects	Defect flow
Sprints	Sprint planning

Those tabs are drill-down. They are not the stakeholder opening visual.

Metric families

Issue flow (Jira views, if scoped)

• Closed / day, touched / day (resolved vs updated).
• Lead time: business days created → resolutiondate; cohort = resolved in window. Show count, avg, median, min, max.
• Cycle time: business days first Started segment → resolutiondate; exclude never-started. Same distribution stats.
• Time-in-status: calendar hours per status (open segment ends at now). Journey strip, not a Pulse KPI.
  Definitions: skill Jira Flow Extract.

VCS velocity (commit views)

• Commits / day, active authors, author share, conventional-commit type mix if messages follow that convention.

Merge-request / pull-request flow

• Opened / merged / day.
• MR cycle: wall-clock hours created → merged (merged in window). Median, mean, min, max, n.
• Optional source-branch → trunk band (avg + min/max) when a branch convention is in the contract.
• Integrator vs reviewer series are separate roles (assignments ≠ approvals).

CI health (workflow / pipeline views)

• Failure rate, status-by-day stack, duration trend, top failing jobs or reasons.

Sprint planning (only if Agile snapshots were extracted)

• Completed points, committed vs delivered, rolling average, unestimated share. Separate from issue lead/cycle. Do not use sprint reports as the flow clock.

Defect flow (bug/defect types if present)

• Opened vs closed, time-to-target-status, open-age buckets.

Load signals (commit timestamps)

• Long-day / weekend session share. Risk indicators, not performance scores.

Render pairings

Pattern	Best render	Notes
KPI strip	4–6 period deltas	Inverse color when lower is better (lead/cycle, failure %, age)
Daily throughput	labeled bar or area	Zero-fill missing days
Duration trend	line + points	Hours or days; optional min–max band
Part-to-whole	donut	Author share, failure reasons
Ranked people or jobs	horizontal bar	Integrators, reviewers, failing jobs
Workflow wait	single-row stacked H-bar	Time-in-status, left-to-right by configured workflow order
Drill-down	table + deep link	Always show sample size n

Shared UX

• Windows: 7 / 14 / 30 calendar days (or closed-sprint count for sprint metrics).
• Period-over-period: fetch 2 × window and split, or use an explicit prior offset.
• Empty states: say "no resolved issues in window" (or equivalent). Do not draw a zero cycle as if work happened.
• Feature-path / single-stage charts are look-until-trusted checks, not the stakeholder opening visual.

Pitfalls

• Equating issue lead/cycle (business days) with MR created→merged (hours).
• Using the mean of daily averages as the exec KPI (unweighted by volume). Prefer per-item median + n.
• Hard-coding one project's status order or issue-type list in this catalog.
• Ranking impact by p90 duration alone (that is Cycle Impact Scoring's job).
• Treating the starter tab list as the opening story.