Burndown Diagnosis
Diagnose a burndown or burnup from the user's own sprint, release, or project data plus team notes.
Sample result
How it works
What Burndown Diagnosis does
Separates gross burn from scope change, fits velocity overall and recently, projects a finish with an explicit range, computes the velocity required to hit the date, classifies the curve pattern (flat then cliff, scope drift, steady shortfall, late batch landing, stale sizing), links each pattern to evidence in blockers, work in progress, carryover, and interruptions, and ends with ranked recovery options (cut scope, extend, add capacity, unblock, reduce work in progress) with trade-offs.
Use it when
Someone asks why we are behind, whether we will make the sprint or release date, what the burndown is telling us, how much scope to cut, or what the recovery options are.
Use something else for
Turning raw standup updates into a summary, for scoring risks, or for pricing a requested addition.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Burndown diagnosis, velocity projection, recovery options and pattern analysis
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Burndown Diagnosis
Updated Oct 20, 2026.
What does Burndown Diagnosis do?
Diagnose a burndown or burnup from the user's own sprint, release, or project data plus team notes. Separates gross burn from scope change, fits velocity overall and recently, projects a finish with an explicit range, computes the velocity required to hit the date, classifies the curve pattern (flat then cliff, scope drift, steady shortfall, late batch landing, stale sizing), links each pattern to evidence in blockers, work in progress, carryover, and interruptions, and ends with ranked recovery options (cut scope, extend, add capacity, unblock, reduce work in progress) with trade-offs. Use when someone asks why we are behind, whether we will make the sprint or release date, what the burndown is telling us, how much scope to cut, or what the recovery options are. Do not use for turning raw standup updates into a summary (use standup-digest), for scoring risks (use risk-register), or for pricing a requested addition (use scope-change-brief).
Who is Burndown Diagnosis for?
It is designed for scrum masters, delivery managers, product owners, engineering managers and sponsors.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Burndown Diagnosis produce?
Burndown diagnosis, velocity projection, recovery options and pattern analysis. Results come back with their sources and any open questions for you to check before anything is used.
How much does Burndown Diagnosis cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt71d80020…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Burndown Diagnosis fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.