Open adam-ky opened 2 years ago
As stated in the textbook, user stories can also help to capture non-functional requirements
.
Hence we reject this bug.
Team chose [response.Rejected
]
Reason for disagreement: Your response suggests user stories can be NFRs but doesn't resolve the underlying issue of this bug: it is ambiguous.
As per the guideline below, I'm not sure how your product has met this NFR because it is a poorly defined user story. For example, how do you quantify "retrieve data fast" or "fastest time possible"? In contrast, the screenshot you provided illustrates a better defined NFR because:
Team chose [severity.VeryLow
]
Originally [severity.Medium
]
Reason for disagreement: As mentioned in several other issues, severity.VeryLow
is reserved for purely cosmetic issues that do not affect the usage of the product. My rationale for severity.Medium
is because the user story is not very well defined and can cause occasional confusion to developers reading the DG.
I'm not sure if this user story represents a feature or a NFR