When a story is too big, it is sometimes referred to as:Select one:Non-functional storyBig User StoryEpicJourney

Break Down the Problem

1. Identify the terms provided in the options.
2. Understand the context of the terms in relation to project management or software development.

Relevant Concepts

1. Non-functional story: Refers to requirements that define criteria such as performance, usability, reliability, etc., not directly related to specific user functionalities.
2. Big User Story: This may refer to a sizable user story but does not have a specific terminology associated with it.
3. Epic: In agile methodologies, an epic is a large body of work that can be broken down into smaller tasks or user stories.
4. Journey: This typically relates to user journeys or use cases but does not signify the size of a story.

Analysis and Detail

• The term "epic" is widely used in Agile and Scrum frameworks to describe large user stories that encompass multiple smaller stories.
• The other options, while they have their significance in different contexts, do not specifically denote a large story.
• Therefore, the most fitting term for a “story that is too big” would be "Epic."

Verify and Summarize

• Verifying the context in which these terms are used confirms that the agile methodology uses "epic" as the correct term for a sizable narrative within a software development context.

Final Answer

Epic