Health is computed, not reported
Plans that tell you when they stop being true.
Backlogs, boards, sprints and a timeline, with goals whose health follows from the numbers: dates against progress, work that waits for other work, overdue tickets. Nobody has to remember to set a status to red.
Goal · due in 12 days
Self-serve billing live
- 1 ticket waits for unfinished work. They are blocked by tickets that are not done.
- Progress is behind the calendar. 67% of the time is gone and 48% of the work is done.
Release 2.4 · 31 open tickets
78% chance to make 27 Nov
Likely
21 Nov
Safe
28 Nov
Almost sure
3 Dec
Pace of the last 12 weeks · 7.4 tickets a weekScope 31
Date conflict: CHK-139 is due 14 Nov, but CHK-151 starts 12 Nov
Gone quiet ET-14
In review for 4 days without a change
Waiting for review #57
No approving review for 3 days
Blocked ET-19
In the sprint, waits for open ET-6
Slipping 2.4
Due in 18 days, open work needs 26 at the recent pace
The assignee hears about it once; the lead when it is serious.
The app’s own components, rendered with example data.
Backlog and board, scrum or kanban
A ranked backlog with sprints, bulk edit and saved filters, and a board with up to 12 columns of your own that each count as one of six statuses. Press C anywhere to create a ticket, ⌘K to find any ticket by key, words or comments.
A timeline with dependencies that argue back
Epics and features on a week, month or quarter scale, with arrows from each blocker to what it blocks. A red arrow is a date conflict: the blocker is due after the other ticket starts. Projects can include tickets of other projects they wait for.
Goals with computed health
Goals, objectives, milestones and releases, nested any way you like, with progress rolled up from every ticket below them. Health follows from the numbers unless a person sets it.
- At risk when progress is more than 15 points behind the time gone, when tickets wait for unfinished work, are overdue or are due after the goal.
- Off track when the due date passed with open work, or progress is more than 35 points behind.
- Analyze with Nova reads every ticket, comment and pull request below the goal and forecasts against the due date.
Sprints planned from your own pace
Plan with Nova proposes a sprint’s scope: blockers first, then the backlog by priority and rank, up to the team’s average velocity. Estimate sizes a ticket from the finished tickets closest in meaning and the time actually logged on them. Both are computed from your history, without sending anything to AI.
Dates as odds, not promises
The delivery forecast runs 5,000 simulations over the tickets finished in each of the last 12 weeks, for the project, a release, a milestone or an epic. It answers with Likely, Safe and Almost sure dates and the chance to make the due date.
A risk radar that scans every morning
At 7:00 the radar looks for work that has gone quiet, pull requests waiting for review, failing checks, blocked work in the sprint, overdue tickets, and releases or goals whose open work no longer fits the pace. The assignee hears once; the lead when it is serious.
- Every Monday a weekly update for stakeholders is written and posted to the project’s chat channels.
Initiatives across projects
An initiative groups epics from several projects and products under one outcome, with their progress side by side.
Questions
Can a person still override the health?
Yes. A person’s call wins. Without one, health follows from dates, progress and dependencies.
Are forecasts AI guesses?
No. Forecasts, the radar, sprint plans and estimates are computed from the project’s own history and are not AI actions. With nothing finished in 12 weeks there is no pace to forecast from yet, and the forecast says so.
Do you support story points and hours?
Both. Progress is weighted by story points when every ticket has them, then by hours, otherwise by count.
Give your next agent a brief.
Free for up to 10 people, with MCP for every agent. No credit card.