Skip to content
Tutorials Center
My learning

Topics

Lesson 27 of 29 ยท Practice and Interview

Practice Exercises with Solutions

Practice Agile, Scrum and Jira with exercises on user stories, estimation, JQL, workflows and WIP limits, each with a worked and runnable solution.

You learn a framework by using it, and these exercises give you five small, realistic jobs: fix weak user stories, run a planning poker round, write JQL for typical questions, audit a workflow log and read a Kanban board for problems. Each exercise states the task first. Try it on paper or in your head before you open the solution.

Each solution is a runnable JavaScript stand-in so that you can change the data and see the result. The code is a model of the thinking, not Jira itself: Jira's own queries, boards and workflows are screens in a real Jira site that this page cannot run, so JQL answers are shown as read-only text and checked against a tiny JavaScript data set. If you need to refresh a topic first, the matching lessons are User Stories and Acceptance Criteria, Estimating with Story Points, JQL and Filters, Issues, Issue Types and Workflows and Kanban and WIP Limits.

Five exercise sets

Stories Rewrite weak stories and add criteria.
Estimation Run planning poker rounds.
JQL Turn questions into queries.

Try each task first, then compare with the solution.

1 / 2

Exercise 1: Fix the stories

Task. Below are three stories from a backlog. Decide which are good and why. Then rewrite the technical task "Build the database table for orders" as a user story with three Given/When/Then acceptance criteria.

  1. Add search
  2. As a user, I want the system to use a MySQL database so that data is stored.
  3. As a shopper, I want to filter products by price so that I can stay within my budget.

Hints. A good story names a specific person, a need (not a technology) and a benefit. Acceptance criteria describe observable behavior, including the empty and the not-allowed case.

Solution. Story 1 is just a title: there is no person, no benefit, nothing to test. Story 2 uses the generic "user" and describes a solution (MySQL) instead of a need; the benefit "data is stored" is not a reason a person cares about. Story 3 is good. The rewrite below turns a technical task into something a person can use, and its criteria cover the normal case, the empty case and the signed-out case. The checker is a stand-in for the INVEST discussion in the user stories lesson: it can only catch mechanical problems, never decide whether a story is truly valuable.

JS Story checker and rewrite

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

No output.

The database table does not disappear: the team still builds it, as a task inside the story. The story stays about what the shopper gets.

Exercise 2: Planning poker

Task. Four developers vote on four stories using the scale 1, 2, 3, 5, 8, 13, 21. Decide for each round whether the team can settle or must talk. Then check whether the stories 5, 8, 3 and 13 fit a forecast of 24 points.

Story Votes
Password reset email 3, 5, 5, 3
Export to PDF 2, 8, 3, 5
Dark mode 2, 2, 2, 2
Migrate payment provider 13, 21, 8, 13

Hints. Votes on neighboring scale values are a small disagreement. A wide gap means people understand the story differently, and the reason behind the highest and lowest votes is the valuable output.

Solution. The function below accepts a round when the lowest and highest votes are at most one step apart on the scale and takes the higher of the two (a common, cautious choice). Otherwise it tells the team to hear the extremes first.

JS Planning poker rounds

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

No output.

"Migrate payment provider" shows a second lesson: a 13 and a 21 on one story is a hint that it is probably too big. Splitting it (for example, "accept one test payment through the new provider" first) gives smaller, more predictable pieces. The stories picked in the last check add up to 29, which is more than 24, so the team should drop the 13-point story or split it.

Exercise 3: Write the JQL

Task. Using the fields type, status, priority, assignee, labels and sprint, write one JQL query for each question. Assume you are the user mia.

  1. Which bugs are not done yet?
  2. What is my unfinished work?
  3. Which issues in the open sprint have nobody assigned?
  4. Which login-related issues have priority High or above?
  5. Which issues are in the backlog (no sprint), newest key first?

Hints. currentUser() means you. IS EMPTY finds fields without a value. statusCategory != Done also catches custom statuses that count as finished. ORDER BY always comes last.

Solution. The real JQL is read-only text below; the JavaScript data set only checks that the intent of each query selects the issues you would expect.

TEXT
type = Bug AND status != Done
assignee = currentUser() AND statusCategory != Done
assignee IS EMPTY AND sprint in openSprints()
labels = login AND priority >= High
sprint IS EMPTY ORDER BY key DESC
JS Check the JQL intent

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

No output.

In this tiny data set, "Sprint 7" plays the role of the open sprint. A common slip is status != Done for question 2: it works only if "Done" is the one finished status. Using statusCategory is safer when a workflow also has statuses like "Won't Do" or "Released".

Exercise 4: Audit a workflow log

Task. The workflow allows these moves: To Do to In Progress; In Progress to In Review or back to To Do; In Review to Done or back to In Progress; Done to To Do (reopen). Find the first illegal move in logs A and B. Then add a "Blocked" status that can be entered from In Progress and only left back to In Progress, and check logs C and D.

Hints. Replay each log from the first event and keep the current status per issue. A new issue starts in To Do.

Solution. The audit function stores the current status of each issue and checks every event against the allowed moves. Adding "Blocked" is purely a data change.

JS Workflow audit

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

No output.

Log B fails on day 2: APP-2 skipped review. Log D fails because an issue cannot be blocked before it has started. In Jira you would build the same rules as transitions in the workflow editor, see Workflows, Permissions and Customization. Many teams prefer a flag ("impediment") over a Blocked status, because a status hides which stage the blocked work is in.

Exercise 5: Read the board

Task. A board has four columns. In Progress has a WIP limit of 3 and In Review has a limit of 2. Count the cards, mark each column as "room", "full" or "over", and name the column that is probably the bottleneck. Then decide what the team should do tomorrow morning.

Hints. A bottleneck is usually a column that is over its limit and also holds the oldest cards. Work flows slowly because the column downstream of the bottleneck is empty and the column upstream is stuck.

Solution. In Review holds 5 cards against a limit of 2, and its cards are the oldest on the board. In Progress is exactly full. The sensible action is to stop starting new work and clear the reviews first: everyone reviews before anyone starts something new.

JS Board check

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

No output.

The scoring formula is made up for this exercise (it weights the excess over the limit ten times more than the age). A real team would look at the board together and ask why the cards are stuck, not trust a formula.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which part of 'As a user, I want the system to use a MySQL database so that data is stored' is the biggest weakness?

    A story should describe what a specific person wants and why. Choosing MySQL is a solution detail that the team decides while building.
  2. 2. Votes of 2 and 8 appear in a planning poker round. What should the team do?

    A wide gap means different understandings of the work. Discussing the reasons is more valuable than picking a number.
  3. 3. Why is statusCategory != Done often safer than status != Done in JQL?

    Status categories group statuses into To Do, In Progress and Done, so custom finished statuses are included.
  4. 4. A column is far over its WIP limit and holds the oldest cards. What is the best next step?

    A Kanban limit exists to expose a bottleneck. The response is to swarm on finishing, not to hide the symptom by raising the limit.

Summary

  • Good stories name a specific person, a need and a benefit; technical tasks live inside stories as sub-work.
  • Planning poker is valuable because of the conversation about differing votes, not the number it ends with.
  • JQL answers should match your intent exactly: currentUser(), IS EMPTY, statusCategory and ORDER BY solve most everyday questions.
  • A workflow is a table of allowed moves, so auditing a log or adding a status is a data change.
  • On a Kanban board, a column over its limit with the oldest cards is the bottleneck; finish work before starting more.

Next, prepare for conversations with Agile, Scrum and Jira Interview Questions.