Jira Jira Boards and Sprints

Question 1

What is the primary purpose of a Sprint in Jira Scrum boards?

Accepted Answer

To define a time-boxed iteration for completing a set of backlog items

Answer

To archive completed issues

Answer

To assign issues to team members

Answer

To create new projects

Question 2

Which board type in Jira is best suited for teams with a continuous flow of work without fixed iterations?

Accepted Answer

Kanban board

Answer

Scrum board

Answer

Roadmap board

Answer

Backlog board

Question 3

What happens to incomplete issues when a Sprint is closed in Jira?

Accepted Answer

They are moved to the backlog or the next sprint

Answer

They are deleted automatically

Answer

They remain in the closed sprint

Answer

They are marked as Won't Do

Question 4

In Jira, what is the Backlog in the context of a Scrum project?

Accepted Answer

A prioritized list of issues not yet in a sprint

Answer

A list of completed issues

Answer

A board showing all active sprints

Answer

A report of sprint velocity

Question 5

What does the Swimlane feature on a Jira board do?

Accepted Answer

Groups issues horizontally by a criteria such as assignee or epic

Answer

Defines sprint capacity

Answer

Filters issues by priority

Answer

Sets up automated rules

Question 6

Which Jira feature allows you to set the maximum number of issues allowed in a column on a Kanban board?

Accepted Answer

Column constraint (WIP limit)

Answer

Sprint goal

Answer

Issue quota

Answer

Board filter