Jira Scrum

Question 1

Backlog:

Answer 1

A list of outstanding user stories, bugs, and features for a product or sprint. It represents the work that needs to be done[2].

Question 2

Board

Answer 2

A visualization tool used by teams to track and manage work items as they move through the workflow. It can be adapted for different agile development styles, such as Scrum or Kanban[2].

Question 3

Burndown Chart

Answer 3

A chart that visualizes the actual and estimated amount of work remaining in a sprint or project. It helps track progress and identify if the team is on track to complete the work within the desired time frame[2].

Question 4

Epic

Answer 4

A large body of work that needs to be broken down into smaller stories. Epics may span multiple sprints and are used to organize and track progress on major deliverables[2].

Question 5

Sprint

Answer 5

A fixed period of time, typically two weeks, during which a team completes work on a set of issues. Sprints are planned in advance and represent a time-bound iteration in the agile development process[3].

Question 6

Scrum

Answer 6

An agile methodology where work is completed in iterations called sprints. It involves key events like sprint planning, daily stand-ups, sprints, and retrospectives[3].

Question 7

Kanban

Answer 7

An agile methodology that emphasizes continuous flow and visualizes work on a Kanban board. It helps teams manage work in progress and optimize workflow[3].

Question 8

Issue

Answer 8

In Jira, an issue represents a unit of work or task that needs to be tracked and managed. It can refer to a bug, feature request, improvement, or any other work item within a project. Issues have various attributes such as status, priority, assignee, and description, which help in organizing and tracking the progress of work[1].

Question 9

Workflow

Answer 9

A workflow in Jira represents the lifecycle or process through which an issue progresses from creation to completion. It consists of a set of statuses and transitions that define the possible states an issue can be in and how it can move between those states. Workflows help teams visualize and manage the progression of work, ensuring that issues follow the desired process[1].

Question 10

Project

Answer 10

In Jira, a project is a container that encompasses a group of related issues and provides a space for managing and organizing them. Projects can represent different teams, departments, or initiatives within an organization. They define the scope and context for the work being done in Jira and can have their own settings, permissions, and configurations specific to the project’s requirements[4].

Question 11

Components

Answer 11

Components in Jira are used to group issues based on their functionality, features, departments, or any other relevant criteria. They act as generic containers for issues within a project and provide a way to structure and categorize work items. Components can be helpful for generating reports, collecting statistics, and organizing issues for further breakdown and analysis[3][5].

Question 12

Workflow

Answer 12

A workflow in Jira defines the series of states and transitions that an issue can go through. It determines the order in which actions can be performed on an issue and the conditions that must be met for each transition to occur. For example, a typical workflow might include states like “To Do,” “In Progress,” “In Review,” and “Done,” with corresponding transitions between them.

Question 13

Condition

Answer 13

Conditions in Jira determine whether a transition can be executed by a user. They are used to check certain requirements before allowing a transition to occur. For instance, a condition can be set to allow only users with a specific permission or role to execute a transition. Conditions help enforce business rules and ensure that only authorized users can perform certain actions.

Question 14

Post Function

Answer 14

Post functions are actions that are executed automatically after a transition occurs. They are used to perform additional processing or tasks once a transition is performed. Post functions can include actions like sending notifications, updating fields, assigning issues, or creating sub-tasks. For example, after an issue is transitioned to the “Done” status, a post function can be used to assign it to a specific user for verification.

Question 15

Trigger

Answer 15

Triggers in Jira allow you to automatically transition issues based on events that occur in connected development tools, such as Bitbucket or GitHub. Triggers are configured in the workflow and are used to keep Jira issues synchronized with the information in these development tools. For example, a trigger can be set to automatically transition an issue from “To Do” to “In Progress” when a branch is created in Bitbucket.

Question 16

Screen

Answer 16

A screen in Jira represents the user interface elements and fields that are displayed when performing a particular action or transition. Screens are used to capture and display information relevant to the action being performed. For example, when transitioning an issue to the “In Progress” status, a screen may be displayed to allow the user to input additional details or make necessary updates.

Question 17

Properties

Answer 17

Workflow properties in Jira are key-value pairs that can be used to further customize transitions and define specific behavior. They allow you to add restrictions on workflow statuses and transitions. For example, you can use properties to make an issue uneditable when it’s in a particular status or to enforce additional restrictions beyond the permission scheme.

Question 18

Board

Answer 18

A board in Jira provides a visual representation of the issues in a project or a specific workflow. Boards can be customized to display different sets of issues, filter based on criteria, and visualize the progress of work. Boards can be used to track the status of issues, prioritize work, and collaborate with team members.

Question 19

Scenario

Answer 19

Let’s say you have a software development project in Jira, and you want to configure a workflow to streamline your development process. Here’s how you can use the items mentioned:

Question 20

Workflow

Answer 20

Create a workflow that represents the stages of your software development lifecycle, such as “To Do,” “In Progress,” “In Review,” and “Done.” Define the transitions between these states, allowing issues to move from one stage to another.

Question 21

Condition

Answer 21

Set a condition on a transition to allow only users with the “Developer” role to execute it. This ensures that only authorized developers can progress the issue to the next stage.

Question 22

Post Function

Answer 22

Configure a post function to assign the issue to the QA team automatically when it moves from “In Progress” to “In Review.” This ensures that the QA team is notified and can start their testing process.

Question 23

Trigger

Answer 23

Set up a trigger to automatically transition an issue from “To Do” to “In Progress” when a new branch is created in your linked Bitbucket repository. This automates the process of moving issues into active development when code branches are created.

Question 24

Screen

Answer 24

Customize the screen displayed when transitioning an issue to “In Progress” to include fields for developers to enter details about their work, such as code branch name, estimated time, and any additional notes.

Question 25

Properties

Answer 25

Use workflow properties to make issues uneditable when they reach the “Done” status. This prevents accidental changes to completed work and ensures data integrity.

Question 26

Board

Answer 26

Create a board that displays all the issues in your project, filtered by status and assigned team members. This board provides a visual overview of the project’s progress, allowing team members to track their work and collaborate effectively.