Skip to main content
Compass

Delivery

Delivery tracking & scope management

Scrum Master Guide: Delivery Tracking

Delivery tracking in Jellyfish operates at the deliverable level — giving Scrum Masters visibility across epics, initiatives, and features that span multiple sprints. Unlike sprint-level metrics, delivery tracking surfaces scope drift, effort alignment, and completion trends over weeks.

The four delivery endpoints power this view:

  • work_category_contents — lists all deliverables within an epic, initiative, or feature category
  • deliverable_details — returns status, issue counts, and effort for a single deliverable
  • deliverable_scope_and_effort_history — weekly scope and effort history for scope creep detection
  • work_categories — enumerates all work category types configured in your Jellyfish instance

Scope & Effort Trend

8-week view — story points per week

W1
W2
W3
W4
W5
W6
W7
W8
ScopeEffort
W1: Scope: 54%, Effort: 46%. W2: Scope: 60%, Effort: 57%. W3: Scope: 50%, Effort: 51%. W4: Scope: 71%, Effort: 64%. W5: Scope: 57%, Effort: 60%. W6: Scope: 79%, Effort: 71%. W7: Scope: 67%, Effort: 70%. W8: Scope: 86%, Effort: 79%

Active Deliverables

Current delivery status by deliverable

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

API Explorer

MockMock

Scrum Master Playbook: Delivery Insights

Three high-value patterns for delivery visibility:

1. Scope Creep Detection

Use deliverable_scope_and_effort_history to compare week-over-week scope changes. A rising scope line alongside flat or declining effort signals unplanned work entering the deliverable. Flag deliverables with significant week-over-week scope growth and bring them to the next planning session. Define your own threshold based on your team's tolerance for scope change.

2. Cross-Sprint Visibility

Deliverables span sprints, but sprint health metrics do not. Pull work_category_contents weekly to build a deliverable-level health summary that persists across sprint boundaries. This gives leadership a stable signal even during sprint transitions or mid-sprint re-planning.

3. Stakeholder Reporting

Combine deliverable_details percent complete with effort data from allocations to build a concise status update: what is done, what is in flight, and where risk is concentrated. Group deliverables by work_category so business stakeholders see progress at the initiative level rather than the sprint level.