When a story is too big, it is sometimes referred to as:

Question

BlackTom AI · Accepted Answer

When a story is described as being too large or complex to manage as a single unit, practitioners often use a specific term to convey its scale and the need to break it down. 
Option: Big User Story — While this phrase communicates a larger scope, it is not the standard terminology used in agile methodologies to denote oversized work items; the common term distinguishes size as “epic” rather than simply a bigger user story.
Option: Non-functional story — This refers to requirements that describe system qualities (like performance or security). It is a valid category of work but does not capture the notion of a story that is too big to fit in a single sprint; it’s about quality attributes, not overall size.
Option: Epic — This is the established term in many agile frameworks for a large body of work that can be broken down into smaller user stories. When a story is too big, it is typically referred to as an epic, which then gets decomposed into more manageable chunks.
Option: Journey — This word is sometimes used informally to describe a user’s experience, but it is not the formal label for a story that is too large to fit into a normal planning unit.
Option: Journey (again) — Reiterating that this term is not the conventional name for a story of excessive size; it describes experience flow rather than item sizing in backlog management.
In summary, the term that matches the description of a story being too big to handle as a single unit is Epic, as it signals the need to subdivide the work into smaller stories for incremental delivery.

When a story is too big, it is sometimes referred to as:

View Explanation

Log in for full answers

Similar Questions

The template of a user story is:

Which one of the following user stories is a complete user story with all the required detail?

A good quality user story does NOT have the following characteristic:

Who is the source of Agile user stories?

User story is:

What is a key benefit of using user stories in Agile development?

Which of the following best represents the standard format of a user story?

A good quality user story does NOT have the following characteristic:

More Practical Tools for Students Powered by AI Study Helper

Homework AI Solver

Stylized AI Paper Writer

Plagiarism Checker Assistant

Citation AI Academic Writing Tool

In-Class Translation Assistant

AI Note Generator

AI Quiz Answers

Past Exam Questions from University Test Bank

Smart Practice Assistant

Adaptive Practice

Making Your Study Simpler