Atlassian ACP-610 Practice Test - Questions Answers, Page 4

One difference between Scrum and Kanban boards is that only Scrum boards support selecting an estimation method. Estimation is a way of measuring how much work is required to complete an issue or a sprint. Scrum boards allow you to choose between story points, original time estimate, or issue count as estimation methods. Kanban boards do not have estimation methods, as they focus on managing the flow of work rather than planning sprints.Reference:Configuring estimation and tracking, Estimating an issue

The issue will appear in theExpediteswimlane, because it matches the querypriority = Blocker. Swimlanes are used to group issues on the board based on a common attribute, such as assignee, epic, or a custom query. The board's swimlane configuration shows that the first swimlane is Expedite, which has the querypriority = Blocker. This means that any issue with a blocker priority will be placed in this swimlane, regardless of its other attributes. The other swimlanes have different queries that do not match the issue's attributes, such as type, labels, or reporter. Therefore, the issue will not appear in those swimlanes. The last swimlane is Everything Else, which is the default swimlane for any issue that does not match any of the previous queries. However, since the issue matches the Expedite query, it will not fall into this swimlane either. Hence, the correct answer is B.Reference:[Configuring swimlanes], [Using swimlanes]

The reason why you are unable to drag an issue into a future sprint in the backlog is that ranking is disabled. Ranking is a feature that allows you to order issues based on their relative priority or importance. Ranking is enabled by adding ''ORDER BY Rank ASC'' or ''ORDER BY Rank DESC'' to your board filter query. Ranking is required for Scrum boards, as it determines the order of issues in your backlog and sprints. If ranking is disabled, you cannot drag and drop issues in your backlog or plan future sprints.Reference: Ranking an issue,Configuring filters

Swimlanes are a way of grouping issues on a board based on certain criteria, such as assignee, priority, query, or epics. If you want to see a grouping of stories without epics, you can use a query swimlane with the conditionepic is EMPTY, which will show only issues that are not part of any epic. The other options will either show epics or not group stories at all. Therefore, the correct answer is A.Reference: [Configuring swimlanes], [Advanced searching - fields reference]

The Version Report and the Sprint Health Gadget are two gadgets that can show the information that the product owner needs. The Version Report shows the progress of a version by comparing the estimated amount of work to the completed work. The report also shows a projected release date based on the team's average velocity. The product owner can use this report to monitor the overall progress of the next release and determine if it will ship on time. The Sprint Health Gadget shows a snapshot of key sprint information such as time elapsed, percentage of scope change, sprint goal, and team members' availability. The product owner can use this gadget to see how each scrum team is performing in their current sprint and identify any issues or risks.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, Version Report, Sprint Health Gadget

The Cumulative Flow Diagram is the report that provides the information that the head of customer service wants. The Cumulative Flow Diagram is a tool that visualizes the quantity and distribution of work items along different stages of a process. The report shows how many work items are in each stage at any given time, and how they flow from one stage to another. The report can help identify potential bottlenecks in the support workflow by showing where work items accumulate or stagnate over time. For example, if the report shows a sudden increase or a wide band of work items in the ''Waiting for Customer'' stage, it may indicate that the customers are not responding quickly enough or that the support team is not following up effectively. The report can also help monitor the overall progress and performance of the support teams by showing the total number of work items created, resolved, and remaining over time.Reference:Managing Jira Projects Data Center and Server: Certification Bundle,Cumulative Flow Diagram

The gadget that meets Kim's need is theIssue Statisticsgadget. This gadget displays the collection of issues returned from a filter, broken down by a field. Kim can configure the gadget to use her project as the filter, and the issue type as the field. The gadget will then show the following information for issues in her project:

the total count of all issues

the total count of each issue type

the distribution of each issue type as a percentage

a graphical chart display of that percentage

The other gadgets are not suitable because:

TheHeat Mapgadget displays issues from a project or filter, grouped by a statistic type, in a heat map format. Issues can be grouped by any statistic type (e.g. Status, Priority, Assignee, etc). However, this gadget does not show the total count of all issues, nor the distribution of each issue type as a percentage.

TheTwo Dimensional Filter Statisticsgadget displays issues from a filter in a table format, where each cell shows the number of issues for a given combination of two statistics types (e.g. Status vs Priority, Assignee vs Issue Type, etc). This gadget does not show the total count of all issues, nor a graphical chart display of that percentage.

TheFilter Resultsgadget displays the results of an issue filter on the dashboard. This gadget does not show any summary or breakdown of the issues by any field, nor a graphical chart display of that percentage.

TheIssues in Progressgadget displays all issues that are in progress and assigned to the user viewing the dashboard. This gadget does not show any information about other issues or issue types in the project, nor a graphical chart display of that percentage.