Sample ART Analysis

This is what your discovery looks like. Four teams, 85 features, seven dimensions of analysis.

71
ART Health
🟡 Needs Attention
↓ Deteriorated vs previous PI

Four teams · 85 active features

Manzanas Team
28 items active
Items28/85
72% orphan rate
⚠ Needs Attention
Plátanos Team
23 items active
Items23/85
Best AC coverage
✓ Healthy
Frutillas Team
18 items active
Items18/85
Uncoordinated deps
⚠ Needs Attention
Mangos Team
16 items active
Items16/85
High dependency load
🔴 At Risk

Key metrics

41%
With PI Objective
🔴 Critical
0%
Business Value Defined
🔴 Critical
34%
AC Complete
🟡 Low
1/4
Dependencies Coordinated
🔴 Critical
3
Placeholder Features
🟡 Review
2
In Dev Without AC
🔴 Critical
Top 3 — Improvements

What you can act on

Define Business Value at ART level
0% of active features carry a Business Value score. Teams leave the field empty or use it as a narrative. Until BV has a shared definition, every prioritization decision is opinion, not data.
Impact: High · Affects all 4 teams
Reduce orphan features before next PI
59% of active features have no PI Objective. They're being built but invisible to leadership. Either they belong to a goal that wasn't connected, or they shouldn't be in the active backlog.
Impact: High · Primarily Manzanas Team (72% orphan)
Establish a cross-team dependency process
4 active dependencies detected. Only 1 has coordination items on both sides. The other 3 are one-sided — one team is waiting on output the other hasn't committed to.
Impact: High · Mangos Team → Plátanos Team affected
Top 3 — Inconsistencies

What needs immediate attention

GDPR / PII exposure — Implementing without review
A feature handling personal data is currently in Implementing state with no AC and no documented review gate. Active regulatory exposure — not a risk to track, an action to take now.
Team: Frutillas · Severity: 🔴 Critical · Action: Pause implementation, define scope, request DPO review
Placeholder feature active for 2+ PI cycles
A feature marked "placeholder for future analysis" sitting in Funnel state for 2+ cycles. No owner, no scope, no AC, no connection to any PI Objective. It appears in reports and creates false coverage.
Team: Manzanas · Severity: 🟡 High · Action: Owner assigns scope in 1h or remove from backlog
Uncoordinated dependency — one-sided only
Mangos Team has 2 features in Ready state depending on an API endpoint owned by Plátanos Team. Plátanos has no corresponding item in backlog. If they don't commit, Mangos hits a blocker mid-sprint.
Teams: Mangos → Plátanos · Severity: 🔴 Critical · Action: Create coordination item, confirm delivery sprint

Recommended action before PI Planning closes

Resolve the GDPR item first. It's the only finding with active regulatory exposure. Everything else can be planned into the next cycle.

Estimated time to unblock: 4 hours (scope definition + DPO review request)

Ready for the full analysis?

This sample covers what the discovery includes. A session with our team goes deeper — context, recommendations per team, and a plan for the next cycle.

Book a session →