Story Splitting
When defining what a User Story is, we stated that we should be able to deliver it in a few days. That means that the team should be able to design, build, test, and deploy to meet the DoD for that User Story. This often means that the teams must rethink how they have typically received requirements and broken down the work.
This breakdown does not mean that the team will write a story to figure out what they are going to do, another story to do the work, another story to test the work, and yet another story to deploy it. If we are doing that, we don’t have a vertical slice of the work.
A vertical slice is a User Story that cuts through all the layers of a system from the user interface down to the data layer. A vertical slice is developed and tested from end to end, providing a working and usable increment of the system.
To create vertical sliced User Stories for our teams that can be completed in a few days, we will often need to split our Features...
