How do I develop better User Stories/Requirements?
I'm about six months into a new role where I lead design sessions for a SaaS product and help develop the solution alongside an implementation team.
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?
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?