How to use the Sprint Planning Assistant.
Sprint planning should consider capacity and dependencies before filling the board. Keep a clear sprint goal and room for known operational work.
Make the workflow fit your task.
Choose a coherent sprint goal, review candidate work for readiness and dependencies, then fit the selected scope within actual capacity. Keep operational work and uncertainty visible rather than filling every available hour.
- What you provide
- Prioritized backlog, estimates and capacity.
- What you get
- Tentative sprint scope with dependency checks.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Sprint capacity 30 hours. Goal: review imports before committing changes. Ready stories: validation 12 hours, preview 10, review help 8, theme colors 8. All estimates include the team's stated delivery checks.
Completed example
Selected scope: - Validation: 12 hours - Preview: 10 hours - Review help: 8 hours Total: 30 hours, matching the supplied capacity. Deferred: theme colors, 8 hours. Rationale: the selected work supports the import-review goal. Confirm dependencies and any capacity not represented in the supplied estimate before commitment.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should the sprint include every high-priority backlog item?
Select the work that supports the goal and fits capacity. Priority does not remove dependency or availability constraints.
Why does a full sprint plan require unexpected overtime?
Check omitted support work, optimistic estimates and incomplete prerequisites. Reduce or resequence scope instead of assuming hidden capacity.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑