In JIRA, a sub-task is often used to break down a larger issue into smaller _______.

  • components
  • stories
  • sub-tasks
  • tasks
In JIRA, a sub-task is used to break down a larger issue into smaller, more manageable tasks. Sub-tasks are essentially smaller units of work that contribute to the completion of the parent issue.

The y-axis of a Burndown Chart usually represents _______.

  • Time
  • Story Points
  • Tasks
  • Effort Remaining
The correct option is Effort Remaining. In a Burndown Chart, the y-axis typically represents the amount of effort remaining to complete the work. This could be measured in various units such as story points, hours, or tasks. It provides a visual indication of the progress made towards completing the sprint backlog.

Scenario: In your JIRA project, you have a parent issue representing a feature, and you want to track the development tasks required to complete that feature. What type of issues would you create to represent these development tasks, and how would you link them to the parent issue?

  • Sub-tasks
  • Epics
  • Stories
  • Tasks
Option 1: "Sub-tasks" is the correct option. When you have a parent issue representing a feature in JIRA and need to track the development tasks required to complete that feature, you create sub-tasks. Sub-tasks break down the parent issue into smaller, manageable tasks, each representing a specific aspect of the feature development. These sub-tasks are then linked to the parent issue, allowing for hierarchical organization and clear visibility into the progress of individual tasks contributing to the completion of the feature.

In Agile Scrum, what is the purpose of the Sprint Review meeting?

  • To discuss technical issues within the team.
  • To estimate the effort for upcoming tasks.
  • To plan the next sprint backlog.
  • To review and demonstrate completed work to stakeholders.
The Sprint Review meeting in Agile Scrum serves the purpose of showcasing the completed work to stakeholders for feedback and validation. It allows stakeholders to provide input, which can influence future product increments. This transparency promotes collaboration and ensures alignment with stakeholders' expectations.

You are tasked with changing the status of an issue from "In Progress" to "Resolved." What steps would you take to perform this action?

  • Edit the issue and manually change the status field to "Resolved"
  • Move the issue to the "Resolved" column on the Agile board
  • Select the issue, then click on the "Resolve" button
  • Use a transition workflow to move the issue from "In Progress" to "Resolved"
Transition workflows in JIRA define the steps an issue moves through during its lifecycle. To change the status of an issue, you need to follow the appropriate transition, which in this case, is moving it from "In Progress" to "Resolved."

In your organization, there is a need to restrict access to certain project-related information in JIRA. Which JIRA feature or configuration would you use to implement this security measure?

  • Global Permissions
  • Issue Security Scheme
  • Project Permissions
  • Workflow Permissions
Issue Security Scheme allows restricting access to specific issues within a project. By configuring Issue Security Scheme, you can control who can view and edit certain issues based on their security level. This ensures that sensitive information is only accessible to authorized individuals.

Customizing a workflow often involves defining _______ to enforce business rules.

  • Schemas
  • Transitions
  • Validators
  • Workflows
Customizing a workflow in JIRA often involves defining validators to enforce business rules. Validators are used to ensure that certain conditions are met before an issue can transition from one status to another within the workflow.

You have a software development project in JIRA, and you want to automatically assign incoming bug reports to the team lead responsible for that component. Which component of JIRA Automation Rules would you use to achieve this?

  • Automation rule triggered by Issue Assigned
  • Automation rule triggered by Issue Created
  • Automation rule triggered by Issue Transition
  • Automation rule triggered by Issue Updated
In JIRA, to automatically assign incoming bug reports to the team lead responsible for the component, you would configure an automation rule triggered by Issue Assigned. This rule would ensure that whenever an issue is assigned, it triggers the automation to assign it to the respective team lead.

When creating issue names, it is advisable to use _______ case for better readability.

  • UPPERCASE
  • camelCase
  • lowercase
  • snake_case
Using camelCase for issue names makes them more readable by capitalizing each word except the first, enhancing readability and consistency in naming conventions.

What role does consistency in naming conventions play in JIRA projects?

  • Impedes communication
  • Increases project complexity
  • Reduces user engagement
  • Simplifies searching
Consistency in naming conventions simplifies searching within JIRA projects. When issue names follow a standardized format, users can easily locate specific tasks, documents, or discussions related to their work. This fosters efficiency and collaboration among team members, ultimately improving project outcomes.