PMI-ACP · Question #544
Non-functional requirements should be written as user stories whenever possible.
The correct answer is B. False. False. Non-functional requirements (NFRs) - such as performance, security, scalability, and reliability - should NOT generally be written as user stories. NFRs apply system-wide rather than representing a discrete user interaction, making the user story format ('As a user, I want
Question
Non-functional requirements should be written as user stories whenever possible.
Options
- ATrue
- BFalse
How the community answered
(51 responses)- A10% (5)
- B90% (46)
Explanation
False. Non-functional requirements (NFRs) - such as performance, security, scalability, and reliability - should NOT generally be written as user stories. NFRs apply system-wide rather than representing a discrete user interaction, making the user story format ('As a user, I want...') a poor fit. NFRs are better captured as constraints, quality attributes, acceptance criteria applied across stories, or as items in a Definition of Done.
Topics
Community Discussion
No community discussion yet for this question.