21
Stories
Traditionally, stories are used by agile teams to specify a piece of functionality to be developed. While they are waiting to be developed, they are assembled into a backlog. These stories are known as “user stories.” However, as we are discovering requirements, it is premature to be thinking about users. The term “user” implies that you envisage someone sitting in front of a computer, which in turn implies that you have a solution in mind. As you are in the process of discovering the business problem, it is definitely unhelpful to be thinking about the solution.
In this chapter, we show you how to make use of stories in a different way. These are not “user stories,” but stories about requirements. This is a trawling technique, so ...
Get Mastering the Requirements Process, 4th Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
