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, laid on a quarter. 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. Pick the quarter under Calendar; quarters follow your fiscal year (with an October start, October to December 2026 is Q1 FY27).
A deliverable can take less than the whole plan. Click the sprints on a card (or drag its bar on the Map) to run it over, say, S1 to S2. A share is then a percentage of the person's time in those sprints. By default the estimate scales with the sprints (21 over four sprints is 13 over two) and each person keeps their share of their time; you can instead keep the estimate and each person's points, so fewer sprints ask for a bigger share of their time there. Someone on two deliverables in the same sprints can be over-booked in those sprints even when the quarter adds up; the flags say which.
Every deliverable has a landing date: the day its people's points add up to its estimate, counting only the days they work. Short of that, it keeps the same pace past its sprints (and past the plan, on the Map) and says so. The Map shows the whole quarter in two tables. In People, each row is that person's schedule: a vacation, a holiday or a team day off replaces the bar on its days, and each sprint shows the points they have there (drag across a row to add a vacation; on a phone, tap the first day, then the last). In Deliverables, each bar runs over its sprints (drag it, or an end) with a diamond where it lands.
One full-time engineer lands on the Fibonacci scale, the same scale the work is sized on: 32 becomes 34, and 48 becomes 55. Everyone else is their own capacity scaled by that same factor, so a vacation day or a load step moves them a little instead of jumping them from 34 to 21. Pick Fibonacci below for a safer plan (32 becomes 21). The raw number is always shown next to the planned one.
Load and sprints away scale one person: half-time on this team over four sprints is 16 raw, 17 planned. Buffer comes off after rounding and holds back a percentage of everyone's capacity for support and unplanned work: 10% of 34 leaves 31 bookable.
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 or only to one country's people when you limit them to it, 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 what someone has for this plan, after load, days off and buffer, and its points follow that capacity: 50% of an engineer planned at 34 is 17 points, and if a vacation brings them to 30 it becomes 15 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; someone already fully booked still gets one sprint's worth, and the over-booking flag says so. Click the number on a share to set a percentage, or a number of points kept as the matching percentage; the pencil on their row shows and edits their whole split.
Plans, Later and Done. Every plan lives in this browser under Plans: a share link, an import or the example opens as a plan of its own, so nothing replaces yours. A deliverable you move to Later (a future plan) or Done (shipped) keeps its people but stops counting; move it back and its shares return as they were. Wipe empties the open plan, and Ctrl+Z brings it back.
Keys
- Enter on a person or a share picks it up; Enter on a deliverable drops it there; Esc puts it back
- Ctrl Z undo, Ctrl Shift Z redo