Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Story Splitting Techniques in a Nutshell

DZone's Guide to

Story Splitting Techniques in a Nutshell

How does story splitting work? what exactly is it? Read here to learn how to do it right.

· Agile Zone
Free Resource

See how three solutions work together to help your teams have the tools they need to deliver quality software quickly. Brought to you in partnership with CA Technologies

There are many techniques for splitting stories depending upon the situation you’re in. The goal is to break down work into the smallest increments that still provides some value, but the value can simply be a step in the right direction—as long as it produces visible results.

Most big stories are compound stories, meaning they’re made up of other smaller stories. If this is the case, simply break down the compound story into its component stories. This may have to happen repeatedly in order to break down a story to its smallest valuable component.

If the story includes unknowns, break out the known from the unknowns and begin iterating to the unknowns until they’re better understood and the domain of the unknown shrinks to nothing. In situations like these, it’s good to spike an unknown by researching specific questions in time boxes. At the end of the time box, evaluate your progress on answering your question. In this way, you can eliminate the unknowns.

If a story represents a workflow or sequence of steps needed to accomplish a task, you can either thin-slice the sequence so you’re doing a very simple version of each step then devise additional stories for implementing each step in more detail. Alternately, you can create stories for each step in detail and string them together, if that makes more sense.

If the story acts on different data in similar ways, then you can make it work for a simple case and then have subsequent stories that work on the different data sets.

In some stories, it makes sense to write the happy path first and then write additional stories to handle exceptions, while in other stories it makes sense to peel off exceptions as individual stories that drive you to the happy path. Whether you choose one approach or the other depends upon the preconditions required and the complexity of the exception handling.

Regardless of the techniques you employ to split stories, the goal is that each story be a step toward overall completion and that it satisfies some acceptance criteria. It’s important to always have a clear criterion for when your story is done so you know when to move on to the next story.

And that’s it in a nutshell.

Discover how TDM Is Essential To Achieving Quality At Speed For Agile, DevOps, And Continuous Delivery. Brought to you in partnership with CA Technologies

Topics:
agile methods ,story

Published at DZone with permission of David Bernstein, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}