Affinity Diagrams: in this technique, the ideas generated from any other requirements-gathering techniques are grouped by similarities. Each group of requirements is then given a title. This sorting makes it easier to see additional áreas of scope (or risk) that have not been identified.
Affinity diagrams can also be organized by requirement categories.
Business Requirements
Annotations:
Why was the Project undertaken?
What business need is the Project intented address?
Stakeholder Requirements
Annotations:
What do stakeholder expect from and want to gain from the Project?
Solution Requirements
Annotations:
What does the product need to look like?
What are its functional requirements (how the product should work) and nonfunctional (what will make the product effective)?
Transition Requierements
Annotations:
What types of handoff procedures or training are needed to transfer the product to the costumer or organization?
Project Requirements
Annotations:
What are the expectation for how the Project should be initiated, planned, executed, controlled and closed?
Quiality Requirements
Annotations:
What quality measures does the product need to meet?
What designates a deliverable as successfully complete?
Technical Requirements
Annotations:
How will the product be built?
What are the product specifications?