Skip to content

Prepare sprint planning briefs with realistic PTO capacity, carryover, and bug load

Teams chronically overcommit on Monday morning because nobody subtracted PTO days, on-call interrupt tax, and 18 points of silent carryover from last sprint. Walk into planning with honest math.

Copy the prompt and paste it into the AI assistant you already use.

Making sprint commitments predictable enough that GTM trusts roadmap dates

  1. 01

    Calculate real maker days available for the upcoming window

    Cross-reference team PTO calendars, regional bank holidays, heavy interview schedules, and on-call bug rotations against historical 3-sprint velocity.

  2. 02

    Audit closing-sprint carryover honestly

    Distinguish tickets that are 90% done in final code review from chronic multi-sprint 'zombie' tickets carried over three times in a row.

  3. 03

    Verify spec and design readiness on candidate stories

    Check candidate top-of-backlog issues for missing Figma links, unresolved open questions, or external dependencies that would stall mid-week.

  4. 04

    Post a 1-page pre-planning brief 2 hours ahead

    Give the PM and Eng Lead a clear Recommended Point Budget, Carryover Summary, and Ready Candidate Queue so Monday planning wraps in 30 minutes.

Answers to your questions

Is velocity tracking used to stack-rank or police individual developers?

Never—capacity math runs at the squad level strictly to protect makers from unrealistic overcommitment and weekend crunch.

How does it account for unpredictable urgent support bugs during the sprint?

It calculates your trailing 4-sprint 'interrupt tax' (e.g., 18% of capacity goes to unplanned bugs/ops) and reserves that buffer upfront.

Does this work for Kanban or Shape Up 6-week cycle teams as well as 2-week Scrum?

Yes. Shape Up cooldown checks and weekly Kanban WIP/throughput audits work just as cleanly using the same calendar + tracker signals.

Learn more

Related guides and background articles for this task