ACP-620 Day 2: Board Configuration Quiz

Questions

Medium level

 

  1. (Novice) A team is adopting Agile methodologies and requires a JIRA board to visualize their workflow, which includes to-do, in-progress, and done statuses. How should the board be configured for a basic workflow?
    A) Use the default Scrum board template and map statuses to the corresponding columns.
    B) Create a new Kanban board and manually create new columns to represent the statuses.
    C) Configure a classic project and allow JIRA to auto-create a board.
    D) Set up a business project board and customize the workflow to match the Agile statuses.

  2. (Novice) To support a team's transition to Kanban, what is the first step to customizing a board that accurately reflects their workflow?
    A) Configure the board's columns to match the statuses in their workflow.
    B) Establish WIP limits for each column on the board.
    C) Implement swimlanes based on assignees.
    D) Enable a backlog for the Kanban board.

  3. (Competent) Your team needs to manage multiple product backlogs on a single board. Which strategy should you recommend?
    A) Configure a filter query to include multiple projects and map the columns to the teams' combined workflows.
    B) Advise against using a single board for multiple backlogs due to potential confusion.
    C) Set up individual boards for each product and link them through a dashboard.
    D) Create a Scrum board with a single backlog and use components to differentiate between products.

  4. (Competent) In a company using a customized workflow with the status 'Awaiting Review,' which column should this status be mapped to on a Scrum board?
    A) The 'In Progress' column to signify that it's still part of the ongoing sprint.
    B) A new column named 'Awaiting Review' to reflect the exact status.
    C) The 'Done' column, assuming that 'Awaiting Review' means work has completed.
    D) The 'To Do' column, because the review is the next action to be taken.

  5. (Proficient) If a team's process includes a 'Blocked' status, how could you visually highlight these issues on the board?
    A) Configure card colors to change when issues are moved to the 'Blocked' status.
    B) Use a specific label for blocked issues and a quick filter to show/hide them.
    C) Create a separate swimlane for 'Blocked' issues.
    D) Set up an automation rule to email the team whenever an issue is blocked.

  6. (Proficient) Your organization wants to manage feature development and bug fixes on the same JIRA board but prioritize feature work. What configuration should be made?
    A) Use quick filters to separate features from bugs.
    B) Set up swimlanes that prioritize features over bugs.
    C) Create separate boards for features and bugs.
    D) Customize the workflow to automatically transition bugs to a lower priority.

Advanced level

 

  1. (Advanced) A team uses a complex workflow with custom statuses. How can you configure the board to simplify the transition between these statuses?
    A) Configure the board columns to combine less frequently used statuses.
    B) Educate the team on how to use the 'Transition Issues' permission.
    C) Create a custom automation for each status transition.
    D) Adjust the workflow scheme to automatically transition between statuses.

  2. (Advanced) For a team that needs to manage cross-functional tasks that affect multiple components within a project, how should the JIRA board be configured for optimal visibility?
    A) Set up a board filter that includes all components and use card layout to display them.
    B) Use a component-based swimlane configuration.
    C) Create a multi-board setup with one board per component.
    D) Implement a tagging system for cross-functional tasks and use quick filters.

  3. (Expert) When managing releases in a JIRA Scrum board, which configuration helps the team understand what is scheduled for the current release?
    A) Configure a quick filter to show only issues assigned to the current release version.
    B) Set up a release burndown chart on the dashboard.
    C) Use version swimlanes to separate issues by the target release.
    D) Label each card with the version number and sort the backlog accordingly.

  4. (Expert) How can a JIRA administrator customize a board to show issues that require immediate attention due to impending deadlines?
    A) Set a quick filter to highlight issues with due dates within the next 7 days.
    B) Customize card colors based on due date proximity.
    C) Implement swimlanes sorted by due date.
    D) Create an 'Expedite' column for all issues with due dates within a week.

  5. (Seasoned) Your team wants to adopt Extreme Programming (XP) practices. How should you configure the board to accommodate pair programming and continuous releases?
    A) Implement a column for 'Pair Programming' and 'Ready for Release' to reflect XP stages.
    B) Use labels for pair programming pairs and configure a board filter.
    C) Customize the board to show subtasks for pair assignments and configure swimlanes for iterations.
    D) Set up a new workflow for continuous delivery and map it to the board.

  6. (Seasoned) To ensure an efficient problem-solving process for critical bugs, what configuration might you apply to a JIRA board to facilitate a 'Swarm' approach, where multiple team members collaborate on a solution?
    A) Create a 'Swarming' swimlane and set rules to move critical bugs into this lane.
    B) Use a label such as 'swarm-needed' and a quick filter to make these issues stand out.
    C) Establish a dedicated 'Swarming' column for critical bugs requiring immediate attention.
    D) Configure an automation to assign all critical bugs to a 'Swarm' sprint automatically.

 

Solutions

 

Question

Answer

Reason

Question

Answer

Reason

1

A

The default Scrum board template is designed to work with Scrum methodologies out of the box, making it easy to map statuses to columns for someone with basic experience.

2

A

Board columns should directly reflect the statuses defined in the team's workflow, ensuring transparency and ease of tracking.

3

A

A filter query including multiple projects will allow the board to pull in issues from across those projects, fitting the requirement for a board spanning multiple teams.

4

B

The addition of a new column named 'Awaiting Review' creates a clear and direct mapping to the corresponding workflow status.

5

A

Configuring card colors based on status changes allows for quick visual cues, which is essential for identifying blocked issues.

6

B

Swimlanes that prioritize features ensure that the team focuses on delivering new value while managing bugs as a secondary activity.

7

A

Combining less frequently used statuses into single columns can streamline the board and make it more manageable.

8

B

Component-based swimlanes allow for logical grouping of issues, which is beneficial for teams dealing with multiple components.

9

A

Quick filters provide an efficient way to display only the issues relevant to the current release version without affecting the board's overall layout.

10

B

Customizing card colors based on due date proximity enables teams to visually prioritize work that is nearing its deadline.

11

C

Configuring the board to show subtasks for pair assignments along with iterations in swimlanes aligns with the XP practice of continuous collaboration and iteration.

12

A

Creating a dedicated swimlane for 'Swarming' ensures critical bugs are prominently displayed and addressed collaboratively, fostering an immediate and focused response.

 

 

 

Â