Vertical Story Slicing Takes the Cake cover image
Product Ownership

Vertical Story Slicing Takes the Cake

Learn the characteristics of a well-formed story, when/how to slice them, and explore nine common patterns for effective story slicing.

Profile image of Kim Poremski
Kim Poremski
Oct 05, 2018 • 68 min read
5.00 (1)
Product Ownership
Product Specifications
Product Increment
Backlog Refinement
Use Case
Show more

Summary

Kim Poremski explores some of the common challenges that Scrum teams experience and how focusing on INVEST criteria and vertical story slicing can help. Through the session, she highlights the characteristics of a well-formed story, explores nine common patterns for effective story slicing, and offers clues for when/how to slice stories.

Takeaways

  • A story should be independent, stand on its own, and be vertically sliced. It should also be negotiable to get the most value out of it.
  • If a story does not add value, then it's not a good story to begin with.
  • Stories should be estimable, the team should have a shared understanding of them.
  • Stories should be small to fit with the sprint and they should also be easy to validate or test.

Learn More

Suggested Resources