Sprint Planning Capacity Calculator and Sprint Goal Draft
Work out realistic sprint capacity and write a sprint goal the team can check.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Help me plan a sprint in Jira. Sprint length and dates: [SPRINT_DATES]. Team members with availability in days (holidays, part-time, support rota): [TEAM_AVAILABILITY]. Velocity or completed story points in the last three sprints: [VELOCITY_HISTORY]. Candidate issues with key, summary, estimate and dependencies: [CANDIDATE_ISSUES]. Calculate capacity: available person-days divided by the person-days of past sprints, multiplied by average velocity, showing the arithmetic and a range rather than a single number. Select a set of issues that fits, leaving about 15 percent for unplanned work, and list what is excluded and why. Flag issues that depend on another team or on an unfinished issue, and issues too large to finish inside the sprint. Write a sprint goal of one or two sentences describing the outcome, three tests that show it is met, and a short list of risks with owners. Produce a table of issues with Key, Estimate, Owner, Dependency, and Confidence. I will check Jira field names and board settings myself; mark any menu or setting references [VERIFY]. Do not invent issue keys.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.