Skip to content
Tutorials Center
My learning

Topics

Lesson 29 of 29 ยท Practice and Interview

Agile, Scrum and Jira Cheat Sheet

A one-page Agile, Scrum and Jira cheat sheet: events and time-boxes, roles, artifacts, story template, JQL patterns and workflow vocabulary.

This is a reference page, not a lesson. It collects the facts you look up most often while working with Scrum and Jira: the events and their time-boxes, the roles, the artifacts, the story template, handy JQL patterns and the vocabulary of workflows. Everything here is explained in the earlier lessons; follow the links when a line is not enough.

The Scrum facts follow the 2020 Scrum Guide. The Jira snippets are real syntax shown read-only, because Jira cannot run on this site. The two TryIts are small stand-ins: a time-box calculator and a JQL sanity checker. They are not Jira.

Scrum at a glance

Scrum in one screen

One Scrum Team Product Owner, Scrum Master, Developers.
Sprints One month or less, back to back.
Three artifacts Product Backlog, Sprint Backlog, Increment.

Transparency, inspection and adaptation.

1 / 2

Events and time-boxes

Maximums for a one-month Sprint. Shorter Sprints usually get shorter events. A time-box is a limit, not a target.

Event Purpose Maximum length
Sprint Container for all other events; produces an Increment 1 month or less
Sprint Planning Decide why the Sprint is valuable, what can be done, how it will be done 8 hours
Daily Scrum Inspect progress toward the Sprint Goal and adapt the plan 15 minutes
Sprint Review Inspect the outcome with stakeholders and adapt the Product Backlog 4 hours
Sprint Retrospective Inspect how the team worked and plan improvements 3 hours

Details: Scrum Events.

Roles

Accountability Owns Not
Product Owner Product Goal, ordering the Product Backlog, maximizing value A committee, or a note-taker for stakeholders
Scrum Master Effective use of Scrum, removing impediments, coaching A project manager who assigns tasks
Developers The Sprint Backlog, quality, the Definition of Done, the Increment Split into sub-teams by specialty inside Scrum

Stakeholders are not part of the Scrum Team but join the Sprint Review. Details: Scrum Roles.

Artifacts and commitments

Artifact Commitment Notes
Product Backlog Product Goal Ordered list of what the product needs; never complete
Sprint Backlog Sprint Goal Sprint Goal + selected items + plan to deliver them
Increment Definition of Done A usable step toward the Product Goal; several can be made in one Sprint

Details: Scrum Artifacts and Commitments.

Story template

TEXT
As a <type of user>,
I want <a capability>,
so that <a benefit>.

Acceptance criteria
  Given <a starting situation>
  When  <something happens>
  Then  <an observable result>

Check a story against INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable. See User Stories and Acceptance Criteria.

Typical point scale for relative estimates: 1, 2, 3, 5, 8, 13, 21. Forecast with the average velocity of recent Sprints, and give a range. See Estimating with Story Points.

JQL patterns

JQL (Jira Query Language) has fields, operators, values, functions and an optional ORDER BY. These patterns are real JQL, read-only here.

TEXT
# My open work, most urgent first
assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC

# Current Sprint, not finished
sprint in openSprints() AND statusCategory != Done

# Unassigned issues in a project
project = SHOP AND assignee is EMPTY

# Bugs with high priority
issuetype = Bug AND priority in (High, Highest)

# Created recently
created >= -14d ORDER BY created DESC

# Resolved in the last week
resolved >= -7d

# Text search in the summary
summary ~ "login"

# A release
fixVersion = "1.0"

Common operators: =, !=, >, >=, <, <=, ~ (contains text), in, not in, is EMPTY, is not EMPTY. Combine with AND, OR, NOT and parentheses. ORDER BY goes last. Use double quotes around values with spaces. More in JQL and Filters.

Workflow vocabulary

Term Meaning
Status Where an issue is in its workflow (To Do, In Progress, Done)
Transition The move from one status to another
Status category The grouping of statuses into To Do, In Progress and Done, used by boards and reports
Resolution The outcome set when work is finished, such as Done or Won't Do
Issue types Epic, Story, Task, Bug, Sub-task
Backlog The ranked list of issues not yet in a Sprint
Component, label Ways to group issues; components are managed, labels are free text
Fix version The release an issue is planned or delivered in
WIP limit The maximum number of items allowed in a column at once (Kanban)
Lead time, cycle time Time from request to delivery, and time from start of work to delivery

See Issues, Issue Types and Workflows and Kanban and WIP Limits.

Stand-in 1: time-box calculator

The Scrum Guide gives maximums for a one-month Sprint and says shorter Sprints usually have shorter events. This stand-in scales those maximums in proportion to the Sprint length, a common rule of thumb. It is not a rule in the Guide, so treat the numbers as a starting point.

JS Time-boxes by Sprint length

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Stand-in 2: JQL sanity checker

Jira validates JQL for you in the search box, with full knowledge of your fields. This stand-in checks only a few typical slips (unbalanced quotes and parentheses, clauses after ORDER BY, a trailing AND, null, ==), to show the kind of mistakes to look for.

JS Spot common JQL slips

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the maximum length of the Daily Scrum?

    The Daily Scrum is time-boxed to 15 minutes, every working day of the Sprint.
  2. 2. Which artifact is paired with the Definition of Done?

    The commitments are Product Goal (Product Backlog), Sprint Goal (Sprint Backlog) and Definition of Done (Increment).
  3. 3. Where does ORDER BY go in a JQL query?

    ORDER BY sorts the results and must come after all conditions; you cannot add AND or OR after it.
  4. 4. Which JQL matches issues with no assignee?

    EMPTY with the IS operator matches fields without a value.

Summary

  • Sprint events: Sprint (1 month or less), Planning (8 h), Daily Scrum (15 min), Review (4 h), Retrospective (3 h) as maximums for a one-month Sprint.
  • Three accountabilities: Product Owner, Scrum Master, Developers.
  • Three artifacts with commitments: Product Backlog with the Product Goal, Sprint Backlog with the Sprint Goal, Increment with the Definition of Done.
  • Stories follow "As a, I want, so that", with Given-When-Then criteria, and should pass INVEST.
  • JQL is field, operator and value, combined with AND and OR, with ORDER BY last.

Rehearse the answers behind these facts in Agile, Scrum and Jira Interview Questions, or return to the start with What Is Agile?.