What user story details reveal the customer problem?
This tests if you see stories as problem placeholders, not specs. A strong answer asks for user role, action, 'so that' value, and confirmation criteria while demanding conversation. Red flag: listing technical tasks without mentioning the customer problem.
This tests whether you treat user stories as placeholders for customer conversations rather than technical requirements documents. A strong answer covers four things: first, the who, what, and why including the 'so that' justification; second, confirmation criteria that define done; third, stakeholder pain context; and fourth, space for conversation instead of prescriptive design. Red flag: answering with JIRA fields, acceptance criteria that only describe implementation steps, or ignoring the value justification entirely.
Read the original → resources.scrumalliance.org
- #agile
- #user-stories
- #scrum
- #product-sense
- #requirements
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.