Skip to main content

How does the development team handle non functional requirements?

Last post 05:30 pm January 21, 2021 by Burhan KARADERE
6 replies
07:03 pm March 1, 2016

How does the development team handle non functional requirements?


05:02 pm March 3, 2016

I believe, documenting them in the product backlog with the PO and ensuring they are properly prioritized.


01:51 am March 10, 2016

Agree with Steven that we should raise them to PO and document them in a PBI to prioritize


10:11 am March 10, 2016

Standard answer : it depends, but usually, the NFR become an item in your DOD.

Let's say your NFR is "the webapp must scale up to XXXX users".
It will be very hard to pin this NFR as a PBI.
Instead, you will probably add your NFR as an element of your DOD.


04:47 pm March 10, 2016

My article on NFR's might help:

http://www.scrumcrazy.com/Handling+Non+Functional+Requirements+in+User+…

Essentially, you might need a PBI to implement an NFR when it first appears, and then you might want to add it to the DoD so that the NFR is adhered to in future. Another alternative would be to just add it directly to the DoD, but...

Any time you change your DoD, it's quite possible that all of the upcoming PBI's need to be re-sized too. Look at how the NFR affects future stories then decide if any of them need to be re-sized.


07:24 pm March 10, 2016

> How does the development team handle non functional requirements?

NFR's that constitute part of the product's scope belong on the Product Backlog. They can then be prioritized relative to other items by the Product Owner. This implies that they might not be necessary for every releasable increment.

NFR's that assert a product's quality belong in the Definition of Done. These will apply to each cumulative increment for which the DoD is observed. No work can be released unless those NFR's are satisfied...in other words they are an invariant assertion of quality. Many NFR's of this type may properly belong in the organizational DoD upon which other DoD's are founded.

In either case, the Development Team should handle them by making sure that the relevant work is planned on their Sprint Backlog. This may take the form of tasks, for example.


08:55 pm January 20, 2021

Ensure every Increment meets them.

 


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.