You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am considering moving my product backlog into JIRA/Greenhopper OnDemand. How have people used JIRA to track non-functional requirements? How have they linked them to user stories, if at all?
Non-functional requirements also should come in product backlog as stories. If you just refer the Scrum Primer by Craig Larman, it states the following.
Product Backlog Item
Functional requirements, non-functional requirements, and issues, prioritized in order of
importance to the business and dependencies and estimated. The precision of the estimate
depends on the priority and granularity of the Product Backlog item, with the highest priority
items that may be selected in the next Sprint being very granular and precise.
In that sense they are also just another story in Jira, right?
Sure - my concern was that NFRs are not typically work items that are scheduled into a Sprint for development, many are underlying principles that drive how other stories are implemented. But just spoke to our resident Agile guru and he agreed that a good way was just to have them in as stories but colour-coded and deprioritised so that they're always there to be seen be everyone but don't actually get scheduled into sprints if it's not appropriate. Thanks.
Many Agile frameworks, including SAFe, define NFRs as constraints on functional requirements. Therefore they should not be as standalone stories, but instead as acceptance criteria. Studies (https://arxiv.org/pdf/1711.08894.pdf) have shown that teams documenting NFRs as stories often lose the requirements and dependencies. Another option is to document the NFRs in a centralised tool such as Confluence, and reference the NFR's unique ID into a stories acceptance criteria.
Some weeks ago I read something interesting about this topic: non-functional requirements are only requirements for which the main stakeholder is not identified yet. ;)
As Renjith mentioned before, you can handle them as normal requirement. An alternativ would be, to create a new issue type for this type of requirements. if you have a lot of non-functional requirements which are related to the normal user stories, I personally prefer to see them as acceptance criteria: e.g. the response time of x should be under 10 seconds.
Thanks for this. Hm. In my case I know who the stakeholders for the non-functional requirements are :)
I like the idea of a different issue type - may do that.
Agree that in reality NFRs are often acceptance criteria for functional stories, I do want to keep them as a list of entities in their own right rather than buried in other stories - in case they get forgotten when new stories are added, for example.