How to address non functional requirements?

Last post 05:27 am May 14, 2020 by Ian Mitchell

3 replies

05:10 pm May 13, 2020

How to address non functional requirements, what do you think ?

11:26 pm May 13, 2020

A popular scaling methodology addresses this. This would cover items such as compliance, IAM, infrastructure, and other operational pieces of a working software. Ideally, these folks would be part of the Scrum Team but they tend to stay in their silos and somebody on the Development Team has to become the go-between to get these resolved.

Chris Belknap

11:51 pm May 13, 2020

NRFs can be addressed by the Definition of "Done", as Product Backlog items, or even Acceptance Criteria. See if this blog post helps: https://www.scrum.org/resources/blog/how-handle-non-functional-requirements-nfrs

Ian Mitchell

05:27 am May 14, 2020

How to address non functional requirements, what do you think ?

Can the Product Owner be reasonably expected to order them in the Product Backlog, or do they represent qualities that are invariant, and which ought to apply to every increment?

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.