Skip to main content
Enterprise Agile Planning icon with arrows

This post is from the CollabNet VersionOne blog and has not been updated since the original publish date.

Last Updated Feb 03, 2011 — Enterprise Agile Planning expert

We didn’t finish the Story – now what?

Enterprise Agile Planning

It happens to the best of teams: good efforts were spent during the iteration toward completing all the tasks (and tests!) associated with a story, but one way or another, not everything was completed on time for the Review.  So, now what?

In the Review > Close Sprint stage, the Split process allows for an accurate reflection of the work that was actually performed within a given iteration while giving you the freedom to determine if any credit (i.e. feature estimate) has been earned by the partially completed feature.  The Split takes the portion of work that is complete and leaves it in the current iteration, and takes the work that remains and moves that to the next iteration under a newly-created story.  The following applies to the tasks (or tests) associated with the story being split; if a task is:

  1. Completed (i.e. To Do of 0) – these are left intact with the story in the existing iteration
  2. Not Started (i.e. Done of 0) – these are moved forward to the new iteration
  3. Partially Completed (i.e. some Done and some To Do) – these will exist in both the new and old iterations.  The one in the old iteration will have a To Do value of 0 and all the Done amount left there.  The one in the new iteration will have the remaining To Do amount.

After you perform a Split…

  • The Story and corresponding tasks/tests are automatically moved to the next iteration – you do not need to edit this manually;
  • You can edit the Detail Estimate and To Do amounts for the remaining workload from the Split screen directly, or leave them as-is for further editing during your next iteration Planning session.

So let’s keep moving along, tracking the story to completion!

The post We didn’t finish the Story – now what? appeared first on VersionOne Blog.

More from the Blog

View more Government Cloud
Apr 12, 2022 Government Cloud receives FedRAMP Authorization through sponsorship from the United States Department of Veterans Affairs

Enterprise Agile Planning
Flagship Agility solutions can effectively scale agile deve ...
Read More
Nov 22, 2021

What are the qualities of highly effective agile teams?

Enterprise Agile Planning
A team is the core unit of productivity in an agile organization. Wher ...
Read More
Nov 15, 2021

How an open-first attitude revolutionized government tech development

Enterprise Agile Planning
Public perception of government is often that it is slow-moving, reluc ...
Read More
cross functional
Nov 08, 2021

6 best practices for building resilient cross-functional teams

Enterprise Agile Planning
Agile frameworks prize the quality of resilience within every facet of ...
Read More
Contact Us