How should a Feature be expressed according to recommendations?

Features in the SAFe framework are designed to be expressed in a specific format that communicates their value and expected outcomes clearly. The correct approach combines a concise description known as a phrase, a benefit hypothesis that outlines the value the feature is intended to deliver, and acceptance criteria that define the conditions under which the feature will be considered complete and acceptable to stakeholders. This holistic expression ensures that the feature captures not just what is being built, but also why it matters to the customer and how success will be measured.

The use of a phrase provides a succinct title or summary of the feature, allowing team members and stakeholders to quickly grasp what is being discussed. The benefit hypothesis articulates the anticipated advantages and aligns the feature with business goals and customer needs, emphasizing the 'why' behind the feature. Acceptance criteria then outline specific requirements that need to be met, ensuring clear expectations for delivery and quality.

Other options, while they serve useful functions in the Agile and Lean methodologies, do not encompass the complete expression necessary for Features. For instance, a Lean business case focuses more on the justification for investment rather than detailing the feature itself. Similarly, functional requirements tend to describe what a system should do without articulating the broader context of benefit and outcomes. An epic hypothesis statement is