The Scrum team deals with non-functional requirements by adding them to the Product Backlog. During Sprint Planning, these non-functional requirements are prioritized along with functional requirements. They are addressed by integrating them into the Definition of Done and reviewing their implementation during Sprint Retrospectives.
How Should Scrum Teams Plan Work To Be Performed Within Sprints:
Before choosing prioritized Product Backlog items that support the Sprint Goal, Scrum teams should clearly define the Sprint Goal. The team estimates and discusses the amount of work that needs to be done during the Sprint Planning meeting, and then develops a plan of action to do it. To accommodate to any changes that may arise throughout the Sprint, constant communication and adjustments are essential.
Non Tech courses provided by StarAgile
Tech courses provided by StarAgile