Docs / Deliver

Planning

The release planner. It spreads the backlog over sprints using your team's capacity, counted in velocity or working days as set on the Estimation tab. The AI generates the plan, or in Manual mode you add sprints and place and split features yourself, then adjust with a timeline, burndown and sprint management.

When to use it

When you know what is in the backlog and need to know when it can ship.

Start here

Set the parameters in the bar at the top and click "Generate Plan", or switch to Manual and click "Add sprints". It works best with estimates and team members in place.

How to use it

  1. Choose the planning mode at the top right. "AI" shows "Generate Plan"; "Manual" shows "Save Settings" and a "Manual planner" panel instead. If the project has streams, you can also switch the view between "project" and "stream".
  2. In the bar below, optionally pick a "Stream", then either keep "Team velocity" on or turn it off and type a "Velocity/sprint". Set "Buffer %", "Sprint weeks" (1 to 4) and "AI multiplier".
  3. In AI mode, click "Generate Plan". The timeline fills with features and epics as rows and sprints as columns, and each bar shows the points allocated to that sprint.
  4. In Manual mode, click "Add sprints" in the "Manual planner" (how many, and when the first starts). Under "Unallocated features" pick a start sprint and points for each feature, then click "Assign".
  5. For a feature under "On the plan", change its start sprint, click "Split" to spread its points over 2 to 4 consecutive sprints (they must add up to its total), or click "Remove" to take it off the plan.
  6. Read the sprint headers: each shows allocated points against capacity, an over-capacity sprint turns red, and diamond markers show milestones that fall inside the sprint.
  7. Click an epic's bar or name to open its panel: change "Estimated Points", "Priority" or "Stream", add "Split Config" entries, then "Save & Re-plan". Drag a bar sideways to move its whole feature to another start sprint.
  8. In "Sprint Management", use "Edit" for dates, goal and points, "Stories" to add or remove stories, and "Capacity" for hours and holiday days per member. "Start Sprint" starts a planned sprint; "Close Sprint" closes an active one.

Good to know

  • "Effective" is the team's velocity times the AI multiplier, reduced by the buffer. If the Estimation tab's "Capacity basis" is "Working days", capacity comes from team days instead and the note beside "Team velocity" reads "Capacity: working days". Members come from the Costing tab.
  • Guardrails are non-blocking warnings: over capacity, dependency violation, scope creep, unallocated feature, unestimated feature, underutilised sprint. Open "Guardrails" and click "Dismiss" on each one you have dealt with. Manual mode does not stop you over-filling a sprint.
  • Dashed arrows on the timeline connect epics that have dependencies, and bars take the colour of their stream. The "Velocity" and "Burndown" charts are at the bottom of the page.
  • Closing a sprint starts creating a retrospective page in the project's knowledge base. When the page exists, a "Retro" link appears in that sprint's row and stays after you reload. It opens the page in the Knowledge Base tab.
  • "Consolidate Streams" appears when the project has streams. It merges stream plans into one project view, either "Sequential" or "Parallel", and a "Revert" button then lets you undo it.

Related

Last updated 6 October 2026