Agile Business Analysis: Common Categories and Characteristics of Non-Functional Requirements (NFR)
17 common types of non-functional requirements that developers must know to deliver the solutions your organization needs
FREE
Author: Tom and Angela Hathaway
Video Duration: 11.56 minutes
This KnowledgeKnugget™ is part of this eCourse
Non-Functional Requirements Are Critical for Agile Project Success
Non-Functional Requirements (NFR) are all too often the cause of IT project failure. It is not enough for developers to know what the software should do. NFR define the characteristics that determine how thrilled the end-users will be with the delivered business solution. This KnowledgeKnouggetTM defines 17 common types of NFR that you might need to consider.
Udemy Course: Agile Business Analysis - Getting and Writing Lean Requirements
Learn Business Analysis Techniques for Discovering Requirements, User Stories, Features, and Gherkin (Given-When-Then) Tests
Description
Groupings of Non-Functional Requirement Types
The most common categories for NFRs fall into one of the four categories:
Constraints
- Physical Limits
- Laws and Regulations
- Business Rules and Policies
Performance Requirements
- Frequency of Use
- Volumes of Data
- Precision of Data
- Life Expectancy of Data
- Response Urgency
- Update Urgency
User Experience
- Physical Access
- Degree of Interaction
- Trainability
- Security
- Culture
Volatility
- Maintainability
- Portability
- Availability
- Scalability
- Rate of Change
- Reliability
User Story Best Practices for
Agile and Business-side Teams
Lean Business Use Cases in an Agile World
For the Readers: Lean / Agile Business Analysis Techniques
Learn how to design and build Chatbots
NO CODING REQUIRED
Kick-start Your Business Analyst Career
Books, eBooks, and Online Courses at a Reasonable Cost
Written for the aspiring Business Analyst and anyone tasked with defining the business needs, requirements, or user stories for a future IT solution.