NFRs are Constraints

NFRs — Non Functional Requirements (qualities of a system like Scalability, Security, etc) are constraints of a system once built and in place. For example: Architecture team determines that Amazon Web Services (AWS) should be the one to go with (this is alignment with ‘Scalability’)… then they make this as one of their ASRs (Architecturally Significant Requirements). Once this ASR is in place, it constraints upcoming functional requirements that use web services … AWS will be used instead of another web services from somewhere else.

NFRs are part of the Definition of Done (DoD).

NFRs are initially enablers along the architecture runway… supporting / enabling a functional requirement to its fruition.

NFRs and Enablers are like the devil and angel on your shoulders as you build functionality of your system.

By Clarence Galapon

CE, MBA, Lean Agile Coach, Trainer, Teacher, SPC, RTE, PSM, PMI-ACP, PMI-PBA, PMP, CC, ABNLP NLP (Neuro Linguistic Programming) Practitioner, NLP Coach, NLP Trainer, Practical Psychologist, Life Coach, Software Executive, Entrepreneur, Author, Investor, and Innovator with a Creative, Lean, Agile, and Wander mindset.

Related Posts


Forgot Password?

Join Us

%d bloggers like this: