Non-Functional Requirements (NFR) in Scrum

Vineet Patni , I always add an Item into Sprint Backlog with the consultation of Product owner on 2 Items. 1) Knowledge Transfer , This helps team share their Technical or Functional expertise among themselves to become self-sufficient to finish their work 2) Non- Deliverables, though it's a non-deliverable, we can't avoid few things during the sprint, such as lower environment availability and usability. If it's not ready, somebody has to work on it to get it to an usable state. This adds value to reach Sprint Goal, but not a functional requirements. It's all non-functional. Many more such examples I have seen throughout my journey.

Very rightly said Vineet, anything or everything which is adding value to the product should be added to product backlog Items.

From my Experience NFR's are never added to the Product Backlog , and you have rightly mentioned it needs to be. For the NFR identification we need to have a mature Product Owner to add the NFR in a timely manner

Who is held accountable for the creation of User Stories ? Now-a-days organisations are asking Scrum Master to do so.. Any comments on that..