This set builds vocabulary for planning hierarchy and estimation in Jira-style workflows.
0 / 5 completed
1 / 5
At standup, a dev references a large body of work spanning multiple sprints, broken down into smaller individual stories and tasks. What is this called in Jira?
An epic represents a large body of work that's too big to complete in a single sprint, serving as a container that groups related smaller stories and tasks toward a common larger goal. This hierarchy lets a team track both granular daily work and progress toward bigger initiatives. Epics typically span multiple sprints before being fully completed.
2 / 5
During a design review, the team estimates the relative size of a story using a non-linear numeric scale rather than exact hours. What is this practice called?
Story point estimation assigns a relative size value, often using a non-linear scale like Fibonacci numbers, to represent the complexity and effort of a story rather than committing to an exact hour count. This accounts for the inherent uncertainty in estimating unfamiliar work. Aggregating story points across a sprint helps a team gauge and forecast their velocity.
3 / 5
In a code review, a dev references the backlog grooming session where the team clarifies requirements and estimates upcoming stories before they enter a sprint. What is this called?
Backlog refinement (or grooming) is a recurring session where the team clarifies requirements, breaks down large items, and estimates upcoming stories before they're pulled into a sprint. This preparation reduces mid-sprint confusion about scope or acceptance criteria. Regular refinement keeps the backlog healthy and sprint planning efficient.
4 / 5
An incident report style retro shows a team's sprint velocity dropped sharply after several oversized, poorly refined stories were pulled directly into a sprint. What planning gap does this reveal?
Pulling stories into a sprint without adequate prior refinement often means they're too large or ambiguously scoped, leading to inaccurate estimates and stalled progress once work begins. Consistent backlog refinement before planning catches this ahead of time. This is a common root cause identified when reviewing an unexpected drop in team velocity.
5 / 5
During a PR review, a teammate asks how an epic differs from a single story within Jira's workflow hierarchy. What is the distinction?
A story represents a single, independently completable unit of work typically finished within one sprint, while an epic groups many such stories together under a larger goal spanning multiple sprints. This hierarchy lets a team manage both day-to-day execution and longer-term initiative tracking within the same system. Understanding this distinction is fundamental to using Jira's planning hierarchy correctly.