Tutorial

Find the tasks pushing back a release date

Use a release schedule and its constraint report to trace a missed deadline to its predecessors.

Compare the computed finish with the constraint

The sample release has implementation, checks, packaging, signing and clean-install testing. Use the schedule to see when Publish release can start, then read the violations to see why its finish constraint cannot be met. Look for the constraint-versus-predecessor message before trying to fix every negative-slack entry.

kaidoplan schedule compute --file release-demo.kaido --lang en
kaidoplan schedule path --file release-demo.kaido --lang en
kaidoplan violations --file release-demo.kaido --lang en

Test a realistic option on a copy

Copy the plan first. In the app, inspect the predecessors of Publish release and work backward through clean-install testing, signing and packaging. If a dependency is real, keep it. If some work can legitimately run in parallel, model that change on your copy and recompute. Do not make security or release checks optional just to make a date fit.

Record the tradeoff

Compare the original and revised finish dates and whether the target constraint still fails. Bring the specific change to the person who owns the deadline. If there is no credible schedule change, change scope or renegotiate the date rather than changing task estimates to hide the conflict.