What options exist when a story is too large for one sprint?
This tests vertical-slicing discipline versus architectural decomposition. A strong answer covers splitting by user value, checking INVEST criteria, and avoiding task-like layers. A red flag is proposing horizontal database or UI splits that defer feedback.
This tests whether a candidate defaults to vertical slicing or falls back to architectural decomposition during sprint planning. A great answer discusses splitting the story into small user stories that deliver end-to-end behavior, evaluating splits against INVEST criteria, and steering clear of task-like or component-based pieces. It should also name the trade-off that horizontal splits feel easier to plan but hide integration risk and delay feedback. A red flag is suggesting database and UI layers as separate stories.
Read the original → humanizingwork.com
- #agile
- #scrum
- #story-splitting
- #sprint-planning
- #invest
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.