Your User Stories Are Too Big!
A common problem for scrum teams is user stories that are too big. When a user story is too big, it is harder to understand, estimate, and implement successfully.
What to do? Scrum promotes incremental development. We talk about getting thin vertical slices of potentially shippable functionality. For many that is a tall order and often seems impossible.
In this experiential session - come get hands-on experience with 4 techniques to split the large stories in your backlog into smaller stories 1 slice at a time. After completing this workshop, participants will be able to split large stories into smaller, more specific stories using: - Conjunctions and connector words - Generic terms - Acceptance criteria - Timeline analysis
- Not Interested