What are three of the best ways to address non-functional requirements?

The correct answer is A. Handle them during a risk mitigation phase before development E. Specific expectations can be used as acceptance criteria to specific product backlog items F. Important, recurring non-functional requirements can be added to the definition of done. There is no hardening sprint, there are only regular sprints. If it's an ever recurring non-functional requirement, it can be added to the definition of done. If it's not it can be added (as a criteria) in the product backlog (item).

Developing Products

Question

Options

AHandle them during a risk mitigation phase before development
BScrum is for functional, frontend development only
CInclude them in the Product Backlog
DBefore the release, they should be tested and validated in a hardening sprint
ESpecific expectations can be used as acceptance criteria to specific product backlog items
FImportant, recurring non-functional requirements can be added to the definition of done

How the community answered

(51 responses)

A
75% (38)
B
16% (8)
C
4% (2)
D
6% (3)

Explanation

There is no hardening sprint, there are only regular sprints. If it's an ever recurring non-functional requirement, it can be added to the definition of done. If it's not it can be added (as a criteria) in the product backlog (item).

Topics

#non-functional requirements#acceptance criteria#definition of done#product backlog

Community Discussion

No community discussion yet for this question.

Full PSD Practice