Draft — in editorial review, not yet published. Content has not been approved by a human reviewer.
Lesson 30 / 50 · Version 2.2.0
Jira and Agile Project Delivery
- Level
- Beginner
- Duration
- 15 min learn + 15 min apply
- Prerequisites:
- None
Why it matters: Jira can organize delivery or bury it in tickets. Clear work items, honest workflows, and a cadence that matches how you really work keep projects moving.
By the end you can:
- Explain work items and workflows
- Choose Scrum or Kanban for a team
- Write work items with acceptance criteria
- Use a board and basic JQL
Learn (15 min)
1. Work items and workflows (5 min)
Jira tracks work items (called issues in many places): tasks, bugs, stories. A workflow defines status transitions (To Do → In Progress → In Review → Done). A board displays work using filters and column-to-status mapping; it isn't the workflow itself.
2. Scrum vs. Kanban (5 min)
| Scrum | Kanban | |
|---|---|---|
| Rhythm | Fixed sprints (1–4 weeks) | Continuous flow |
| Planning | Commit to a sprint backlog | Pull when capacity opens |
| Control | Sprint scope | Work-in-progress (WIP) limits |
| Best for | Planned feature delivery | Support, ongoing requests |
| A tool doesn't make a team agile; habits do. |
3. Write work clearly (5 min)
A good work item states the need, the outcome, acceptance criteria, and dependencies:
Title: Add booking button to Team Headshots page
Why: Visitors currently must find the contact form
Acceptance criteria:
Given a visitor on the Team Headshots page
When they click "Book a call"
Then they see the scheduling page within 2 seconds
And the click is recorded as a GA4 event
Depends on: Scheduling page URL approved
Search with JQL: project = WEB AND status != Done ORDER BY priority DESC.
Apply (15 min)
Worked example (3 min). Website feature launch: three items (booking button; GA4 event; QA on mobile), Kanban with WIP limit 3 because requests arrive unpredictably. Dependency: approved scheduling URL. Progress measure: cycle time per item and number of blocked items.
Lab (7 min): Write the work.
- Pick a feature or project.
- Write three work items with outcome and acceptance criteria.
- Choose Scrum or Kanban and justify it in two sentences.
- Write one JQL query to list unfinished items by priority.
Deliverable: Three items, a method choice, and a JQL query. You're done when: A reviewer can tell from the criteria whether each item is done.
Check yourself (5 min)
- What does a workflow define?
- What is a sprint?
- What is Kanban's practical focus?
- Scenario: Stories keep "finishing" and then bouncing back from QA. What's missing?
- Does using Jira guarantee agile delivery?
Reference
Common mistakes
| Symptom | Likely cause | Fix |
|---|---|---|
| Items bounce back | Vague acceptance criteria | Write testable criteria |
| Too much in progress | No WIP limit | Add WIP limits |
| Board confusing | Columns don't match workflow | Map statuses deliberately |
Cheat sheet: Describe outcome → acceptance → dependency → prioritize → visualize and review flow.
Key terms: work item, workflow, board, sprint, WIP, JQL.
Interview prompts: When would you choose Kanban over Scrum? How do you write good acceptance criteria?
Go deeper: Jira Cloud REST API · What is a sprint · Use active sprints · Configure boards
Next: Track 4 — marketing and measurement (Lesson 31).