Non Functional Requirements are Ignored
The product does everything the user stories say…yet customers complain it’s slow, and insecure.
It’s a frustrating place to be; the user stories are “done,” and still something is clearly missing.
What exactly?
Performance. Security. Usability. Scalability.
These are the Non-Functional Requirements… the NFRs.
The problem is, the NFRs DO NOT shout during sprint planning. They shout during production.
In today’s post, I’ll break down:
why NFRs get ignored,
why does it happen with the Scrum teams
how the teams I worked with fixed this problem
Let’s get started.
Got an urgent question?
Get a quick answer by joining the subscriber chat below.
