Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Repeated story carryover does not automatically mean Developers estimated badly or failed to work hard enough. A common first check is whether the Sprint forecast counted the team’s nominal days while overlooking leave, shared assignments, Scrum events, refinement, support work, verification, or changing scope. Calculate the time people can actually devote to the team, then compare that capacity with recent completed work and choose a forecast that supports a coherent Sprint Goal.
Scrum does not prescribe a capacity formula, a fixed focus factor, or a required buffer. Its guidance is to consider past performance, upcoming capacity, and the Definition of Done when forecasting. The method below makes those inputs visible without turning hours into a quota.
What does “capacity” mean in a Sprint?
Sprint capacity is a planning estimate of the time the people on a Scrum Team can devote to the upcoming work. It is not the same as headcount multiplied by working days multiplied by eight hours. A person may be on leave, allocated to another team, attending meetings, or handling operational work during the Sprint; those demands reduce the time available for the forecast.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallIn Scrum, “Developers” means the people on the Scrum Team who do the work needed to create a usable Increment. It is not limited to people with the job title “developer” or to writing code. Testing, design, analysis, integration, and other work needed to meet the Definition of Done can affect the same forecast.
Popular on Amazon
- 【90 Degree Full Function USB C Adapter】Supports the latest USB4 standard for up to 40Gbps of bandwidth, 8K video support, and up to 240W Fast charging; Support USB PD 3.1 Extended Power Range (EPR) including 140W, 180W and 240W. Your productivity is easily doubled. *Warm Tip: For the best fit, please make sure the USB-C port is fully exposed; thick or bulky cases may affect compatibility.
- 【Reliable Quality】Made from high-quality, scratch-resistant aluminum alloy, delicate metal frame. get excellent wear resistance and heat dissipation. Non-Slip Design for easier insertion and removal.
- 【Small and portable】Ultra thin size, ultra compact design, a petite physique that matches the minimalist design of your modern laptops. Coming with a slim figure that won't block the port next to the one it's plugged into.
- 【Compatibility】Widely work with most usb c, thunderbolt 4/3 devices. Compatibilit for ROG Ally, Steam Deck, Switch, MacBook Pro, Quest 3 VR headset, Surface Book 2, iPhone 18/17/16/15, Samsung Galaxy S23/S22/S21, Note 20/10, Google Pixel, ChromeBook, etc.
- 【Excellence Customer Support】If you experience any issues or cable failure, simply reach out to our dedicated customer service team. We provide a prompt response within 18 hours, providing you with the necessary technical support to resolve any concerns.
Capacity is an input to a forecast, not a promise about a person’s output. The November 2020 Scrum Guide says Developers use past performance, upcoming capacity, and the Definition of Done to make a forecast. It does not mandate converting hours into story points or applying a particular percentage.
Why do we keep carrying stories over?
Carryover is a signal to inspect what happened, not a verdict on effort or estimating skill. Start by asking whether the original forecast was realistic given availability, then examine what changed during the Sprint and whether selected work met the team’s Definition of Done.
- Availability was overstated. The plan may have counted all working days and nominal hours without accounting for leave, public holidays, part-time allocation, or recurring work outside the backlog forecast.
- Work was not ready enough to forecast. Hidden dependencies, uncertain acceptance conditions, or differing assumptions about testing, migration, and integration can make an item larger or riskier than the discussion suggested.
- Scope changed. New work may have been added or existing work expanded after the Sprint began. Record that change rather than attributing the entire miss to the original estimate.
- Impediments or interruptions consumed time. Incidents, waiting on another team, production support, and unexpected review work can reduce delivery time even when the initial plan was reasonable.
- “Done” was treated too loosely. Coding may be complete while required testing, review, documentation, integration, or other Definition of Done work remains. Work that is not Done is not completed work for forecasting purposes.
- The selected work did not serve one feasible goal. A large or scattered selection can create switching costs and make it harder to finish a useful outcome, even if each item sounded manageable alone.
The Sprint Goal and the selected backlog items are related but not identical. The Guide calls the Sprint Goal “the single objective for the Sprint.” Developers commit to the goal while selecting and planning the work; as learning occurs, scope can be clarified and negotiated with the Product Owner without endangering that goal. An unfinished selected item deserves inspection, but it does not by itself prove that the Sprint Goal failed.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
How do you calculate Sprint capacity with PTO and meetings?
Calculate availability person by person, using only the time each person is actually allocated to this team. Then account for known work demands once, and leave an evidence-informed allowance for uncertainty if the team chooses to use one.
- Set the Sprint’s working days. Use the team’s calendar, not an assumed universal two-week or ten-day calendar. Note local holidays and nonworking days.
- Record each person’s actual team allocation. For example, someone allocated half-time to the team does not contribute a full-time week to its forecast. A person shared across teams counts only for the time genuinely available here.
- Subtract known absences. Include vacation, personal leave, training, or other known periods away. A day off for one person is not a day off for the whole team.
- Account for time spent in events and refinement. Use the time the team expects to spend, not automatically the maximum Scrum timebox. A two-hour session attended by four Developers consumes eight person-hours in total.
- Include separate support and review work. Account for operational support, code review, or other work only when it is not already represented in the backlog work being forecast or in a measured focus-hours figure.
- Apply a team-chosen uncertainty allowance, if useful. Calibrate it against what actually happened in prior Sprints. Do not subtract the same demand twice or stack percentages that cover overlapping risks.
- Compare the result with completed work. Use the calculation to make constraints visible, then check whether recent completed items or points suggest the proposed forecast is plausible.
A practical worksheet for each person is: working days × hours per day allocated to this team − known absences − event/refinement time − separate support or review time. Sum the people’s remaining time. This is a planning aid, not a Scrum-required formula.
Also popular on Amazon
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
There are two sensible starting approaches. One is to begin with nominal time and subtract known demands. Another is to begin with empirically observed focus hours per day. If using focus hours, first document what that figure already excludes; otherwise, subtracting meetings or support again will understate availability. Likewise, do not deduct review time separately if it is already included in the estimates for the forecast work.
What does a capacity calculation look like?
The following arithmetic is deliberately hypothetical. It illustrates how deductions work; it is not research data, an industry benchmark, or a recommended capacity target.
| Illustrative item | Hours | Running total |
|---|---|---|
| Four Developers × 10 working days × 8 nominal hours | 320 | 320 |
| One 8-hour holiday for each of four Developers | −32 | 288 |
| Two leave days for one Developer | −16 | 272 |
| Eight hours of scheduled Scrum events per Developer, after absences | −32 | 240 |
| Two hours of refinement per Developer | −8 | 232 |
| Other specifically scheduled support work | −24 | 208 |
| Illustrative 15% uncertainty allowance | −31.2 | 176.8 |
In this invented example, the forecast starts from 320 nominal person-hours and reaches 208 after listed known demands, then 176.8 after a separately applied uncertainty allowance. Replace every input with the team’s own calendar and experience. If the event hours, support, or review are already included in a focus-hours assumption or item estimates, do not deduct them again.
A separate worked scenario in a September 30, 2026 article by Scrum.org contributor Sanjay Saini starts with 300 assumed hours for five Developers in a two-week Sprint and arrives at about 182 hours after known demands—roughly 61% of the initial assumption. That is the author’s illustration, not an observed industry failure rate or representative study. Its value is the reminder to expose assumptions, not to copy its percentage as a rule. See Saini’s capacity-planning example.
How much time does a Developer actually have in a two-week Sprint?
There is no reliable universal number: a two-week Sprint can contain different holidays, leave, allocations, event schedules, and support demands. Ten working days at eight hours produces 80 nominal hours per full-time person only when that calendar and workday assumption applies; it does not mean 80 hours are available for planned backlog work.
Also popular on Amazon
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Scrum event timeboxes help explain why calendar time is not all delivery time, but they are maximums, not mandatory meeting bookings. In the 2020 Guide, a one-month Sprint’s maximums are 15 minutes for the Daily Scrum, eight hours for Sprint Planning, four hours for Sprint Review, and three hours for Sprint Retrospective. The Guide says shorter Sprints usually have shorter events. Teams should use their actual schedule and attendance rather than deducting every maximum by default. Refinement is ongoing work, too, but it is not one of the formal Scrum events with a prescribed timebox.
Recommended Free Tools
For example, if someone is on the team for only three of five days each week, count that actual allocation. If a team-wide meeting lasts two hours and four Developers attend, count eight person-hours of attendance, not two. If one Developer is absent, account for that individual’s time rather than reducing everyone’s availability.
What focus factor should I use?
There is no official Scrum focus factor. Scrum Alliance gives 0.6–0.8 as common examples in its capacity-planning guidance, while Atlassian suggests a 10% commitment buffer in its planning advice. These are suggestions, not measured guarantees or laws.
A focus factor can be useful if the team has a clear, consistent definition of what it represents. For instance, a team might use it to reflect ordinary interruptions not otherwise listed in the calendar. But multiplying already reduced availability by a focus factor that also accounts for the same meetings and interruptions double-counts the loss. The same problem arises when a buffer and focus factor overlap.
Choose an allowance by looking at the team’s actual history: what work was not visible at planning, what kind of uncertainty recurs, and whether the allowance helped produce a more credible forecast. Review it after the Sprint. If it is consistently too small or too large, adjust the assumption rather than treating the number as a permanent rule.
Also popular on Amazon
- Portable and powerful USB-C HUB: BENFEI USB Type-C HUB, with super-soft and knot-free silicone woven design cable, meets most mobile office needs. Compact, lightweight, stylish, and powerful portable USB C Hub equipped with 1 x HDMI port, 1 x 100W charging, and 3 x USB ports. 18-month warranty, 24-hour response, to ensure you feel at ease when using our product.
- Design centered on comfort and reliability: Thanks to BENFEI's end-to-end in-house cable production capability, in-house PCBA and assembly capability, using the industry's most advanced silicone woven design and process, 20cm cable in length, no knots, super-soft, the HUB is easy to use in all scenarios: laptop, tablet, stand etc. Super-soft, 25000+ life cycles, to meet your daily carrying and office needs.
- 100W Charging: Support up to 90W USB C pass-through charging via Type-C port to keep your laptop powered. 10W is reserved for other interface operations. No data and video function on the Type-C port.
- 4K HDMI Display: The HDMI port supports media display at resolutions up to 4K 30Hz, keeping every incredible moment detailed and ultra vivid. Please note that the C port of the Host device needs to support video output.
- Transfer Files in Seconds: Transfer files and from your laptop at speeds up to 10 Gbps with USB A 3.2 port. Extra 2 USB A 2.0 ports are perfectly for your keyboards and mouse.
Do story points equal Developer hours?
No. Hours describe a time constraint; story points represent a team’s relative estimate of work, complexity, uncertainty, or effort. There is no universal points-to-hours conversion, and dividing a team’s point total by its available hours does not produce a reliable individual productivity measure.
Recent completed points or items can help a team discuss a forecast, provided the work and team context are reasonably comparable. If availability changes substantially, compare the coming Sprint with a relevant past Sprint and discuss the difference; do not apply a fixed points-per-person formula. Points are most useful as a team’s own planning aid, not as a basis for ranking Developers or teams.
Explicit person-hour planning makes holidays, meetings, and allocations visible, but it can imply false precision. Recent completion history reflects the team’s actual delivery, but may mislead when the team, work type, or availability changes. Combining visible upcoming capacity with comparable historical completion is a stronger conversation starter than treating either figure as a quota.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How should you diagnose the miss before the next Sprint?
Compare what the team forecast at planning with what was completed and what changed; do not collapse every kind of miss into “bad estimates.” The Sprint Review and Retrospective provide opportunities to inspect the outcome and improve the next forecast.
Free tools Windows power users keep installed
One-click scans. No signup required.
- Compare planned and actual availability. Were people absent, reassigned, or pulled into more support work than expected? Which demands were knowable at planning?
- Separate original scope from added or changed scope. Identify work introduced after the Sprint began, scope expansions, and changed acceptance conditions. Discuss how those changes affected progress.
- Inspect unfinished work against the Definition of Done. Was it waiting on tests, review, integration, or another necessary step? Avoid counting partially completed work as completed output.
- Look for uncertainty hidden in refinement. If people who estimated the same item had different assumptions about migration, testing, dependencies, or acceptance criteria, clarify the assumptions or split the item into smaller pieces.
- Identify impediments and recurring interruption patterns. Distinguish a one-off surprise from support demand that should be visible in future planning.
- Check the relationship between selected items and the Sprint Goal. Would a smaller, more coherent set of work have supported the goal better? An item list is a forecast, not a reason to keep work that no longer helps the objective.
The response depends on the cause. If the initial plan exceeded realistic availability, correct the capacity assumptions. If item discussions concealed different interpretations, improve refinement or split the work. If mid-Sprint scope changed, make the change visible and revisit how scope is negotiated. If the Definition of Done exposed unfinished verification, include that work in future forecasts rather than treating it as optional cleanup.
Also popular on Amazon
- 【Read before You Buy】 Note: This adapter is USB 2.0 version and cannot transmit HDM, VGA, or other video signals. Nevertheless, they are fully capable of charging devices,duplicating files, and can be seamlessly integrated with USB-C earphones, wireless network adapters, and SD card adapters.
- 【Easy to Use and Safe】Thanks to modern manufacturing techniques, we've made these adapters sufficiently compact so that they can remain inserted in your device without noticeable protrusion or inconvenience. This means you don't have to constantly plug and unplug them, reducing the likelihood of wear and misalignment, and making them more convenient to carry around.
- 【Reliable Quality】Engineered for enhanced durability, durable aluminum alloy shell material,get excellent wear resistance and heat dissipation,the male USB C and female USB connectors & the male USB and female USB C connectors are designed to be plugged and unplugged up to 20000 times. Provides data transfer, device charging, memory space expansion, and additional computer peripherals.
- 【Think more for you】Do you need to connect a USB-C-enabled device to an odd device that only has USB-A ports? Then these USB-A male to USB-C female adapters are made for you.Simply insert the adapter into the USB-A port on the device, and you can instantly connect your USB-C device to the device that originally didn't have the correct connection port.
- 【Trusted xiwxi Quality and Service】As a responsible brand seller, you will receive xiwxi's 12-month Quality assurance and lifetime friendly customer service, you're not just buying a product,you're investing in peace of mind with all-round quality and exceptional customer service.
What if the team uses an AI coding agent?
Do not add an AI agent to the forecast as another accountable Developer. People still need to inspect, test, own, and integrate its outputs, and that work belongs in the forecast. If that review is already captured in the relevant backlog estimate or your focus-hours assumption, do not deduct it a second time.
The practical question is not how many “extra developers” a tool represents, but whether it changes the work, the time available, or the verification needed to meet Done. Track any material difference in the team’s own completed work and planning assumptions rather than assuming a universal productivity multiplier.
What should go on the next-Sprint capacity worksheet?
Use a short worksheet at planning to make assumptions reviewable. It should help the Developers discuss a forecast; it should not be used to assign individual quotas.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →| Planning prompt | What to record |
|---|---|
| Which dates are working days? | Team calendar, local holidays, and nonworking days for this Sprint. |
| Who is available to this team? | Each person’s actual allocation, including shared-team time. |
| What known absences are scheduled? | Leave, training, and other known time away by person. |
| What planned time is outside backlog work? | Expected Scrum events, refinement, and separate support or review demands. |
| What does our focus-hours number already exclude? | Its definition, if the team starts from observed focus hours rather than nominal hours. |
| What uncertainty is not already counted? | A team-chosen allowance, if used, and the recurring evidence behind it. |
| What did we complete in comparable Sprints? | Recent completed items or points, Definition of Done context, and major differences in availability or work type. |
| What is the Sprint Goal? | The single objective the selected work is meant to support. |
After the Sprint, compare the worksheet with what actually happened. Update the assumptions that were wrong, preserve the ones that remain useful, and distinguish forecast error from scope changes or unexpected events. Over time, the goal is not to predict every hour; it is to make a forecast that is honest about capacity and useful for achieving the Sprint Goal.
Frequently Asked Questions
Should I remove the Scrum Master and Product Owner from the capacity calculation?
Count the people who will do the forecasted work, not job titles in isolation. Scrum accountabilities do not determine whether someone contributes to a particular item; include their real availability only when they are part of the team’s delivery work for that Sprint.
Should unfinished stories count toward velocity?
Use the team’s Definition of Done consistently: work that did not meet it is not completed output for that Sprint. Keep partially finished work visible for planning and inspection, but do not treat its remaining effort as completed points or items.
Can I use capacity planning to compare individual developers?
Capacity planning is for making a team forecast, not ranking people. Individual comparisons ignore differences in allocation, work type, collaboration, and the fact that Scrum outcomes depend on the team’s combined work.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesHow should we handle an emergency that arrives mid-Sprint?
Make the new work and its trade-offs visible, then discuss scope with the Product Owner while protecting the Sprint Goal. Afterward, record the interruption so the team can decide whether it was exceptional or a recurring demand that future forecasts should account for.
