Most Recent Atlassian ACP-610 Exam Dumps

The solution that will meet the team's requirements of using agile boards with minimal disruption to their current configuration is to use a Kanban board for tasks and a Scrum board for features in the current project. This way, they can use different agile methodologies for different issue types without creating a new project or changing their existing configuration. They can use a Kanban board for tasks to handle them based on priority and rank and release them incrementally as needed. They can use a Scrum board for features to develop them during three week iterations with sprints and backlogs. The other solutions are either not feasible or not optimal for their needs. Therefore, the correct answer is E.Reference: [Creating a board], [Using a Scrum board], [Using a Kanban board]

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 Cumulative Flow Diagram is the report that provides the needed insight to see if frequent scope change mid-sprint is causing bottlenecks. The Cumulative Flow Diagram shows the quantity and distribution of work items along different stages of a process over time. The report can help identify potential bottlenecks in the 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 ''In Progress'' stage, it may indicate that the team is overloaded with work or facing some blockers. If the team often accepts new requests from outside groups during an active sprint, the report can show how this affects the flow of work and the completion of the sprint goal.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.