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. Proper definition and implementation of NFRs is critical. Over-specify them, and the solution may be too costly to be viable; under-specify or underachieve them, and the system will be inadequate for its intended use. An adaptive and incremental approach to exploring, defining, and implementing NFRs is a vital skill for Agile teams. (SAFe) If you like this subscribe to the Podcast to receive all the notifications. Patreon link if you like to buy us a cup of coffee :) https://www.patreon.com/iahmadzain Links in this Episode: SAFe (Scaled Agile Framework) NFR (SAFe) / Wikipedia Protofolio EA (Enterprise Architect) Epic Owner Product and Solution Management System and Solution Architect/Engineering Product Owner