Skip to content
Tutorials Center
My learning

Topics

Lesson 28 of 29 ยท Practice and Interview

Agile, Scrum and Jira Interview Questions

Prepare for Agile, Scrum and Jira interviews with concept, scenario and tool questions, model answers, common traps and runnable drills.

Interviews for Agile, Scrum Master, Product Owner, project manager and even developer roles tend to ask the same families of questions: definitions ("what is a Sprint?"), situations ("the Product Owner keeps adding work mid-Sprint, what do you do?") and tool skills ("write a JQL query for my open bugs"). Interviewers rarely want a textbook recital. They want to hear that you understand the reasons behind the rules and that you have seen the rules bend in real teams.

This lesson gives you model answers in plain words, grouped by type, plus two runnable drills. The answers follow the 2020 Scrum Guide, which is the current version of the framework. If you need a refresher first, read Scrum at a Glance, Scrum Events and JQL and Filters.

Answer in three beats: a one-sentence definition, the reason it exists, and a short example from your own work. Even a small example from a school or hobby project beats a perfect definition with nothing behind it.

How to use this lesson

Read each question, cover the answer, and say yours out loud. Then compare. The point is not to memorize sentences; interviewers can tell. If your answer contains the same ideas in your own words, you are ready. The commands and queries below are real Jira syntax shown read-only. The TryIts later are honest stand-ins that drill the facts and the arithmetic, not Jira itself.

Three kinds of question

Concept Define it and say why it exists.
Scenario Describe what you would do and why.
Tool Show a Jira query or setup.

Name the trade-off in every answer.

1 / 2

Concept questions

What is Agile, and how is it different from Scrum? Agile is a mindset and set of values (the Manifesto) about delivering value in small steps and responding to change. Scrum is one specific framework that applies those ideas with fixed roles, events and artifacts. You can be Agile without Scrum (Kanban, XP), but Scrum is always meant to be Agile. A good follow-up point: Agile is the "why", Scrum is one possible "how".

What are the Scrum roles? The 2020 Scrum Guide describes one Scrum Team with three accountabilities: the Product Owner (maximizes the value of the product and orders the Product Backlog), the Scrum Master (helps the team and the organization use Scrum well) and the Developers (create a usable Increment every Sprint). There is no separate "tester" or "team lead" accountability. The Product Owner is one person, not a committee.

What are the Scrum events and their time-boxes? The Sprint (one month or less) contains Sprint Planning (up to 8 hours for a one-month Sprint), the Daily Scrum (15 minutes), the Sprint Review (up to 4 hours) and the Sprint Retrospective (up to 3 hours). For shorter Sprints the maximums are usually shorter. A time-box is a maximum, not a target.

What is the Definition of Done, and who owns it? It is a shared, formal description of the quality an Increment must meet before it counts as done, for example "reviewed, tested, documented and deployable". If an organization has a standard, every team follows at least that; otherwise the Scrum Team creates one. Work that does not meet it goes back to the Product Backlog and is not shown as finished. A common trap: confusing it with acceptance criteria, which belong to one story, while the Definition of Done applies to all work.

What is the difference between velocity and capacity? Capacity is how much time or effort the team has available in a Sprint (holidays and leave reduce it). Velocity is how many story points the team actually finished in past Sprints, used only as a forecasting aid. Neither measures how good the team is, and comparing velocity between teams is meaningless because each team sizes differently.

What is the difference between a story, a task and an epic? A story is a small, valuable change described from the user's point of view. A task is a technical step that is not itself valuable to a user. An epic is a large body of work that is broken down into stories over time. See User Stories and Acceptance Criteria.

Kanban or Scrum? Scrum fits work that benefits from regular planning and review rhythms, such as product development. Kanban fits a continuous stream of unpredictable requests, such as support or operations. Many teams mix them ("Scrumban"). Compare them in Scrum, Kanban, XP and Lean Compared.

Scenario questions

Scenario questions test judgment. There is rarely one correct answer; interviewers listen for whether you start with the team's goals, talk to people and protect the process without being rigid.

A stakeholder asks to add an urgent item in the middle of a Sprint. What do you do? First, understand how urgent it really is and what it is worth. The Product Owner decides, because they own the Product Backlog. If it is truly critical, the team and the Product Owner negotiate: something of similar size leaves the Sprint, or the Sprint Goal is at risk and may be cancelled in extreme cases (only the Product Owner can cancel a Sprint). If it is not critical, it goes into the Product Backlog for the next Sprint Planning. Scope can be renegotiated during a Sprint as long as the Sprint Goal is not endangered.

The team is consistently missing its Sprint forecast. What do you look at? Start with data and conversation, not blame. Look at how much work was carried over, whether stories are too large, whether unplanned work and interruptions are eating capacity, and whether the team is forecasting from real velocity or from hope. Take it to the Retrospective, pick one improvement experiment, and check next Sprint. A fix that works: smaller stories and a forecast based on the average of recent Sprints.

A developer says "I'm blocked" every day at the Daily Scrum, but nothing changes. What now? The Daily Scrum exists to inspect progress and adapt the plan, so a repeated blocker means the team is not adapting. The Scrum Master helps remove the impediment, or escalates it if it lives outside the team. Also ask why the blocker is not being solved right after the meeting. If it is a dependency on another team, make it visible on the board and agree on an owner.

The Product Owner is never available. What do you do? Explain the cost: the team builds on guesses, and feedback arrives late. Offer concrete help, such as a standing 30-minute slot, a short list of the open questions, or a delegate who is empowered to decide. If nothing changes, raise it as an impediment with the sponsor. The Scrum Master should not become the Product Owner.

Your manager wants to use velocity as a performance target. How do you respond? Explain that once a measure becomes a target, people can inflate it (bigger estimates, skipped quality) and it stops being useful. Offer outcome-based measures instead: lead time, escaped defects, customer satisfaction, and whether the Sprint Goals were met. More in Common Mistakes and Scaling Agile.

Jira questions

What is the difference between a company-managed and a team-managed project? Company-managed projects are configured by Jira administrators with shared schemes for workflows, fields and permissions, which suits large organizations that want consistency. Team-managed projects are configured by the team itself, inside the project, which suits small independent teams. Details are in Getting Started with Jira.

What is a workflow in Jira? A workflow is the set of statuses an issue can have and the transitions between them, for example To Do, In Progress, In Review, Done. Administrators can add conditions, validators and post functions to transitions. See Issues, Issue Types and Workflows.

Write JQL for: my unresolved bugs, highest priority first.

TEXT
assignee = currentUser() AND issuetype = Bug AND resolution = Unresolved ORDER BY priority DESC

Write JQL for: unassigned issues in the current Sprint.

TEXT
sprint in openSprints() AND assignee is EMPTY

Write JQL for: issues created in the last 14 days that are not done.

TEXT
created >= -14d AND statusCategory != Done

How do you see how a Sprint is going? The Sprint burndown chart and the board show the remaining work against time; the Sprint Report lists completed and not-completed issues and scope changes. Remember what they cannot show: whether the work is the right work. See Jira Reports and Dashboards.

What would you automate in Jira? Repetitive, rule-like steps: assign new bugs to the component owner, move a parent to Done when all sub-tasks are done, send a message when a high-priority issue is created. Rules follow the pattern trigger, condition, action. See Jira Automation and the REST API.

Drill 1: flashcards

This stand-in shuffles a deck with a fixed seed so the output is the same every time, and scores a set of sample answers. Edit the answers to see how the score changes.

JS Scrum flashcard drill

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

No output.

Drill 2: forecasting questions

Interviewers like a small calculation: "The backlog has 140 points and the last five Sprints delivered 21, 25, 23, 27 and 24. When will it be done?" A good answer gives a range, not a single date.

JS Answer with a range, not a date

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

No output.

The honest framing: "About 6 to 7 Sprints, so 12 to 14 weeks, assuming the scope and the team stay stable. If the scope grows, so does the forecast." That sentence shows you understand forecasts as ranges. Practice more of these in Release Forecast from Velocity.

Traps to avoid

  • Reciting rules with no reason. Always say what problem the rule solves.
  • Calling the Scrum Master a project manager. The Scrum Master serves the team and the organization; they do not assign work.
  • Treating story points as hours. Points are relative sizes; hours are a different measure.
  • Claiming one right answer to scenario questions. Say "it depends" only if you follow it with what it depends on.
  • Inventing experience. Interviewers probe. A true small example is safer.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the maximum length of Sprint Planning for a one-month Sprint?

    The Scrum Guide sets 8 hours as the maximum for a one-month Sprint; shorter Sprints usually have shorter planning.
  2. 2. A stakeholder wants an urgent change in the middle of a Sprint. Who decides what happens to the Product Backlog?

    The Product Owner owns and orders the Product Backlog, and works with the Developers on any change to the Sprint scope that keeps the Sprint Goal safe.
  3. 3. Which JQL finds unassigned issues in the current Sprint?

    openSprints() is a JQL function, and EMPTY (with the IS operator) matches fields with no value. null, none and == are not valid JQL for this.
  4. 4. How should you answer a question about when a backlog will be done?

    Velocity varies from Sprint to Sprint, so a range with stated assumptions is honest and useful.

Summary

  • Answer with a definition, the reason behind it and a short example.
  • Know the Scrum Guide basics: three accountabilities, five events with time-box maximums, three artifacts with their commitments.
  • For scenarios, start with the goal, talk to people, and protect the Sprint Goal and the Product Owner's ownership of the backlog.
  • Know the common JQL building blocks: currentUser(), openSprints(), EMPTY, ORDER BY.
  • Give forecasts as ranges and name the assumptions.

Keep the key facts on one page with the Agile, Scrum and Jira Cheat Sheet.