Sprint planning that knows who is on leave.

Approved leave comes out of sprint capacity automatically, so the plan matches the team you really have. Standups and retros find their meetings on the calendar by themselves, and what you learn stays with the sprint.

Design sprintTeam capacity22 of 28 pointsCommit issues
Leave3 days outno reminder
Capacity22 pointsnot guessed
Velocity21 trailingno spreadsheet
Scope+6 after startnot hidden
No integration. One database.
One sprintCapacity that already knew Priya was away

Three days of approved annual leave came out of the sprint on their own. The leave ledger belongs to People and the sprint belongs to Projects, and one reads the other because they are one database.

The plan tab

Commit work against real capacity.

The sprint goal sits at the top with its status. The backlog and the committed list are side by side so you can move work between them. On the right, capacity per person with leave already deducted, and the four numbers that tell you whether the sprint was realistic.

NearSyncProjectsSprintsSearch, plan and askKAll hubs
All activeManage sprints
DesignDesign-system language for widgets, charts and tables, applied across Analytics.On track
Backlog2 ready
ENG-11371Org-scope canva-oauth refresh2Commit
ENG-11372Clean up dead edge-function imports1Commit
Committed to sprint4 issues24 points
ENG-11370Add a toggle for manifest feature flagsAR3Remove
ENG-11369Type the client and resync database typesMG5Remove
ENG-11361Ship the Service triage cockpit and SLA enginePN8Remove
ENG-11359Build the shared Account 360 spineAR8Remove

Leave approved in People is already out of the sprint.

Capacity

Approved leave comes out of capacity by itself.

There is nothing to connect. Leave is approved in NearSync, so the sprint already knows about it.

  • Deduct approved leave from capacity automatically
  • See capacity per person, and for the team
  • Compare committed points against team capacity
  • See velocity from the last few sprints while you plan
  • See scope added mid-sprint counted on its own
CapacityLeave-aware
Aisha8 of 10
Micheal5 of 8
Priya, on leave4 of 10
Team this sprint22 points
Where that came from
Leave requestApproved
Owned byPeople
Read byThe sprint
No integration involvedthe leave ledger and the sprint are one database
Ceremonies

Standups and retros find their own meetings.

Each one is matched to its calendar meeting, and action items appear once the retro records measured outcomes.

  • Have each standup and retro matched from the calendar automatically
  • Open a standup with what changed since the last one
  • Log what the sprint taught you, and keep it with the sprint
  • Link a meeting by hand when it was not on the calendar
  • Follow an epic's progress across every sprint it runs through
RetroMatched
MeetingFound on the calendar
NotesAlready taken
LearningsLogged to the sprint
Action itemsFrom measured outcomes
Since last standup
What movedListed
Who says itThe board
NotEveryone in turn
Or link one yourselfif the meeting was not on the calendar
Warnings

Six warnings that tell you a sprint is in trouble.

Someone committed to more than they can finish. Work is blocked. You promised more than the team has managed in recent sprints. Each warning appears on the planning screen with a suggestion for what to do about it.

This sprint
2 over capacityRebalance
3 blockedClear or reassign
Above recent paceTrim scope
Every warning comes with a suggestion
Closing a sprint

It works out what to do with the work you did not finish.

As a sprint winds down you get a short list of suggested actions: move the unfinished points into the next sprint, chase issues that have been blocked for days, escalate bugs that have been open since before the sprint started, book the retro.

Needs your call
Carry 8 points forward4 issues
Nudge stalled work2 blocked
Escalate old bugs1 bug
Suggested, never done for you
The written summary

A plain-English summary of the sprint, and it is not AI.

Every sprint gets a short written summary of where it stands. It is built from your own numbers rather than generated, so it says the same thing every time you open it and it can never be wrong about a figure.

Sprint 12, day 6
Built fromYour own numbers
Generated by a modelNo
Says the same twiceAlways
Nothing in it is invented

Access

Who can do what.

Everybody on the team moves their own work and can log what they learned. Planning the sprint, naming a scrum master and closing it belong to whoever runs delivery.

See

See the sprint, its capacity and its velocity.

Do

Commit work, move issues, log a learning.

Manage

Plan sprints, set the goal, name a scrum master.

Admin

Run parallel sprints and close them.

Admin is the highest role and is not constrained by the permission grid, so it is worth keeping to the smallest group that genuinely needs it.

One sprint, start to finish

Leave approved in March, already in the plan.

Nobody had to copy that leave into the sprint tool, because there is no second tool. The sprint was planned against 22 points instead of 28, the six points added mid-sprint were counted on their own, and the retro matched its own meeting on the calendar.

Approved in People, weeks before anybody thought about the sprint.

Related guides

See Projects on your own data.

Half an hour on your own sprint, with the backlog and the roadmap reading the same board.