In SAFe, a clear distinction is made between the purpose, structure and content of features, and that of stories (including enablers). Features are visible units of business intent that the customer recognizes, and it’s at this level of detail that the customer is able to prioritize their needs1. Features are maintained in the ART Backlog and sized to fit in a PI so that each delivers new value2. Stories are short descriptions of a small piece of desired functionality written from the user’s perspective. Stories are the primary artifact used to define system behavior in Agile3. Stories are small and must be completed in a single iteration3. Therefore, features can be larger than an iteration but stories should be small enough to fit into an iteration. References: Story - Scaled Agile Framework, Features and Capabilities - Scaled Agile Framework, Right-Sizing Features for SAFe Program Increments - Scaled Agile Framework