Decide what to do with unfinished sprint work

Separate unfinished work that still matters from scope that should be split, paused or dropped before the next sprint.

Make carry-over a new decision with fresh evidence instead of moving every card automatically.

Request TeamBoostAI access Get the work brief Task table (.csv)

Opens the current invite-request page. Access is subject to approval; this example is not imported automatically.

Decision desk

Decide before adding more work

Decision to make: Accept any independently complete slice; keep date filtering uncommitted until its rule is decided.

Illustrative case: an export task was carried over twice. The download works, but filtering remains blocked by an undecided date rule.

Inspect the current evidence

Owner role · Task owner

Evidence: The review distinguishes working download behavior from unfinished filtering.

Resolve the remaining decision

Owner role · Product owner

Evidence: The intended inclusive or exclusive date boundary is recorded.

Replan the remainder

Owner role · Sprint coordinator

Evidence: Only the remaining accepted scope is estimated and considered for commitment.

Filled illustrative decision

Invented planning text. Adapt it to your evidence and confirmed owners.

The synthetic carry-over review accepts the working download as an independent slice. Filtering stays unresolved because stakeholders disagree about whether the final date is inclusive. The next sprint does not inherit the entire old task automatically; a named decision owner must settle the date boundary first.

Questions about this workflow

Is carry-over always a failure?

No. The cause may be changed scope or a discovered dependency. The decision should make that cause visible and actionable.

Should we keep the same estimate?

Reassess the remaining work and uncertainty. Reusing the original estimate can conceal what is already done and what changed.

Does this create tasks in the product?

No. The brief is a manual planning resource. Use the product access link to check onboarding and the workflows available in your account.

Put the outline to work

Review the original outcome and what the team can demonstrate today.
Choose finish, split, pause or drop, with a reason for the remaining work.
Reassess effort and dependency conditions before placing it in the next commitment.

From a useful outline to team work

Explore TeamBoostAI for your team

Record the fresh scope decision when reviewing unfinished TeamBoostAI work instead of treating last sprint’s commitment as current. Confirm the workflows available in your account before adopting this outline.

Request TeamBoostAI access