How to Deal with Unplanned Work in Software Development
Unplanned work is just what you would expect—anything that needs to be done but hasn't gone through the normal planning process. It's the production bug that drops in mid-sprint, the urgent customer request that can't wait, or the infrastructure issue that demands immediate attention.
Every team deals with unplanned work. The question isn't whether it will happen, but how you handle it when it does. Teams that manage unplanned work effectively maintain their velocity and predictability. Teams that don't end up in a constant state of firefighting.
Short-Term Tactics to Deal with Unplanned Work
When unplanned work arrives, you have three options:
Absorb
If the team has capacity, absorb the unplanned work into the current sprint without removing anything else. This works when the unplanned item is small and the team isn't already at capacity. Be careful not to overload the team—absorption should be the exception, not the rule.
Replace
If the team is at capacity, replace a planned item with the unplanned work. Choose the lowest-priority planned item to defer. This maintains a sustainable workload while ensuring the urgent item gets addressed. Communicate the trade-off to stakeholders so they understand what's being deferred and why.
Reject
Not all unplanned work is truly urgent. Evaluate whether the item really needs to be done now or if it can wait for the next sprint. Push back on requests that aren't genuinely urgent. Having clear criteria for what constitutes an emergency helps the team and stakeholders make better decisions.
Long-Term Solutions to Prevent Unplanned Work
Provision a Buffer
The most effective long-term strategy is to plan for unplanned work by reserving capacity. Most experienced teams plan for 70-80% of their capacity, leaving 20-30% as a buffer for unplanned items. Track your historical ratio of planned to unplanned work to calibrate the right buffer size for your team.
Improve Your Prioritization
Strong prioritization reduces unplanned work by ensuring the most important items are addressed proactively. Regular backlog grooming, clear priority frameworks, and stakeholder alignment all help prevent "urgent" requests that could have been anticipated with better planning.
Focus on Quality
Much unplanned work comes from bugs and production issues. Investing in code quality—through better testing, thorough code reviews, and proactive technical debt management—reduces the volume of unplanned work over time. Track the sources of your unplanned work to identify patterns and address root causes.
Enter DevStats
Engineering analytics tools help you understand and manage unplanned work by providing visibility into how your team's time is actually spent. Track the ratio of planned to unplanned work over time. Monitor how unplanned work affects cycle time and throughput. Use work breakdown reports to see how much effort goes to new features versus bug fixes and maintenance.
informed decisions about buffer sizes, identify recurring sources of unplanned work, and demonstrate to stakeholders the impact of interruptions on planned delivery.
Wrapping Up
Unplanned work is inevitable, but it doesn't have to derail your team. Use short-term tactics (absorb, replace, or reject) to handle individual items, and invest in long-term solutions (capacity buffers, better prioritization, and quality improvements) to reduce the overall volume. Track your unplanned work ratio over time and use the data to continuously improve your planning process.