Writing User Stories and Grooming the Backlog

Abstract

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 and comprehension, where you plan to store the Product Backlog for easy access and sorting, and how frequently you plan to groom the backlog.