Plan sprint capacity from real retro evidence.

The basic workflow

1. Create a plan. Name the upcoming sprint, set dates, working days, and the default focus factor. The default 0.75 focus factor leaves room for meetings, reviews, support, and unplanned work.
2. Add team availability. Add each person with working days, availability percentage, planned leave, and optional personal focus overrides.
3. Import candidate work. Bring in unresolved retro actions, FreeScrumPoker stories, or Jira snapshot issues. Imports are snapshots, so nothing silently changes after you review it.
4. Choose what to include. Exclude work that should wait, watch the remaining capacity card, and balance load by owner.
5. Send to FreeScrumPoker. When the plan is ready, create or open a linked FreeScrumPoker planning room with the included items as estimate-ready stories.

Examples

Carryover-heavy sprint

If a retro produced five action items, import them first. Include the two that unblock delivery, assign owners, and see how much capacity remains before adding new feature work.

Jira sprint rollover

Import the latest Jira snapshot, exclude completed work, and keep spillover or blockers visible so the next sprint starts with the full cost of unfinished work.

Planning handoff

Once the capacity plan looks realistic, send included items to FreeScrumPoker. The team can estimate them without copying notes or losing the retrospective context.