A.During the sprint planning when they can't fit enough into the sprint

B.Prior to starting a new sprint

C.In the retrospective when it turns out they can improve quality

D.Prior to starting a new project

A.Handle them during a risk mitigation phase before development

B.Scrum is for functional, frontend development only

C.Include them in the Product Backlog

D.Before the release, they should be tested and validated in a hardening sprint

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

A.They support Continuous Integration

B.The eliminate the need for build engineers

C.They ensure your product remains bug free

D.They clearly define the build process

E.They allow frequent validation and ensure the product remains in a potentially releasable state

A.Increase quality

B.Complain only in this session to avoid complaining in the rest of the sprint

C.Have more fun during the sprint

D.Increase effectiveness

A.False

B.True