Absence and Leave Adjustment

Absence and Leave Adjustment is the process of modifying a team's raw capacity figures to account for planned and unplanned time away from work, including vacation, sick leave, public holidays, parental leave, jury duty, bereavement leave, and other approved absences. It ensures that sprint commitments reflect the real number of working days each team member will actually be present and productive, rather than the full calendar length of the iteration.

Core Concept

Why Absence Must Be Adjusted For

An iteration nominally spans a fixed number of working days, but individual team members rarely work every one of those days without exception. If a two-week sprint contains ten working days and a team member is on vacation for three of them, that person contributes capacity for only seven days, not ten. Failing to adjust for this discrepancy is one of the most common and avoidable causes of sprint overcommitment.

Where $A_i$ is the adjusted available days for team member $i$, $D_i$ is the nominal working days in the iteration, $V_i$ is planned vacation days, $H_i$ is public holidays falling within the iteration, and $S_i$ is an estimated reserve for unplanned sick leave.

Categories of Absence

Planned Leave

Planned leave, such as scheduled vacation, training courses, or approved personal days, is known in advance and can be subtracted from capacity with certainty before sprint planning begins.

Public and Company Holidays

Holidays that fall within an iteration reduce the working days available to the entire team simultaneously, rather than to individual members separately, and are typically subtracted from the iteration's total working-day count before any individual calculations occur.

Unplanned Absence

Unplanned absence, including illness or emergencies, cannot be known precisely in advance, so teams typically apply a statistical buffer based on historical absence rates rather than attempting to predict specific days.

Partial-Day Absence

Not all absence is full-day; medical appointments, childcare obligations, or partial remote-work limitations can reduce a person's availability for only part of a working day, and precise capacity models track these as fractional day deductions rather than rounding them away.

Applying Adjustments to Sprint Planning

Recalculating Individual Availability

Before each sprint, every team member's availability is recalculated based on known leave requests and remaining holidays, producing an updated capacity figure rather than relying on a static assumption carried over from the previous iteration.

Aggregating to Team Capacity

Individual adjusted availabilities are summed to produce the team's total adjusted capacity for the sprint, which then feeds into the broader effective capacity calculation alongside focus factor and other overhead deductions.

Flagging High-Impact Absences

Absences affecting team members with rare or specialized skills warrant particular attention during planning, since their absence may reduce capacity in a specific skill category disproportionately, even if the team's aggregate day count looks only modestly reduced.

Tools and Techniques

Shared Leave Calendars

Maintaining a shared, visible calendar of planned absences across the team allows sprint planning to account for known leave before commitments are finalized, rather than discovering conflicts mid-sprint.

Rolling Historical Absence Rates

Teams often track their own historical rate of unplanned absence over several iterations and use that rate as a standing adjustment factor applied automatically during future capacity calculations.

Automated Capacity Calculators

Many Agile planning tools allow team members to log planned time off directly against the sprint calendar, automatically recalculating team capacity totals as leave is entered or updated.

Consequences of Skipping Leave Adjustment

Sprint Goal Failure

Sprints planned without leave adjustment routinely fail to meet their goals, since the gap between assumed and actual availability directly translates into unfinished work.

Uneven Workload Distribution

When leave is not accounted for at the planning stage, remaining team members often absorb the shortfall informally, leading to uneven workload distribution and potential burnout among those who did not take leave.

Erosion of Planning Credibility

Repeated failure to account for known absences damages the credibility of the planning process itself, making stakeholders less willing to trust sprint forecasts even when future adjustments are made correctly.

Best Practices

Require Leave Requests Before Planning Cutoff

Establishing a deadline for submitting leave requests before sprint planning ensures the team has the most accurate picture of availability when commitments are made.

Separate Known Leave From Unplanned Buffer

Modeling known leave and unplanned absence buffer as distinct components, rather than a single blended discount, produces more transparent and adjustable capacity calculations.

Review Absence Patterns Periodically

Periodically reviewing actual absence rates against planned buffers helps refine the buffer over time, improving the accuracy of future capacity forecasts.