Agile Foundations

7 COMMON AGILE TECHNIQUES

7.1 STORIES AND BACKLOG REFINEMENT

Stories define what is required from the team by the customer and stakeholders (see Chapter 5). A story is not a detailed specification of a requirement; rather, it is a token or reminder for the team that a feature (or anything else that is value-add – for example, a story driving the creation of a security standard) needs to be delivered.

Stories should include:

• WHO wants a feature. It is good practice to write the ‘Who’ statement in the stories from the perspective of an ‘Agile persona’. An Agile persona is any person or group (a ‘user’) who will interact with the features being created. The reason that stories are written from the perspective of an Agile persona is that it facilitates ...