A user story is a work type that is defined as “a short description of a small piece of desired functionality written in the user’s language” in SAFe. A user story is a primary artifact used to define system behavior in Agile. It is a simple and concise way of expressing the user’s needs and expectations from the system. A user story typically follows the format of “As a [role], I want [functionality], so that [benefit]”. A user story also has acceptance criteria and acceptance tests that specify how the functionality will be verified and validated. A user story is intended to enable the implementation of a small, vertical slice of system behavior that supports incremental development. A user story is maintained and prioritized in the team backlog by the product owner1. References: Story - Scaled Agile Framework