POD AI · DELIVERY HEALTH
Sprint overview
A live-data prototype for delivery status, team progress, and planned-versus-logged time.
Delivery team
All delivery teams
Multi-team sprint view
ISSUES IN VIEW
—
— not completed
STORY POINTS
—
— completed points
COMPLETION
—
BLOCKERS
—
Needs attention across teams
Issue status
Current distribution across the project view
Planned vs logged time
1 Story Point = 6 hours
—Planned hours
—Time logged
—Logged minus planned
Daily worklog coverage will appear after the snapshot is refreshed.
AGILE DELIVERY
Sprint performance
Select a SAFe iteration to compare team commitment, completion, carryover, and burndown. Use the delivery-team filter to focus this view and the other dashboard sections.
Team sprint breakdown
Commitment, completion, carryover, and burndown availability by delivery team
| DELIVERY TEAM | COMMITTED | COMPLETED | COMPLETION | CARRYOVER | BURNDOWN |
|---|
Burndown
Remaining work by day, based on Jira issue history
Story Points
Issues
FIX VERSION HEALTH
Release progress
— fix versions
Released vs unreleased
Fix Version counts by fiscal quarter (Nov–Oct)
Released
Unreleased
Archived
| VERSION | STATUS | PROGRESS | START DATE | RELEASE DATE | DESCRIPTION |
|---|
TEAM PERFORMANCE
Delivery teams
| DELIVERY TEAM | ISSUES | POINTS | DONE | BLOCKED | PLAN / LOGGED |
|---|
SPRINT TIME TRACKING
Worklogs by delivery team
Plan = Story Points × 6 hours; planned hours belong to the issue assignee and actual hours to the worklog author. Checks cover Monday–Friday since sprint start, with today separate; public holidays are not excluded.
JIRA ISSUE TRACKER
Issues
| ISSUE | DELIVERY TEAM | FIX VERSION | ASSIGNEE | STATUS | PRIORITY | POINTS | PLAN / LOGGED (H) |
|---|
No issues match these filters.