When should you consider breaking down a large user story into smaller ones in the backlog?

  • When the user story cannot be completed by a single team member
  • When the user story exceeds the sprint duration
  • When the user story involves multiple stakeholders with conflicting requirements
  • When the user story is too complex to estimate accurately
In Agile development, breaking down large user stories into smaller ones is essential for better estimation, implementation, and tracking. When a user story is too complex to estimate accurately, it should be broken down into smaller, more manageable pieces. This allows the team to understand and deliver value incrementally, reducing risks associated with uncertainties and facilitating collaboration among team members.

In Agile, what is the primary purpose of a product backlog?

  • To capture all the tasks required to deliver the product
  • To define the scope of the project
  • To prioritize and manage requirements
  • To track sprint progress
The primary purpose of a product backlog in Agile is to prioritize and manage requirements. It serves as a dynamic document that captures all the features, enhancements, and fixes that need to be implemented in the product. Prioritization ensures that the team works on the most valuable items first.

Why is it important to follow consistent naming conventions for JIRA issues?

  • Consistency aids in searchability and organization
  • It doesn't matter as long as issues are documented
  • It encourages creativity and diversity
  • It makes the project manager's job harder
Following consistent naming conventions for JIRA issues is crucial because it aids in searchability and organization. Consistent naming makes it easier for team members to locate specific issues quickly, fosters better communication, and enhances overall project management efficiency.

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.

Which of the following is a recommended approach for naming issues in JIRA?

  • Use cryptic titles to encourage curiosity
  • Use descriptive titles that clearly indicate the issue's content
  • Use emoji-filled titles for visual appeal
  • Use generic titles to cover a broad range of topics
In JIRA, using descriptive titles that clearly indicate the issue's content is a recommended approach. This helps users quickly understand the nature of the issue without having to delve into the details. Clear and concise titles facilitate efficient communication and collaboration within the team.

To restrict access to certain actions in JIRA, you can use _______.

  • Issue types
  • Permission schemes
  • User groups
  • Workflow schemes
In JIRA, permission schemes are used to control access to various actions and features within the system. These schemes define who can perform which actions on different aspects of JIRA projects and issues.

In JIRA, what types of actions can be performed using Bulk Operations?

  • Comment, log work, re-open, attach files
  • Create, close, assign, link, watch
  • Delete, resolve, assign, prioritize
  • Edit, transition, move, clone, delete, watch
In JIRA, Bulk Operations allow users to perform actions like editing multiple issues' fields at once, transitioning multiple issues through workflow states, moving multiple issues to another project, cloning issues, deleting multiple issues, and more.

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.