How do I develop better User Stories/Requirements?
1 comments
This makes me curious about where you turn to when you have hard questions about design stuff. Do you primarily Google your questions, ask colleagues, ask the internet? Is there engineering/type of documentation for design? I know AOSP, but wonder if there's a UX-focused version of that.
I'm paired with a Technical Architect (more programmatic, less point and click) who I can bounce ideas off of. We have a community of people with the same job responsibilities that I can also bounce design questions off of as well (time permitting). I use those resources as well as reference architecture, internet communities and documentation to complete designs.
In User Story meetings, I'm usually the only person representing technology, and I facilitate the conversation and take notes to write user stories after the fact.
When writing the User Stories, I find that sometimes the ask is too specific, e.g., "Add a field." So when a developer picks it up, they easily create the field, but then the business will ask for three more things out of the initial ask.
Is there a method in interviewing the stakeholder which helps round out the user story a bit better so that the feature solves the business problem?