BAs embrace Non Functional Requirements

It is often argued that business analysts like functional requirements, so, therefore, they tend to naturally gravitate towards these. On the other hand, the humble non-functional requirements are left in the shadow and rarely given a second thought until the last minute. Doing, this causes many issues when you are about to go live with a system. While the system/product may look great, if the performance is not there then no one will use it. This will impact the business a lot more than if a nice to have a feature is not included in the final product. Differences …

This post was originally published on this site