Sprints and capacity

A sprint is a dated window with a name and a goal. It collects work from any project, which is what makes it usable by a team serving several clients at once. It can be associated with a team, or belong to the organisation as a whole.

Lifecycle

Capacity

This is the payoff of having HR in the same database. For each person in the sprint:

  scheduled working minutes in the sprint window
     (from their working pattern, minus public holidays)
  ×  their FTE
  −  approved leave falling inside the window
  −  any reserved overhead the team has agreed

• FTE is applied per day, not to the total. Prorating only the total would let somebody at 0.6 FTE lose a full eight-hour day of capacity to one day of leave when they only had 4.8 hours that day — the absence would remove more capacity than existed.
• A leave day is capped at what that person was scheduled to work. Otherwise a calendar-day absence spanning a weekend removes capacity nobody had.
• Holidays are resolved per person. A team split across a Georgian and a UAE entity does not share public holidays, and applying one set to everybody makes the number wrong for half of them.
• Reserved overhead is a first-class input, expressed as a percentage. Teams that skip it and then miss every sprint are the norm, so it is a field rather than a haircut somebody applies in their head.
• A manual override wins over the whole calculation. There are always commitments the system cannot see, and an override is honestly labelled as one rather than disguised as a computed figure.

Provisional numbers

Where an unconfirmed public holiday moved somebody's number — a date announced by decree that has not landed yet — the capacity figure is marked provisional and carries a marker rather than being presented as settled. See Holiday calendars.