Navigator · Scenario simulator
Test a delivery decision before you commit to it.
Pick a scenario, enter counts and dates, and see whether the plan holds, where the critical chain is, which waits staffing cannot shorten, and what would have to change. Every finding names the rule and inputs behind it.
Scenario
Define the situation.
How it works
Explainable by design.
The simulator schedules the remaining work as a dependency network with lead and tail overlaps, checks it against team capacity, treats decisions, external data, reviews and sign-off as fixed waits that extra programmers cannot shorten, and applies independent-QC rules. Effort per unit comes from your calibrated parameters if you have saved them in the Capacity Estimator, otherwise from illustrative defaults that are not benchmarks.
Inputs→Effort→Schedule→Rules→Verdict + why