Agile & DevOps

Two more options for splitting agile user stories is by conditional logic or words that combine conditions, and by doing one story that do most of the work.

Funding a value stream will keep development in progress, maintain openness to change, and empower your development team to continually deliver business value.

Two more options for splitting agile user stories is by breaking out manual processes vs automated, and by starting with an empty set, then one, then many.

If getting real data is slowing you down, you can split your agile stories along the line of fake data (and hook into the real data later) and static data.

By building “just enough” to be able to release and get feedback, you’ll figure out if you really need the gold version, or if bronze is “good enough”.

Here are a few ways to consider including non-functional qualities in your solution. If you are aware of these, then you’ll find a way to include them.

Two great techniques for splitting user stories are Spikes (aka Research stories) and Simple to Complex (starting with simple core functionality).

Data is another great way to split User Stories. Variations include options for language or location, and boundaries could be attributes for the same entity.

There are countless possible combinations of devices, platforms, and channels you could design and develop solutions for, so how do you decide what to focus on?

As you evaluate using Business Rules as a story splitting technique, make sure to remember what Business Rules are and how they apply to the work you are doing.