What is Jira backlog and feature backlog
A backlog is the prioritized list of work not yet done. The product/feature backlog holds upcoming features, stories, bugs, and tech debt — owned by the PM and continuously groomed. The sprint backlog is the slice pulled into the current sprint. Backlog grooming/refinement keeps it estimated and prioritized.
A practical Agile/process question — they want to know you understand how work is tracked and prioritized.
What a backlog is
A backlog is the ordered, prioritized list of everything the team might work on but hasn't yet. It's a living queue, not a fixed plan.
Product / feature backlog
The product backlog (sometimes called the feature backlog) is the master list, owned and prioritized by the Product Manager / Product Owner. It contains:
- Features / epics — large bodies of work.
- User stories — features broken into user-facing increments.
- Bugs — defects to fix.
- Tech debt / chores — refactors, upgrades, infra.
It's continuously ordered — highest priority/value at the top, ready to be pulled next; lower-priority and vaguer items toward the bottom.
Sprint backlog
The sprint backlog is the subset the team commits to for the current sprint, pulled from the top of the product backlog during sprint planning, sized to the team's capacity. It's owned by the dev team for that sprint.
Backlog grooming / refinement
A recurring ceremony where the team and PM keep the backlog healthy:
- Clarify and add detail / acceptance criteria to upcoming items.
- Estimate (story points) items near the top.
- Re-prioritize as business needs change.
- Split large stories, remove stale ones.
The goal: the top of the backlog is always "ready" — well-defined and estimated — so sprint planning is smooth.
In Jira specifically
Jira has a literal Backlog view (a list of issues not yet in a sprint) and Sprint sections. You drag issues from the backlog into a sprint. Issue types map to the above: Epic → Story → Sub-task, plus Bug, Task.
The framing
"A backlog is the prioritized queue of work not yet done. The product or feature backlog is the master list — features, stories, bugs, tech debt — owned and continuously ordered by the PM, highest value at the top. The sprint backlog is the slice the team commits to for the current sprint, pulled from the top during planning. Backlog refinement is the recurring ceremony that keeps upcoming items clarified, estimated, and prioritized so the top is always 'ready.' In Jira that's the literal Backlog view you drag issues from into sprints."
Follow-up questions
- •What's the difference between the product backlog and the sprint backlog?
- •Who owns and prioritizes the backlog?
- •What happens during backlog grooming/refinement?
- •How do epics, stories, and tasks relate in Jira?
Common mistakes
- •Conflating the product backlog with the sprint backlog.
- •Thinking the backlog is a fixed plan rather than a living, re-prioritized queue.
- •Forgetting bugs and tech debt belong in the backlog too.
- •Not knowing who owns prioritization (the PM/PO).
Performance considerations
- •Not applicable — process question. The 'health' metric is whether the top of the backlog is always refined and ready.
Edge cases
- •A backlog that grows unbounded and never gets groomed.
- •Items at the bottom going stale and irrelevant.
- •Mid-sprint scope changes affecting the sprint backlog.
Real-world examples
- •Sprint planning pulling the top-priority stories into the next two-week sprint.
- •A weekly refinement meeting estimating and clarifying upcoming Jira stories.