Loading dashboard data...

Upstream Health Check

Story Quality Analysis Across Active Projects
200Apps — Product Operations
Hemi — Head of Product Ops

What Did We Review?

Data Source

Scanned Stories and Epics across 4 active Jira projects. Analysis focused only on Stories & Epics — bugs, support tickets, and technical tasks were excluded.

What We Measured

6 Definition of Ready criteria: Target User Defined, User Journey Mapped, Acceptance Criteria Written, Design/UX Ready, Technical Review Done, No Blockers. Plus: User Story format and Acceptance Criteria coverage.

Review Period

Data pulled from Jira via Atlassian MCP.
Stories analyzed across all active projects.

How is the score calculated?
Criterion Weight Reason
Target User Defined 10% Basic — most stories have this
User Journey Mapped 15% Important for dev context
Acceptance Criteria Written 30% Most critical for dev readiness
Design / UX Ready 20% Prevents rework
Technical Review Done 15% Catches feasibility issues early
No Blockers 10% Basic hygiene
Score = (TUD×0.10 + UJM×0.15 + AC×0.30 + DUR×0.20 + TRD×0.15 + NB×0.10) / 10

Story Quality — Cross-Project Comparison

% of Stories with User Story format and Acceptance Criteria

Status Distribution

To Do / In Progress / Done per project

Definition of Ready — Radar Comparison

6 DoR criteria — % of Stories meeting each criterion per project

DoR Heatmap — Detailed Breakdown

Green = Strong | Yellow = Moderate | Red = Needs Attention

Release Progress

Per-project release tracking from Jira fixVersion field

Top 3 — Recommended Actions

Must — High Impact

Complete Acceptance Criteria

For every Story in Backlog / In Progress that has no AC — add clear, testable acceptance criteria

Good — Foundation

Unified Story Template

Including: User Story, Acceptance Criteria, Tech Notes, UX link, Flow reference

All projects | Consistency + quality
Good — Visibility

Document User Journeys

Add Figma board link or flow diagram in every Story description