Managing Non-Functional Requirements in Agile Projects
Here are some tips for getting NFRs sorted out in an Agile project.
The Guide to the Business Analysis Body of Knowledge® (BABOK® Guide v3) (p. 16) denominates Non-functional requirements (NFRs) also as quality of service requirements, which, although it is not directly associated with the functionality of the solution, define the circumstances in which the solution must remain effective or the quality it must have. Ensuring that your solution is of good quality and performs well is essential when working on Agile projects, and NFRs are crucial in achieving this goal. Although NFRs are not directly related to how a piece of software works, they are still essential to determine how effective, efficient, reliable, usable, adaptable, maintainable, and secure the software is. Usually, it’s up to the Business Analyst to write down and manage all the NFRs. This helps everyone on the Agile team understand what they’re supposed to be doing. Here are some tips for getting NFRs sorted out in an Agile project:
