How are NFR's (Non-Functional Requirements) handled within SAFe4.0 Program and team template

Guido Schneider (3.4k●13●85●112) | asked Jun 27 '17, 11:13 a.m.
edited Jun 27 '17, 11:14 a.m.

Dear SAFe Guru's,

we are implementing and rollout the SAFe process together with the RTC 4.0 Program and Team template.
During training, we got the question, how NFR's (Non-Functional Requirements) are handled.

For example in the 4.0 Template the feature does not have an attribute to mark it as a NFR. I think this corresponds to the SAFe process. But now the question comes how is the idea to handle NFR's within project areas based on RTC SAFe P+T template.

regards
Guido

One answer

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Amy Silberbauer (306●5●7) | answered Jun 30 '17, 8:46 a.m.
JAZZ DEVELOPER

Hi Guido,
Non-Functional Requirements are part of the RDNG SAFe Portfolio project template. You would then link these to RTC work items. In the SAFe 3.0 template we had general feedback that the NFR "type" we had added on Features was not the optimum way to deal with NFRs, so when SAFe 4.0 was released we moved those to the Requirements domain. You can certainly add NFR to the Enabler type if you want to customize it and include it on Features (and other work item types).
Amy

It's all about the answers!

Related questions

How are NFR's (Non-Functional Requirements) handled within SAFe4.0 Program and team template

One answer

Your answer