Skip to main content
Jellyfish Compass

Roadmap Alignment

Investment vs plan & initiative health

Planned vs Actual

Side-by-side comparison of Jellyfish allocation data and your planned investment

Actual Effort (from Jellyfish)

FTE allocated per initiative — pulled from Jellyfish

Auth Service Rewrite4.2 FTE
Mobile App v3.03.8 FTE
Data Pipeline Migration2.1 FTE
API Rate Limiting0.8 FTE
Platform Monitoring2.4 FTE

Planned Effort (your input)

Enter your planned FTE per initiative from your roadmap


Gap Analysis

Difference between actual and planned FTE — gaps greater than 1.0 are highlighted in bold

Gap analysis between planned and actual FTE per initiative
InitiativePlanned FTEActual FTEGapStatus
Auth Service Rewrite4.04.2+0.2On Track
Mobile App v3.06.03.8-2.2Under-Invested
Data Pipeline Migration2.02.1+0.1On Track
API Rate Limiting1.50.8-0.7Under-Invested
Platform Monitoring1.02.4+1.4Over-Invested

Initiative Health

Delivery status of active deliverables across your initiatives

Initiative health by deliverable
DeliverableCategoryIssuesCompleteStatus
Auth Service RewriteEpics2478%On Track
Mobile App v3.0Epics4245%At Risk
Data Pipeline MigrationInitiatives1892%On Track
API Rate LimitingFeatures830%Behind

Product Tool Integrations

Connect your roadmap tool for automatic planned vs actual tracking

Jellyfish integrates with product roadmap tools for automatic alignment:

ProductboardAha!ProductPlan

Connect your roadmap tool in Jellyfish platform settings for automatic planned vs actual tracking.

When you see under-invested initiatives, discuss in planning — is the team pulled toward unplanned work? When over-invested, check if scope expanded without the Product Owner's knowledge. Use this data to facilitate alignment conversations between product and engineering. Look for patterns in the allocations_by_work_category endpoint to surface recurring misalignment.