Categories
5G Network
Agile
Amazon EC2
Android
Angular
Ansible
Arduino
Artificial Intelligence
Augmented Reality
AWS
Azure
Big Data
Blockchain
BootStrap
Cache Teachniques
Cassandra
Commercial Insurance
C#
C++
Cloud
CD
CI
Cyber Security
Data Handling
Data using R
Data Science
DBMS
Design-Pattern
DevOps
ECMAScript
Fortify
Ethical Hacking
Framework
GIT
GIT Slack
Gradle
Hadoop
HBase
HDFS
Hibernate
Hive
HTML
Image Processing
IOT
JavaScript
Java
Jenkins
Jira
JUnit
Kibana
Linux
Machine Learning
MangoDB
MVC
NGINX
Onsen UI
Oracle
PHP
Python
QTP
R Language
Regression Analysis
React JS
Robotic
Salesforce
SAP
Selenium
Service Discovery
Service Now
SOAP UI
Spark SQL
Testing
TOGAF
Research Method
Virtual Reality
Vue.js
Home
Recent Q&A
Feedback
Ask a Question
How non-functional requirements can be dealt with within the product backlog?
Home
>
Agile
>
How non-functional requirements can be dealt with within the product backlog?
Dec 23, 2019
in
Agile
Q: How non-functional requirements can be dealt with within the product backlog?
#non-functional-requirement
1
Answer
0
votes
Dec 23, 2019
Non-functional requirements play an important role in the overall product development and delivery. These are the requirements without which the functional part cannot be termed as complete. Let’s first understand what a non-functional requirement is, “Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs.” – Scaledagile. There are different ways of handlings such requirements, like:
Create user stories in the backlog – The non-functional requirements can be similar to “constraints” we put on the system. It can be written in the same format as the usual user story.
Inclusion in DoD – The team can add these requirements as part of their definition of Done. If it is one of the parameters in the definition, it will make sure the NFR doesn’t get missed out and the team can keep track of it along with the original story.
Acceptance Criteria – Non-functional requirements may also be articulated as part of Acceptance criteria which are circumstances that a product must fulfill to be accepted by a user, customer or other stakeholders.
Click here to read more about Agile
Click here to read more about Insurance
Facebook
Twitter
LinkedIn
Related questions
0
votes
Q: How non-functional requirements can be dealt with within the product backlog?
Jan 5, 2020
in
Agile
#product-logs
0
votes
Q: What are non-functional requirements and how do you capture them?
Nov 10, 2020
in
Business Analyst
#non-functional-requirements
+1
vote
Q: How do you align the business direction (roadmap) with the product backlog and user stories?
Dec 23, 2019
in
Agile
#product-roadmap
0
votes
Q: The event-polling nature of Nginx can be dealt with using _____________.
Feb 3, 2020
in
NGINX
#nginx
0
votes
Q: Product Backlog should be ordered on the basis of?
Dec 5, 2020
in
Agile
#product-backlog
#backlog-items
0
votes
Q: ______ indicators can be traced after the product has been launched to view if it meets product goals and user requirements.
Feb 11, 2020
in
JavaScript
...