CEDX Sprints · Projects & Delivery
Sprints turns planning into arithmetic: 52 pts committed against 48 pts of capacity, 0 pts of headroom, and a commit-risk model that scores all 18 issues in the sprint and expects 21 pts to fail — with the reason printed on each row.
The best row in the risk queue is the boring one: risk 5%, top signal “Healthy commit, protect capacity.” A planning tool should tell you when to leave well alone, too.
Runs on demo data. Sprint 42, day 6 of 14, is the seeded demo sprint.
What it is
The Commit screen builds capacity from the team up: ten working days, days off subtracted per person. Eli is 3 days off and carries 11 pts against 6 — 183%, flagged OVER in red before the sprint starts, not after it burns.
Every scored issue carries its top signal. DATA-904 sits at 95% with “Unfinished carry-in from prior sprint”; another row reads “Owner historical miss rate 28%”; a third, “Added after sprint start (no capacity trade).” You argue with a reason, not a colour.
Cycles keeps fourteen sprints of history and future in one ledger — cap, commit, done and carry-out per row. The active sprint's projected carry reads 19 pts at 40% risk on day 6, while the goal line admits 0 of 5 goal issues done.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/sprints.
01 — Overview
Committed 52, completed 19, remaining 46, velocity 40. The health ring reads 54% and earns it: goal 0/5 done, blocked open 16, WIP 110. The alerts name the pressure points — DATA-904 at 95% commit risk, the sprint over-committed by 4, and 5 retro actions still open from last time.
02 — Commit
60 backlog items above the line, 23 of them P0/P1 and marked “should plan soon.” Below, the team's adjusted capacity row by row — role, points per sprint, days off, assigned vs remaining — with two people already OVER before day one.
03 — Commit risk
Eighteen rows, each with status, points, remaining, risk%, expected fail and the top signal that produced the score. Capacity headroom reads −34 pts; the simulated fail column holds at 21 pts with no levers pulled — the Planning simulator tab is where you pull them.
04 — Cycles
History and future in one table: cap, commit, done and carry-out per cycle, with the active row's goal — “Ship checkout v3 beta + auth MFA” — and its progress, 13 of 28 goal points done. Carry-out is a column, so a sprint that leaks is visible in the record.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Lives in the commit-risk queue during planning and the health ring during the sprint. Over-commit by 4 pts is a conversation on day one, not day fourteen.
sprint health · 54%
Owns the goal line — 0/5 goal issues done on day 6 is their number — and trades scope adds against capacity, one swap at a time.
goal progress · 13/28 pts
Reads the top signals. “Owner historical miss rate 28%” is a coaching conversation; “unfinished carry-in” is a scoping one. The queue tells them which.
expected fail · 21 ptsThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Capacity is built from the team — days off subtracted, per person — and the commitment is checked against it: 52 on 48, with the over-commit flagged before the sprint starts.
Every issue in the sprint gets a risk score and a named top signal, so the planning argument is about reasons: carry-in, miss rate, backlog age, estimate confidence.
Day by day the overview reconciles done against committed — 19 of 52 on day 6 — and re-prices the carry forecast as blocked work sits.
The retro's action items go on the record and into the next sprint's alerts: 5 are still open, and Sprint 42's overview says so.
One record
Commitment, risk and carry are computed over the same issues the rest of the estate reads. There is no second copy of the work to reconcile at the end of the sprint.
Every scored row in the risk queue — DATA-904, CHK-2410 — is an issue with labels, a workflow and an SLA clock.
CEDX ProjectsThe board and the slip predictor read the same commitment; Projects shows it across the workspace, Sprints inside the cycle.
CEDX RoadmapCarry-out is how epics slip: the roadmap's initiative progress moves when the sprint's 26 pts land somewhere.
CEDX TimesheetsWhen the sprint's points become hours, the utilisation and billable share are Timesheets' reading of the same people.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your team, your points
Sprints with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/sprints. It runs on demo data.
From the team, not from a guess: each person has points per sprint and days off, and days off reduce effective points over the ten working days. Eli at 3 days off has 6 effective pts and 11 assigned — 183%, marked OVER on the Commit screen.
A per-issue score with the reason attached. Remaining points times risk% sums to the expected fail — 21 pts for Sprint 42 — and the top-signal column prints the driver: unfinished carry-in, owner historical miss rate, backlog age, an add after sprint start.
It is forecast before it happens and counted after. The carry forecast reads 26 pts at close on day 6; the Cycles ledger records carry-out per sprint, so a pattern of leaking sprints is visible in the history.
No. They are tracked as open items and surfaced into the next sprint: Sprint 42’s overview carries the alert “5 open retro actions — prior retro commitments still open into active sprint.”
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then score the sprint you are sitting in right now.