Agile team mentor Lisa Mabli is putting the magnifying glass on user stories in this fun, live session. One of the key components of backlog health — and as a result, work that flows consistently to the Scrum team — is right-sizing the stories and having crystal clear requirements. We know that smaller is better, but how small is too small? How can we break up those larger, blocky stories that take forever to complete? Can’t we just split the story into its Dev part and QA part?
This session answers questions like:
- Can we write one story for dev, and one for QA?
- What if a story is too big for one sprint?
- What is a Gherkin?
- How small is too small?
Contact us to bring a custom user story workshop to your team.