Atlassian ACP-610 Exam Questions & Answers

Correct Answer: E

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. References: Configuring estimation and tracking, Estimating an issue

Correct Answer: B

Based on the report shown, which is a Velocity Chart, the only statement that is definitely true about the team's performance is that they sometimes commit more work than they can complete in an iteration. This can be seen by comparing the green bars (completed work) and the gray bars (estimated work) in each sprint. For example, in Sprint 4, the team committed 10 story points but only completed 8 story points. The other statements are not necessarily true based on the report alone. For example, the team may be estimating their work accurately, but facing other challenges or impediments that prevent them from completing their work on time. Or, the team may not be committing unestimated work to an iteration, but rather re-estimating some issues during the sprint. Or, scope change may not be affecting the team's ability to complete work on time, but rather reflecting changes in priorities or requirements. Or, the team may be using sprint duration consistently, but varying the amount of work they commit to each sprint based on their capacity or velocity. For more information on how to interpret and use the Velocity Chart, see Velocity Chart. References: Velocity Chart

Correct Answer: AC

https://support.atlassian.com/jira-software-cloud/docs/understand-project- permissions-and-roles/ The two permissions that can be granted through a project role are:

A. see issues with a security level

C. share a dashboard with other auditors

These permissions are related to the project level and can be configured by the project administrator using the permission scheme or the dashboard settings.According to the documentation1, a project role can be granted the following

permissions:

Browse Projects: View the project and its issues.

Create Issues: Create new issues.

Edit Issues: Edit existing issues.

Schedule Issues: Edit the Due Date of an issue, or rank issues on a Scrum board. Move Issues: Move issues from one project to another, or change the issue type.

Assignable User: Be assigned issues.

Assign Issues: Assign issues to other users.

Resolve Issues: Resolve or reopen issues, or set a resolution when closing issues.

Close Issues: Close issues.

Modify Reporter: Modify the Reporter field of an issue.

Delete Issues: Delete issues from the project.

Link Issues: Link issues to each other, or create sub-tasks under an issue. Set Issue Security: Set a security level on an issue to control who can see it. View Voters and Watchers: View the list of voters and watchers for an issue. Manage

Watchers: Add or remove watchers for an issue. View Read-Only Workflow: View the workflow diagram for an issue, but not edit it. Manage Sprints: Start, complete, or edit sprints on a Scrum board. Additionally, a project role can be given

access to share a dashboard with other users or groups2. To do this, the project administrator needs to:

Go to Dashboards > View all dashboards

Find the dashboard to share and click > Share

Click Edit permissions

Under Add Permissions, select Group or Project Role Choose the auditors project role from the dropdown menu Click Add

The other options are not correct because:

B. see issues that have been archived is not a permission that can be granted through a project role.Archived issues are hidden from all users except Jira administrators3. To view archived issues, the auditors would need to have the

Administer Jira global permission, which is not related to project roles. D. subscribe other auditors to a search result is not a permission that can be granted through a project role.Subscribing other users to a search result is a feature that

requires the Manage Group Filter Subscriptions global permission4. This permission is not related to project roles and can only be granted by Jira administrators to individual users or groups.

E. use bulk change to update seven issues is not a permission that can be granted through a project role.Bulk change is an operation that requires the Bulk Change global permission5. This permission is not related to project roles and can

only be granted by Jira administrators to individual users or groups.