HKSM

A Team Calendar is a shared schedule of sprint dates, team availability, and Scrum events used to plan realistic capacity and coordinate work. It is created in sprint planning and kept current throughout the sprint, serving as an input to estimating, committing user stories, and daily coordination.

Key Points

• Shared, visible schedule of sprint timebox, events, and member availability.
• Created and baseline during sprint planning; updated anytime availability changes.
• Input to Approve, Estimate, and Commit User Stories and Estimate Tasks in SBOK.
• Helps right-size the Sprint Backlog based on capacity, not wishful scope.
• Supports distributed teams with time zones and core collaboration hours.
• Links to Scrumboard and burndown tracking for day-to-day coordination.

Purpose

The Team Calendar exists to make capacity transparent so the team can commit realistically and plan handoffs. It also anchors the timing of Scrum events and stakeholder interactions such as sprint reviews and backlog refinement.

By exposing non-working days, personal leave, and training, it reduces scheduling risk and helps the Product Owner and Scrum Master coordinate dependencies and participation.

Key Terms & Clauses

• Capacity: The effective, available hours or days the team can spend on sprint work.
• Focus factor: A realistic percentage of time available for planned work after meetings and interrupts.
• Core hours: Daily time window when distributed members overlap for collaboration.
• Non-working time: Holidays, weekends, leave, and training that reduce capacity.
• Scrum events: Sprint Planning, Daily Standup, Sprint Review, and Retrospective placed on the calendar.
• Working agreements: Team rules for availability, response times, and update cadence for the calendar.

How to Develop/Evaluate

Develop:

• Set sprint start and end dates and mark public holidays and weekends.
• Collect each member's planned leave, training, and part-time allocations.
• Add recurring Scrum events and backlog refinement sessions.
• Define core collaboration hours and time zone overlaps if distributed.
• Calculate team capacity using focus factor and note it on the calendar.
• Publish in a shared tool and baseline during sprint planning.

Evaluate quality:

• Accurate: Reflects up-to-date availability and organization holidays.
• Complete: Includes all Scrum events and relevant stakeholder sessions.
• Visible: Easy access for the whole Scrum Team and key stakeholders.
• Actionable: Capacity totals are clear and used to guide commitment.
• Consistent: Matches Sprint Backlog scope and release planning schedules.

How to Use

• Before Sprint Planning: Review capacity and highlight constraints to inform story selection.
• During Planning: Use capacity to commit user stories and break into tasks that fit the timebox.
• During the Sprint: Reference in Daily Standup to plan handoffs and adjust to availability changes.
• For Events: Schedule Sprint Review, Retrospective, and backlog refinement when the team can attend.
• Across Processes: Input to Approve, Estimate, and Commit User Stories; Estimate Tasks; Create Sprint Backlog; and a reference for Conduct Daily Standup.

Example Snippet

Two-week sprint example:

• Sprint: Mon 3 Jun - Fri 14 Jun (10 working days, holiday on Wed 5 Jun).
• Availability: Asha PTO 2 days; Luis training Fri 7 Jun; Priya 50% on support.
• Core hours: 13:00-16:00 UTC for cross-time-zone collaboration.
• Events: Daily Standup 13:15 UTC; Review Thu 13 Jun; Retrospective Fri 14 Jun.
• Calculated capacity: 250 person-hours after focus factor applied.

Risks & Tips

• Risk: Outdated calendar leads to over-commitment and missed sprint goals.
• Risk: Ignoring time zones creates coordination gaps and delays.
• Risk: Hidden stakeholder events conflict with reviews and demos.
• Tip: Make one source of truth and link it from the Scrumboard.
• Tip: Review and update in each Daily Standup if availability changed.
• Tip: Capture lessons in the Retrospective and adjust working agreements.

PMP/SCRUM Example Question

During Sprint Planning, the team notices a mid-sprint public holiday and two planned leaves. What should the Scrum Master encourage to ensure a realistic commitment?

1. Add a 20 percent buffer to all task estimates and proceed.
2. Extend the sprint by two days to offset the holiday.
3. Update the Team Calendar and recalculate capacity before finalizing the Sprint Backlog.
4. Keep the original scope and plan to work overtime if needed.

Correct Answer: C — Update the Team Calendar and recalculate capacity before finalizing the Sprint Backlog.

Explanation: The Team Calendar is an input to estimating and committing user stories. Adjusting capacity using the updated calendar leads to a realistic, sustainable commitment without changing the sprint timebox.