driftless Route Optimization Pilot
Search As of 2026-07-01

A greyed-out label above marks a link this fixed demo does not ship: only the story project's pages go this deep, and an action a live reader could take here (signing in, applying a technique) is disabled in a read-only export.

Route Optimization Pilot

As of 2026-07-01 · Process map · Wizard · Schedule · Flow · Board · Weekly status · RAID log · Requirements & WBS · Team · Procurement calculator · Cost workbench · Quality workbench · Closeout · Schedule network · Decisions and meetings · Earned value calculator · Scope worksheet · Stakeholder assist · Decision tree · Probability and impact · Risk responses

Status

Process completeness 8%

Integration
Integration 0%
Scope
Scope 0%
Schedule
Schedule 17%
Cost
Cost 0%
Quality
Quality 0%
Resource
Resource 0%
Communications
Communications 0%
Risk
Risk 43%
Procurement
Procurement 0%
Stakeholder
Stakeholder 0%

No cost baseline yet — earned value has nothing to measure

Baseline the plan (POST /baselines, POST /baseline-lines) and record spend (POST /cost-entries); the wizard walks that order.

Flow

Work in progress 0 items · throughput (last 7 days) 0 items · median cycle time no data yet · no release forecast yet. See the flow page.

Scorecard strategy

amber Reduce fleet waste · Internal Operations · supporting contribution

Live threats

red Integration · score 1.00 — Overall health is red: red in resource; amber in quality, communications.
red Resource · score 0.20 — 1 person over-allocated (peak ratio 1.20 — 24 h in all, 24 h of it on this project).
amber Quality · score 1.00 — Quality is unmeasured: no quality measurements are recorded for this project.
amber Communications · score 1.00 — Communications reporting is behind cadence: no status reporting at all (no status snapshot).

RAID

Open risks 1 · open issues 0 · open change requests 0

Risk reserve suggested: 600.00 — the open register's residual exposure, from the risk-response planner.

Milestones

No milestones yet — these are the dates this project is judged against

Add one with POST /milestones (this project's id, a target date); a slipped one then shows here and on the threat board.