13. A user story covers registration, billing, reporting and cancellation. How would you split it?
MediumNeeds & requirements
Technical
Show model answer
Identify independently useful user outcomes and the smallest coherent slices that can be demonstrated. Split by workflow or supported scenario while making dependencies and safety requirements explicit.
Keep acceptance criteria with each slice and check the end-to-end journey across them. Splitting only into frontend, database, and API tasks may help engineering planning but does not by itself create separately usable customer outcomes.
What interviewers listen for
- Slice by useful outcome
- Expose dependencies
- Retain end-to-end criteria