Skip to content
kumo

Milestones and scenarios

Production lives in Tasks → Production. Its pages are Milestones, Goals, Products, Marketing, Funding, Templates, Localization and Budget; a studio can hide, rename or add pages.

Production → Milestones draws the project’s milestones on a timeline, with their dependencies. Milestones that follow each other share a row, so a long project stays readable. Each milestone holds its tasks; moving a task’s dates moves what the milestone shows.

A scenario asks what if without touching the plan. Open Scenarios from the Milestones menu; production roles see it.

  • Give each task or milestone a priority: must, should or could. A task takes its milestone’s, and one with none counts as should.
  • Cut what does not fit. A cut can be restored, and it is never a delete; what depends on a cut task goes with it.
  • Set the crews that do the work: their disciplines and hours a day.
  • Ask for a date or a budget, and kumo suggests the cuts that meet it: could first, then should, never must.
  • Compare against a baseline to see the scope that crept in since.

The board changes only when you apply a scenario: its cut work is marked cut (and leaves the totals, the schedule and the timeline), its dates are written, and its crews become the plan.

Production → Budget holds the production budget beside the milestones it pays for, where the project keeps a production folder.

The Goals button, beside New milestone, holds the studio’s goals and their key results. A key result follows a milestone, a task query or an Insights figure by itself, or is set by hand with a weekly check-in. See Goals and key results.

A funding call you track becomes a task with the call’s deadline, so it shows on the timeline beside the milestone it would pay for. See Funding.