Techniques for Collecting Epics
There are a number of methods that can be used to pull together the information that is needed to define epics and the subsequent collection of broken down user stories. Some of these methods are described below.
Interviews
Interviews tend to be the default technique used to collect user story requirements. However, while this is one of the more common methods, it takes a certain amount of skill to be able to use this process effectively. The reason for this is that the users themselves are not normally very clear about what they need. In order to clarify exactly which features would help them to simplify their tasks, the Product Owner must be adept at asking the right questions and following up with more context-specific inquiries, while at the same time being careful to keep the query open-ended enough to tease out any important pieces of information.
Observations
A good way for the Product Owner to understand how users use a system, and to find out what changes they need, is to watch them using it. This can be done either by simply going along to their workspace and observing them while they perform their daily tasks, or actually asking them to demonstrate how they would carry out a specific function. Both these techniques can provide valuable insight into the actions that a user will take, and can sometimes uncover scenarios that would otherwise have potentially remained hidden.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: