Mastering the Requirements Process, 4th Edition
by James Robertson, Suzanne Robertson, Adrian Reed
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 ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access