Writing User Stories and Grooming the Backlog
Focus on what can be done rather than be frustrated by what can’t be done.
The key drivers of work within an agile process are the user stories, which are collected from the customers, stored in the backlog, and built by the team. User stories are essentially requirements that are written from the perspective of the user of the product. The backlog is essentially a requirements list that is continuously groomed to understand priority and gain clarity. As a readiness activity within the RICH model, you need to consider the user story language construct you plan to use to help with consistency ...