What is the recommended focus factor for agile development teams?

Most high-performing agile engineering teams operate with a focus factor between 65% and 75% (typically 0.70). This accounts for daily standups, backlog refinement, sprint review, retrospectives, code reviews, architectural discussions, and unexpected production triage.

How does PTO and public holidays affect sprint capacity?

Every full day off reduces a developer's available hours by 8 gross hours (or 5.6 focus hours at a 70% focus factor). Deducting PTO individually before applying the focus factor prevents severe sprint overcommitment.

What is the recommended focus factor for agile development teams?

Most agile teams operate with a focus factor between 65% and 75% to account for ceremonies, code reviews, and unplanned interruptions.

🛡️ 100% Client-Side Privacy • Zero Backend Logs • YC & Scrum Alliance Aligned

Agile Sprint Capacity & Velocity Planner

Stop overcommitting in sprint planning. Model exact developer working days, individual PTO, public holidays, focus factors, and historical velocity to establish rock-solid sprint targets.

⚡ Quick Presets:

📅 1. Sprint Configuration

Baseline Cadence

Sprint Days (Workdays)

days

Default 10 days = 2 weeks

Standard Hours/Day

hrs

Contractual work hours

Team Public Holidays

days

Deducted from all members

🎯 Engineering Focus Factor: 75% Recommended (65-75%)

40% (Heavy overhead) 65% (Pragmatic default) 75% (Lean team) 90% (Zero meetings)

👥 2. Team Members & Individual Availability

Specify individual PTO and role-based allocations

Role / Name	Days Off (PTO)	Dedication	Net Focus Hrs	Action

📈 3. Historical Velocity & Calibration

Points Calibration

Sprint N-1 Points

Sprint N-2 Points

Sprint N-3 Points

Historical Average: 44.0 pts Historical Standard Deviation: ±2.0 pts Hours per Story Point: ~6.8 hrs/pt

Sprint Capacity Verdict Optimal Load

Recommended Commitment

42 pts

Equates to ~298.5 focused engineering hours

🛡️ Conservative (90%)

38 pts

High confidence

🎯 Target (80%)

42 pts

Committed goal

🚀 Stretch (50%)

47 pts

If smooth sailing

Total Gross Capacity (100%): 440.0 hrs

Holidays & PTO Lost: -42.0 hrs

Net Working Capacity: 398.0 hrs

Focus Factor (Scrum Ceremonies Drag): 75% (-99.5 hrs)

Total Available Focus Hours: 298.5 hrs

Compare Planned Backlog (Story Points in Sprint):

⚖️ Backlog matches 104% of recommended capacity. Healthy stretch.

Mastering Agile Sprint Capacity & Velocity Planning

1. Why Focus Factor Matters

No developer codes for 8 hours a day. Between standups, backlog refinement, architecture syncs, code reviews, and Slack interruptions, productive coding time is typically 65% to 75%. Assuming 100% capacity guarantees sprint spillover and burnout.

2. Deducting PTO Correctly

Always deduct personal leaves and public holidays *before* calculating focus hours. When team members take staggered leaves, capacity drops non-linearly due to dependency handoffs and reduced review throughput.

3. Velocity vs. Capacity

Velocity tells you what the team accomplished in the past under previous conditions. Capacity tells you how much bandwidth the team actually has in the upcoming sprint. Always scale historical velocity proportionally to capacity changes.

Frequently Asked Questions

Is Agile Sprint Capacity & Velocity Planner free to use?

Yes, Agile Sprint Capacity & Velocity Planner is completely free with no signup or registration required. All processing happens directly in your browser.

Is my data safe?

Absolutely. Your data never leaves your device. Everything runs locally in your browser — no uploads, no servers, no tracking.

Do I need to install anything?

No installation needed. Agile Sprint Capacity & Velocity Planner works entirely in your web browser on both desktop and mobile devices.

How do I use

Simply enter or paste your input in the tool above, and the result will be generated instantly. No configuration required.