Formula
Capacity = (Team Size Γ Days Γ Hours/Day - Overhead) Γ Focus Factor
Sprint capacity is total available hours minus overhead (meetings, support, admin), multiplied by focus factor to account for productivity variations.
Worked Examples
Example 1: Standard 2-Week Sprint
Problem: Team of 6, 10-day sprint, 6 productive hrs/day, 15% meetings, 10% support, 5% admin, 75% focus.
Solution: Total hours: 6 Γ 10 Γ 6 = 360 hours\n\nOverhead:\nMeetings: 360 Γ 15% = 54 hours\nSupport: 360 Γ 10% = 36 hours\nAdmin: 360 Γ 5% = 18 hours\n\nPlanned work: 360 - 54 - 36 - 18 = 252 hours\nCapacity (75% focus): 252 Γ 0.75 = 189 hours\n\nAt 0.5 points/hour: 189 Γ 0.5 = 95 story points\nPer person: 95 / 6 = 16 points
Result: 189 hours capacity | 95 story points | 16 pts/person
Example 2: Startup Sprint (High Velocity)
Problem: 3-person team, 10 days, 7 hrs/day, 10% meetings, 15% support, 3% admin, 80% focus.
Solution: Total: 3 Γ 10 Γ 7 = 210 hours\n\nOverhead:\nMeetings: 21 hours (lean)\nSupport: 31.5 hours\nAdmin: 6.3 hours\n\nPlanned: 210 - 58.8 = 151.2 hours\nCapacity (80%): 151.2 Γ 0.8 = 121 hours\n\nPoints (0.6 pt/hr, smaller team): 73 points\nPer person: 24 points\n\nNote: High per-person load - monitor burnout
Result: 121 hours | 73 points | 24 pts/person (high load)
Example 3: Enterprise Team (High Overhead)
Problem: 8-person team, 10 days, 6 hrs/day, 25% meetings, 20% support, 10% admin, 70% focus.
Solution: Total: 8 Γ 10 Γ 6 = 480 hours\n\nOverhead:\nMeetings: 120 hours (high - multiple standups, planning)\nSupport: 96 hours (legacy system)\nAdmin: 48 hours\n\nPlanned: 480 - 264 = 216 hours\nCapacity (70%): 216 Γ 0.7 = 151 hours\n\nPoints: 151 Γ 0.5 = 76 points\nPer person: 9.5 points\n\nLow per-person despite large team - overhead dominates
Result: 151 hours | 76 points | 9.5 pts/person | Reduce overhead
Frequently Asked Questions
What is sprint capacity planning?
Sprint capacity planning calculates available development hours for a sprint by subtracting meetings, support work, and other overhead from total available time, then applying a focus factor for realistic estimation.
How many story points can a team complete per sprint?
Velocity varies by team, definition, and complexity. Typical: 0.3-0.7 points per person-hour. A 5-person team with 150 capacity hours might complete 50-100 points. Use historical data to establish baseline.
How do I account for support work in capacity?
Reserve 10-20% for bug fixes, customer issues, and unplanned work. High-traffic products may need 20-30%. Consider dedicated support rotation to protect sprint work.
What's the difference between capacity and velocity?
Capacity is planned available hours/points for upcoming sprint. Velocity is actual points completed in past sprints. Use historical velocity to validate capacity planning and improve accuracy.
How does team size affect capacity?
Capacity doesn't scale linearly. Communication overhead grows with team size. 5-7 people is optimal for scrum teams. Larger teams should split into multiple squads.
Should I plan to 100% capacity?
No. Plan to 70-85% of capacity. Buffer allows for: unplanned urgent work, underestimated stories, team member illness/PTO, and reduces stress. Consistently hitting 100% indicates planning issues.
Background & Theory
The Dev Team Capacity Sprint Planner applies the following established principles and formulas.
Structural and construction engineering is governed by fundamental load analysis, material science, and regulatory standards that ensure the safety and durability of built structures. The primary distinction in load analysis is between dead loads β the permanent self-weight of structural elements, finishes, and fixed equipment β and live loads, which represent variable occupancy, furniture, and environmental forces such as wind and snow. These are combined using factored load equations, such as the ASCE 7 formula U = 1.2D + 1.6L, where D is dead load and L is live load. Concrete mix design is governed by the water-cement (w/c) ratio, which is the primary determinant of compressive strength and durability. A w/c ratio of 0.40β0.45 typically yields concrete with 28-day compressive strengths of 30β40 MPa. Common mix ratios by weight for structural concrete are approximately 1 part cement : 1.5β2 parts sand : 3 parts coarse aggregate. Structural steel is characterized by its yield strength (the stress at which permanent deformation begins, typically 250β350 MPa for mild steel) and ultimate tensile strength (typically 400β500 MPa). Mid-span deflection of a simply supported beam under a central point load is given by Ξ΄ = FLΒ³ / (48EI), where F is force, L is span length, E is Young's modulus, and I is the second moment of area. Building insulation is rated by R-value, a measure of thermal resistance in units of mΒ²Β·K/W (SI) or ftΒ²Β·Β°FΒ·h/BTU (imperial). Higher R-values indicate greater resistance to heat flow. Foundation design depends on the allowable bearing capacity of the underlying soil, which ranges from approximately 75 kPa for soft clay to over 10,000 kPa for bedrock. Drainage gradients for surface water are typically specified as a minimum of 1β2% slope away from building foundations to prevent hydrostatic pressure and water infiltration.
History
The history behind the Dev Team Capacity Sprint Planner traces back through the following developments.
The history of construction engineering spans thousands of years of accumulated empirical knowledge and, more recently, rigorous scientific analysis. The ancient Egyptians built the Great Pyramid of Giza around 2560 BCE using an estimated 2.3 million stone blocks, demonstrating sophisticated logistics, geometry, and workforce organization. Roman engineers advanced the field dramatically through the use of pozzolanic concrete β a mixture of volcanic ash, lime, and seawater β enabling the construction of the Pantheon dome (43.3 m diameter, completed around 125 CE) and a vast network of aqueducts and roads across the empire. Cast iron emerged as a structural material during the Industrial Revolution, first used prominently in the Iron Bridge at Coalbrookdale, England, completed in 1779. Wrought iron and later steel allowed far greater spans and heights. The Eiffel Tower, completed in 1889, demonstrated the structural possibilities of wrought iron at scale and influenced the development of steel-frame skyscraper construction in Chicago and New York. Reinforced concrete was systematically developed by Joseph Monier, a French gardener, who patented iron-reinforced concrete pots and panels in the 1860s, and later by engineers including FranΓ§ois Hennebique who created the first comprehensive reinforced concrete framing system in the 1890s. The 1906 San Francisco earthquake caused widespread devastation and galvanized the engineering profession to develop seismic design provisions. Subsequent earthquakes β including the 1971 San Fernando and 1994 Northridge events β drove successive improvements in seismic codes, base isolation technology, and ductile detailing of reinforced concrete and steel frames. Building codes became increasingly standardized in the twentieth century, with the International Building Code (IBC) first published in 2000 providing a unified model code adopted across much of the United States. Building Information Modeling (BIM) emerged in the 2000s as a digital workflow integrating architectural, structural, and MEP design into a unified three-dimensional model, fundamentally changing coordination practices across the industry.