A common challenge while writing a user story is how to handle a product's non-functional requirements. These are requirements that are not about a specific functionality but rather about operational qualities, such as performance, security, and technical requirements. These are normally captured as performance constraints. Scrum teams have been putting NFR as stories in the backlog and it has worked for them.
A product owner can define the overall story/epic that may be large and would require decomposing into Sprintable stories. These are stories that can be understood, estimated, and are small enough to fit into the Sprint. It's done over the project progressively.
While working with backlog, we should keep ...
