A -day sprint starting , planning points per person, with % allocated for support.
Add your team to see what it can take on.
Who's in this sprint
Click a date to mark a team holiday. Click someone's day to mark them off.
This is a sample team so you can see how the planner works. Change anything to make it yours, or to start with your own team.
Bring in your sprint from Jira
Fill the planner from your Jira Cloud board in one click: the next sprint's dates, everyone with tickets in the current sprint, their unfinished points as carried over, and points per person from your last three sprints.
- Drag this button to your bookmarks bar: Send to Scrum Tools
- Open your team's board in Jira.
- Click Send to Scrum Tools in your bookmarks bar. The planner opens with your sprint filled in.
That button works from your bookmarks bar, not from here. Drag it up to your bookmarks bar, then click it while your Jira board is open.
It runs in your browser while you're signed in to Jira, so there are no passwords or tokens to share. Your sprint goes straight from Jira into this page in your browser, with no Scrum Tools server in between.
How the planner works
It starts from the points one person usually finishes in a full sprint, then scales that for the time each person actually has.
New here? to see what you can click and type in.
- Team holidays shrink the target. A 10-day sprint with 1 holiday has 9 working days, so a 13-point target becomes 13 × 9 ÷ 10 = 11.7 points.
- Days off scale each person. Someone off for 3 of those 9 days has 6 days in, so they get 6 ÷ 9 of 11.7, which is 7.8 points.
- Availability scales it again. If they're only on this team half the time, 50% availability turns 7.8 into 3.9.
- Support time comes off next. Set the percent allocated for support, then click the headset next to whoever's covering it. The time is split evenly, so 20% across two people takes 10% off each, and their availability drops by that much: 100% becomes 90%, and 80% becomes 70%.
- Carried-over work comes out first. With 4 points carried over from last sprint, a person with 7.8 points has room for 3.8 new points, shown as 4. If the carry-over is more than their capacity, they're flagged as over.
Capacity = points per person × (working days ÷ sprint days) × (days in ÷ working days) × availability (after support)
New points = capacity − carried over
Team total = everyone's new points + everyone's carried-over points
The "People in" row under the grid counts who's working each day, and turns red when half the team or more is out. That's usually the day to avoid scheduling a release or a big demo.
Questions people ask
What should I use for points per person?
Look at the last three sprints. Divide the points the team actually finished by the number of people, adjusting for anyone who was out. Use the average, not your best sprint.
Why does carried-over work count against capacity?
It's work the team has already committed to and still has to finish, so it uses up the same time as new work. Counting it keeps the plan honest about how much new work fits.
What does availability mean?
The share of someone's time that goes to this team's sprint work. Use 50% for someone split between two teams, or lower it for a lead who spends a lot of the day in meetings.
Does the sprint length include weekends?
No. Sprint length is in working days, and the dates skip Saturdays and Sundays.
Is my team's data stored anywhere?
Your plan is saved in your browser and in the share link. There are no accounts and we don't keep your plans. The share link is a normal web address, so it can show up in places like browser history. See the privacy policy for details.
How do I share the plan with my team?
Use "Copy share link" and paste it anywhere. Anyone who opens it sees the same plan. Changes they make stay on their side until they send you a new link.