How to Categorize Customer Requirements
One of the hardest tasks that business analysts and product managers are faced with is making sense of large amount of information and requirements they receive from a variety of sources: project stakeholders, business executives, end users, goverment laws and regulations.
In this article, Karl Wiegers helps us deal with this challenge by showcasing nine categories for requirements knowledge which can help you organize your project requirements.
"Elicitation participants won’t simply tell you, “Here comes a business requirement.” As a BA, you need to determine what type of information each statement you hear represents. "
- Karl Wiegers
![Requirements Categorization Requirements Categorization](/Portals/0/categorize-requirements.jpg)
Here are the nine common categories for requirements:
- External interface requirements
For each clasification, Karl presents types of queues to listen to which will help you categorize the informaton you gather and requirements you receive.
"Classifying the customer input is just the beginning of the process to create good requirements. You still need to assemble the information into clearly stated and well-organized requirements collections. An essential role for a business analyst, product manager, or product owner is to sort through the pile of random customer input and turn it into actionable requirements."
- Karl Wiegers
Continue reading at Medium.com