Definition
Jira is a project management and issue tracking tool built by Atlassian. It is the most widely used tool for Agile software teams — supporting Scrum boards, Kanban boards, backlog management, sprint planning, and reporting all in one place.
Why Teams Use Jira
- Plan and track work across Sprints and releases
- Visualize team progress with boards and dashboards
- Manage the Product Backlog and prioritize work
- Track bugs, tasks, stories, and epics in one system
- Generate velocity charts, burndown charts, and reports
- Connect with tools like Confluence, Slack, and GitHub
Real World Context
Most companies hiring Scrum Masters, Product Owners, and Agile team members expect Jira experience. It is used by over 65,000 companies worldwide including Google, NASA, and Spotify.
The Jira Hierarchy
Jira Work Item Hierarchy — Big to Small
🟣 Epic — Large body of work (e.g. User Authentication)
🟢 Story — User-facing feature
🔴 Bug — Defect to fix
Work Item Types Explained
- Epic — A large initiative spanning multiple Sprints. Example: "Build the Login System"
- Story (User Story) — A feature described from the user's perspective. Example: "As a user, I want to reset my password"
- Task — A piece of technical work. Example: "Set up database schema"
- Bug — A defect that needs to be fixed. Example: "Login button not working on mobile"
- Sub-task — A smaller breakdown of a Story or Task
The Scrum Board in Jira
The Scrum Board is a visual representation of your Sprint. Each card (issue) moves across columns as work progresses. The board is the team's single source of truth during a Sprint.
Example Jira Scrum Board — Sprint 3
To Do
MM-14: Password reset flow
MM-15: Write unit tests
MM-16: Fix login timeout
In Progress
MM-11: User registration page
MM-12: API integration
Done
MM-08: Login page UI
MM-09: Database setup
MM-10: Nav bar alignment
Backlog vs. Sprint Board
- Backlog — All items not yet in a Sprint. The Product Owner orders these by priority
- Sprint Board — Only items committed to the current Sprint. Developers manage this
- Items move from Backlog → Sprint during Sprint Planning
- Items move across the board (To Do → In Progress → Done) during the Sprint
Jira in the Scrum Cycle
| Scrum Event | What You Do in Jira | Who Does It |
|---|
| Sprint Planning | Select backlog items, create Sprint, set Sprint Goal | Whole team |
| Daily Scrum | Update task status, log progress, flag blockers | Developers |
| Sprint Review | Mark stories as Done, share board with stakeholders | Whole team |
| Retrospective | Review velocity chart and burndown — identify patterns | Scrum Master |
| Backlog Refinement | Add details, acceptance criteria, and story point estimates | PO + Developers |
Key Jira Features to Know
- Story Points — Add estimates to backlog items before pulling into a Sprint
- Sprint Goal — Set a Sprint Goal when creating or starting a Sprint
- Labels & Components — Tag issues to filter and organize by area
- Assignee — Assign issues to team members; in Scrum, the team self-assigns
- Acceptance Criteria — Added in the issue description so the team knows when it is done
- Velocity Chart — Shows story points completed per Sprint; used for forecasting
- Burndown Chart — Shows remaining work in the Sprint; helps the SM spot risks early
Common Mistake to Avoid
Do not use Jira story points as a measure of individual performance. Velocity belongs to the team — never compare one developer's points to another's. Points measure complexity, not speed or output.
Jira Roles — Who Does What
| Role | Jira Responsibilities |
|---|
| Product Owner | Creates and orders the Product Backlog, writes stories and acceptance criteria, sets priorities |
| Scrum Master | Creates Sprints, monitors burndown and velocity, ensures the board reflects real progress |
| Developer | Updates issue status daily, logs time, breaks stories into tasks, moves cards across the board |
Question 1
In Jira, which work item type represents the largest body of work that spans multiple Sprints?
A. Story
B. Epic ✓ Correct — Epics are the largest work items and span multiple Sprints
C. Task
D. Bug
Question 2
Who is primarily responsible for ordering and prioritizing the Jira Product Backlog?
A. Scrum Master
B. Development Team
C. Product Owner ✓ Correct — The PO owns and orders the backlog
D. Project Manager
Question 3
What does the Jira Burndown Chart show?
A. The number of bugs in the backlog
B. Remaining work in the Sprint over time ✓ Correct — it helps the SM spot if the team is on track
C. Individual developer performance
D. Total story points ever completed
Question 4
During the Daily Scrum, a developer says they are blocked. What should they do in Jira?
A. Delete the issue and create a new one
B. Move the issue to Done
C. Flag the issue or add a comment describing the blocker ✓ Correct — this makes the impediment visible to the team and SM
D. Reassign it to the Scrum Master
© 2026 MickyMarvels LLC
Practical Agile Mentoring · mickymarvels.info
