User stories that should be simple are frequently quite complex, written ambiguously, or have underlying needs that are hidden below the surface. Some should be broken up in to multiple stories. You may not know how best to write a user story and communicate needs. Many developers are not trained in the techniques needed to break through in this challenging environment and quickly get a clearer understanding of user needs.
Break Through Thinking
Make this break through: it’s not the designs you bring, or the solutions you suggest, that will clarify needs – it’s the questions you ask that determine how quickly a solution can be implemented. Good questions showcase your understanding and build trust between you and the user. Here are a few situations where a few great questions will help you deal with difficult user stories and difficult times:
Determining the success criteria
Here is a simple approach to clarifying user stories: attach your clarifications as acceptance criteria or test conditions. The user story could be all about the user interface. The success condition in the mind of the user could be very different “A user can buy our product.” By focusing on the outcome not only is the capability needed clearer, but you also now have a clear understanding of what to focus on with users during sessions.