One engineer's capacity
Calendar
Public holidays: the team's countries
The spreadsheet holds every table on its own sheet, plus a Settings sheet with the numbers behind them. CSV and the copy buttons take the table shown above.
A story point is one focus day. A week has five working days; with the meeting day on, one of them goes to ceremonies and does not count, so a week holds four points and a two-week sprint holds eight.
A plan is a number of sprints. A quarter holds six two-week sprints; when two months of it go to planned work, the plan is four. One engineer's plan is points a sprint times sprints: 8 × 4 = 32.
Capacity lands on the Fibonacci scale, the same scale the work is sized on, so 32 becomes 34 and 48 becomes 55. Pick Fibonacci below for a safer plan, where 32 becomes 21. The raw number is always shown next to the rounded one.
Load and sprints away scale one person: half-time on this team over four sprints is 16 raw, 13 planned. Buffer holds back a percentage of everyone's capacity for support and unplanned work.
The calendar takes days out. Sprints start on the date you pick. Public holidays come from the country you choose for the team (anyone can have their own), team days off apply to everyone, and vacations belong to one person. A day off only costs a focus day when it lands on a working day, and a week someone spends entirely away costs no meeting day either.
A share is a percentage of someone's time, and its points follow their capacity: 50% of an engineer planned at 34 is 17 points, and if a vacation brings them to 21 it becomes 10 without anyone touching it. A person can hold shares on as many deliverables as you like, and a deliverable can have as many people. Dropping someone on a card gives it what they have free, up to what it still needs. Click the number on a share to set a percentage (or exact points), or open the pencil on their row to see and edit their whole split at once.