How to Discuss Sprint Carryover in English

Sprint carryover — work that didn’t finish and rolls into the next sprint — is normal, but how it’s discussed shapes whether a team looks like it’s struggling or simply adapting to real information. Vague explanations (“we just ran out of time”) invite skepticism, while specific ones build trust even when the news isn’t great. This guide covers the English for discussing carryover clearly.

Key Vocabulary

Carryover item — a specific piece of work that didn’t complete within the sprint and is being moved to the next one, distinct from work that was cut entirely. “This is a carryover item, not a cut one — it’s about 80% done and we expect to finish it in the first two days of next sprint.”

Scope discovery — new information learned during the sprint that revealed the work was larger than originally estimated, a common and legitimate reason for carryover. “The carryover isn’t due to slow execution — it’s scope discovery. We found the migration needed to handle three legacy data formats we didn’t know about at planning time.”

Blocked time — time during the sprint when the item couldn’t progress due to an external dependency, distinct from time spent actively working on it. “Two of the five days on this item were blocked time, waiting on a security review from another team — actual engineering time was closer to three days.”

Re-estimate — an updated estimate for the remaining work, given with the benefit of what was learned during the sprint, rather than repeating the original number. “Based on what we now know, the re-estimate for the remaining work is two days, down from our original five-day estimate for the whole item.”

Reprioritization — the decision about whether the carryover item should be the first priority next sprint or should yield to something more urgent that emerged since. “Given the carryover, we need a reprioritization conversation — does this still take precedence over the new request from the support team?”

Common Phrases

• “This is a carryover item — here’s specifically why it didn’t finish.”
• “This wasn’t a velocity problem, it was scope discovery — we learned [specific thing] partway through.”
• “A chunk of this time was blocked, waiting on [specific dependency].”
• “Based on what we now know, the re-estimate is [specific new estimate].”
• “Does this carryover item still take priority next sprint, or has something more urgent come up?”

Example Sentences

Explaining carryover without sounding defensive: “This item is carrying over, and I want to be specific about why: we discovered during implementation that the third-party API doesn’t support batch requests the way the documentation implied, which added about two days of unplanned work. It’s currently 70% done.”

Distinguishing blocked time from slow progress: “It’s not that the team was slow on this — two full days were blocked waiting on legal sign-off for the data retention policy, which we didn’t anticipate needing at planning time. Active engineering time was on track.”

Opening a reprioritization conversation: “Since this is carrying over, I want to check whether it should still be next sprint’s top priority — the incident from last week surfaced a related issue that might actually be more urgent to fix first.”

Professional Tips

• Name the specific reason for carryover (scope discovery, blocked time, underestimation) rather than a vague “we ran out of time” — specific reasons build more credibility than a blanket excuse.
• Distinguish blocked time from active working time when explaining a delay — a task blocked for two days out of five is a very different story than a task that took five days of active effort and still isn’t done.
• Give a re-estimate based on new information rather than repeating the original estimate — it shows you’ve actually incorporated what was learned, not just hoping the same number holds.
• Use carryover as a trigger for a reprioritization conversation, not an assumption that the item automatically stays top priority — priorities can shift between sprints for good reasons.

Practice Exercise

1. Write a two-sentence explanation of a carryover item that specifies the actual reason it didn’t finish.
2. Write one sentence distinguishing blocked time from active working time for a delayed task.
3. Write a sentence opening a reprioritization conversation about a carryover item.

Navigating Nuance: Specific Language for Carryover Requests

Let’s be honest – “carryover” can feel like a technical term that obscures the real reason something wasn’t completed in a sprint. For non-native English speakers, the precise language around it feels particularly crucial because it directly impacts how your ideas and requests are received. It’s not just about what you say, but how you frame it – focusing on collaborative problem-solving rather than simply pointing out what didn’t get done. A key shift is to move away from statements that can sound accusatory (“We couldn’t finish X”) and towards solutions focused on future planning (“To ensure we deliver the core features in this sprint, could we explore carrying over [specific task]?”).

Consider a scenario: you’re responding to a code review comment regarding a feature that wasn’t finished. Instead of replying with “I didn’t have time,” which can sound dismissive, try something like, “Thanks for the feedback! I recognize that implementing [feature name] fell slightly behind schedule. To ensure its completion in the next sprint, I propose we dedicate two days to it, focusing on [specific tasks identified in the review]. This will allow me to address the concerns raised and deliver a fully functional version.” Notice how this explanation includes acknowledging the delay, offering a concrete solution with a defined timeline, and demonstrating an understanding of the reviewer’s perspective. Using phrases like “fell slightly behind schedule” is often more palatable than stating a direct failure.

Another common situation arises in Slack channels when discussing upcoming sprints. Suppose you need to request that a task be carried over from the previous sprint. A simple “Can we carry this over?” lacks context and might raise questions about why it wasn’t completed initially. Instead, craft a message like: “Hey team, I’m looking at the next sprint and realizing we have significant overlap with [task name] from last week. To optimize our workflow and ensure we prioritize the most impactful items, could we discuss carrying over [task name] for approximately half a day to focus on [new priority]? This would allow us to fully address [specific challenge related to the task].” The key here is to frame it as an optimization decision, not a complaint about past performance.

Finally, when writing PR descriptions requesting carryover, be exceptionally clear. Don’t just say “Carry over for next sprint.” Instead, detail why it’s being carried over and what you plan to do with it: “Requesting carryover of [task name] from Sprint 3 due to unforeseen complexity in integrating with [external system]. This work will be prioritized during Sprint 4, focusing on [specific tasks], and will contribute directly to the completion of [overall goal].” This level of detail demonstrates professionalism and a commitment to delivering value.