← Back to Mark Curtiss

Business Analyst Dashboard Sample data

Standard business analysis metrics (requirements, stakeholders, process KPIs, value, UAT, data quality, gap analysis, MoSCoW, deliverables) · As of Oct 29, 2026 · Fictional initiatives

Sample data. Every number, name and initiative on this page is fictional (Project Orion, Nimbus and Atlas are made up). Connect Jira/Azure DevOps, a requirements tool and your BI platform to replace it with live data.

Contents

Initiative

Requirements Health of the requirements set and backlog

Requirements by status

Backlog readiness

What it tells a BA: high churn or ambiguity means elicitation was incomplete or scope is unstable; low traceability means some requirements may ship untested or tests exist with no business need. Refinement depth under 2 sprints risks the team pulling unready work.

Stakeholders Engagement, sign-off and open decisions

Power / interest grid

Open questions & decisions

What it tells a BA: low sign-off rates and aging decisions are leading indicators of schedule slip. The power-interest grid sets how often and how deeply each stakeholder is engaged.

Process & business performance KPI scorecard, as-is vs to-be, funnel and trend

Sales conversion funnel

Claim cycle time vs target (days)

Claim cycle timeTarget

What it tells a BA: the scorecard proves whether the solution changed the business, not just whether it shipped. The funnel shows where conversion drops (Qualified → Proposal is the weakest step here) and the trend shows whether gains are holding.

Value & business case Benefits realization, ROI, NPV and payback

Planned vs realized benefit ($K, cumulative by quarter)

Planned benefitRealized benefit

What it tells a BA: benefits realization closes the loop on the business case. Realized at 87% of plan through Q3 means the solution is working but adoption or process change is lagging.

Quality & UAT Acceptance testing and change control

Requirements-related defects by root cause

Change requests by impact

ApprovedPendingRejected

What it tells a BA: defects caused by requirements (rather than code) point back to elicitation and review quality. Many high-impact change requests signal the original scope was not well understood.

Data & analytics Data quality and report adoption

Report views (last 30 days)

What it tells a BA: decisions are only as good as the data. Low timeliness or accuracy undermines KPI reporting; low report usage means the analytics deliverable is not meeting a real need.

Gap analysis & MoSCoW prioritization

Requirements by MoSCoW

What it tells a BA: gap analysis turns the current vs future state into a scoped work list. Must-haves should stay at or below about 60% of effort so the release keeps room to absorb change; here they are 43% of items.

BA deliverables tracker Status as of Oct 29, 2026 (sample)

Metric definitions & thresholds Formula and green / amber / red targets

Thresholds are common industry rules of thumb (aligned with IIBA BABOK practice); tune them to your organization. Sample data