Non-Functional Requirements. Do your best for the product quality

Non-functional Requirements (NFR) evaluation is often problematic.

The main reasons are:

1. Customers usually don’t know what to say about the NFR. They hope that you are a team of experts and will do everything right.
2. Business Analysts often lack in-depth knowledge in this area. And that's normal, because some experts dedicate their lives to specific NFR types.
3. The tech team needs the proper input from the business analyst to help.

In my talk, I will tell you about the main categories of non-functional requirements. On examples we will see:

• where to start,
• what to ask and from whom,
• how to describe.

Missed non-functional requirements can lead to failure even the most wonderful project. So do your best for the product quality.