CEDX 2026 Delivery Release: Resource capacity, sprint velocity, billable PSA timesheets, and milestone invoicing on one graph Explore the CEDX Sprints architecture ->
CEDXSystems
EnglishTalk to sales
PROJECTS & DELIVERY CEDX Sprints
Overview Commit Commit risk Workflow & Tour Operators TCO Model 14-Day Sandbox Live build ↗
PROJECTS & DELIVERY CEDX Sprints · Projects & Delivery · sprints.cedxsystems.com

Commit against capacity. Score the risk.

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.

Open live CEDX Sprints -> Inspect 4-screen build tour
18 issues scored in Sprint 42 21 pts expected to fail −34 pts capacity headroom Zero-ETL Shared Postgres Record
CEDX Sprints Enterprise Architecture Briefing
CEDX Sprints · 18 issues scored in Sprint 42

"We started with one application to fix our most painful bottleneck, and added five more modules on the same login with..."

Arjun Patel · SVP of Global Operations · Keystone Logistics · 0.01s Canonical Sync
CEDX Sprints reads and writes the exact same canonical Postgres record as CEDX Issues, CEDX Projects, and CEDX Roadmap with zero third-party webhooks.
🔒 https://sprints.cedxsystems.com/workspace/live
CEDX Sprints · Overview (Day 6 of 14, stated plainly)
sprints.cedxsystems.com · 01 Overview · Live Canonical Dataset
● Overview Active · 0.011s Sync Open /app/sprints ↗
ISSUES SCORED IN SPRINT 42
18
3 rated high risk (≥55%)
EXPECTED TO FAIL
21 pts
Σ remaining × risk%
CAPACITY HEADROOM
−34 pts
82 pts of queue on 48 pts of capacity
VELOCITY MEAN
40 pts
±2.2 across 14 tracked cycles
Program / Client Engagement Milestone & Sprint Phase Delivery Principal Budget / Billable Margin Capacity Utilization Delivery Health
Meridian Global ERP RolloutCEDX Sprints · Record #1040 Phase 03 · Data Migration K. Vance · Principal Architect $680,000 · 44% Margin ● 88.5% Billable Util On Schedule
Q4 Core Kernel Release v4.8CEDX Sprints · Record #1041 Sprint 22 · 64 Story Points A. Rostova · Staff Eng Lead 18 Engineers Allocated ● 92.0% Sprint Velocity Zero Blockers
Harbor Retail POS DeploymentCEDX Sprints · Record #1042 180 Stores · Wave 2 Cutover M. Okafor · Program Dir $510,000 · 41% Margin ● 85.2% Field Capacity Milestone Billed
SOC-2 & ISO Continuous AuditCEDX Sprints · Record #1043 Control Evidence Automation R. Lin · Security PMO $140,000 Internal Cap ● 100% Evidence Linked Audit Ready
✦ CEDX Sprints Copilot · Meridian Global ERP Rollout
Overview Verified
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.
CEDX Sprints operator workspace in natural daylight
FIELD DOCUMENTARY · PROJECTS & DELIVERY

Capacity is a number, not a feeling

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.

CAMERA: CANON EOS R5 · 35MM F/1.4 · NATURAL DAYLIGHT ESTATE ROUTE: /APP/SPRINTS
CORE CAPABILITIES · CEDX SPRINTS

Three architectural jobs CEDX Sprints gets right on one record.

Every capability below runs against the shared CEDX Postgres database with zero external sync queues or reconciliation lag.

01 · PROJECTS & DELIVERY FOUNDATION

Capacity is a number, not a feeling

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.

✓ 52 pts committed · 0 pts headroom · open queue 82 ptsVerified
✓ Per-person load vs adjusted capacity, OVER / UNDER printedVerified
✓ Copy from last sprint, one clickVerified
02 · LIVE EXECUTION

Risk with a named reason

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.

Risk with a named reason
CEDX Sprints Live Telemetry ● 18 issues scored in Sprint 42
03 · DETERMINISTIC GOVERNANCE

Carry treated as a forecast, not a surprise

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.

✓ Velocity mean 40 pts ±2.2 across 14 cyclesActive
✓ Carry-in 8 pts · scope added 6 pts, both on screenActive
✓ Sprint dates on the record: 2026-07-28 → 2026-08-10Active
04 · VERIFIED DEMO DATASET METRICS

What the live CEDX Sprints build looks like when you open /app/sprints.

Every figure below is directly inspectable in the running CEDX Sprints application workspace with zero synthetic projections.

ISSUES SCORED IN SPRINT 42
18
3 rated high risk (≥55%)
EXPECTED TO FAIL
21 pts
Σ remaining × risk%
CAPACITY HEADROOM
−34 pts
82 pts of queue on 48 pts of capac
VELOCITY MEAN
40 pts
±2.2 across 14 tracked cycles
4-SCREEN RUNNING BUILD TOUR

Four screens captured from sprints.cedxsystems.com, in the order operators run them.

Click any screen below to inspect how CEDX Sprints moves from initial intake to verified cross-estate completion.

01 OVERVIEW
Day 6 of 14, stated plainly
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
Plan the sprint against the people
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
The queue you argue with
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
Fourteen sprints of institutional memory
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.
01 OVERVIEW · SPRINTS.CEDXSYSTEMS.COM

Day 6 of 14, stated plainly

● Live Screen Capture

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.

✓ Completed vs committed, last 7 sprints, on one chartVerified in /app/sprints
✓ Active sprint by status: 5 todo · 6 in progress · 5 in review · 2 blocked · 0 doneVerified in /app/sprints
✓ Retro actions counted into the sprint they were promised toVerified in /app/sprints
Day 6 of 14, stated plainly
OPERATING CADENCE · PROJECTS & DELIVERY

How CEDX Sprints runs across the week, in the exact order work happens.

Engineering sprints, consultant timesheets, resource bench capacity, and milestone billing read from the exact same project object.

STAGE 01

Capture & Ingest

Records land in CEDX Sprints already linked to the canonical customer, employee, or vendor ID.

STAGE 02

Score & Triage

Deterministic rules and auditable Copilot signals rank every item by financial and SLA impact.

STAGE 03

Execute & Approve

Operators resolve work in one click with role-based guardrails and instant cross-app writeback.

STAGE 04

Reconcile & Report

Every completed action updates live executive dashboards and the immutable audit log automatically.

OPERATOR WORKSPACES · WHO RUNS CEDX SPRINTS

Three roles open CEDX Sprints every day. Each sees the exact surface they own.

Role-based views and permissions are enforced at the database row level so executives, managers, and frontline operators share one source of truth.

Scrum master using CEDX Sprints

Scrum master

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%
Product owner using CEDX Sprints

Product owner

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
Engineering lead using CEDX Sprints

Engineering lead

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 pts
ONE CANONICAL RECORD ACROSS 132 APPLICATIONS

Every Completed Task Updates Project Margin and Triggers Client Invoicing

CEDX Sprints is not an isolated point tool. It reads and writes the exact same customer, ledger, and identity records as the rest of the CEDX software estate.

CONNECTED MODULE 01 Open /issues/ ->

CEDX Issues

Every scored row in the risk queue (DATA-904, CHK-2410) is an issue with labels, a workflow and an SLA clock.
CONNECTED MODULE 02 Open /projects/ ->

CEDX Projects

The board and the slip predictor read the same commitment; Projects shows it across the workspace, Sprints inside the cycle.
CONNECTED MODULE 03 Open /roadmap/ ->

CEDX Roadmap

Carry-out is how epics slip: the roadmap's initiative progress moves when the sprint's 26 pts land somewhere.
CONNECTED MODULE 04 Open /timesheets/ ->

CEDX Timesheets

When the sprint's points become hours, the utilisation and billable share are Timesheets' reading of the same people.
ARCHITECTURAL PROOF · OPERATOR PERSPECTIVES

Why enterprise operators replace stitched SaaS stacks with CEDX Sprints.

"We started with one application to fix our most painful bottleneck, and added five more modules on the same login without a single migration project."

Arjun Patel
Arjun Patel
SVP of Global Operations · Keystone Logistics

"Consolidating onto CEDX eliminated four middleware connectors and cut our weekly forecast and close reconciliation from two days to twelve minutes."

Marcus Vance
Marcus Vance
Chief Revenue Officer · Meridian Systems

"When Sales, Operations, and Finance read and write the exact same Postgres record, month-end stops being a detective investigation across six spreadsheets."

Elena Rostova
Elena Rostova
Chief Financial Officer · Northline Group
LIVE TCO & CONSOLIDATION MODEL · PROJECTS & DELIVERY

Stop paying five vendors to re-sync the same projects & delivery record.

Drag the seat slider to compare your current stitched stack (Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo) against running CEDX Sprints natively on the unified CEDX estate.

Organization Seats 250 seats
25 seats 500 seats 1,250 seats 2,500 seats
Legacy Stitched Stack
Jira Align + Kantata (Mavenlink) + Asana Enterprise + Float + Tempo
$1,380,000 / yr
CEDX Sprints + Full Estate Bundle
All 132 applications · Canonical Postgres · Unlimited Copilot
$267,000 / yr
Verified Annual Hard Savings
Plus 0 middleware sync failures
$1,113,000 / yr
TECHNICAL & PROCUREMENT FAQ · CEDX SPRINTS

Questions operators and architecture teams ask before piloting CEDX Sprints.

01 Is the software on this page real? +
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.
02 How is sprint capacity computed? +
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.
03 What is the commit-risk score? +
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.
04 What happens to work that does not finish? +
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.
05 Do retro actions just disappear after the meeting? +
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.”
LIVE SANDBOX · ZERO MIDDLEWARE · NO CARD REQUIRED

CEDX Sprints is running right now. Open it and inspect the record.

Explore the live CEDX Sprints workspace on canonical demo data at /app/sprints, or book a 30-minute architecture session to map your first entity rollout.

Open live CEDX Sprints (/app/sprints) -> Book an estate architecture map