Stop calling requirements ‘non-functional’!
You want deliveries that don’t function?
Why name it wrong? Call it what it is!
If you look closer at non-functional requirements, they fall into two groups:
1οΈβ£ Operational requirements π
Just like Function requirements, it describes what users can observe at runtime: the behavior. But we focus more on how it does this, like Performance and Availability.
2οΈβ£ Developmental requirements π οΈ
Users can’t observe these, but they are also important. These are developmental qualities, requirements from the development team. Like Maintainability, Portability, and guidelines.
Change the conversation by doing this! π‘
