Pass the ATLASSIAN Jira Project Administrator ACP-610 Questions and answers with ExamsMirror

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

A Control Chart is the best report to provide the information that Darren wants. A Control Chart shows the cycle time or lead time for your team’s issues, broken down by the time spent in each status. It helps you identify whether data from the current process can be used to determine future performance. Less time in the Waiting for Support status indicates optimal team performance, as it means that the issues are being addressed promptly and efficiently. A Control Chart also provides a way to dynamically analyze not only specific days but also specific time frames, by using the date range selector and the zoom feature. You can also filter the chart by issue type, assignee, label, or any other field. References: Managing Jira Projects Data Center and Server: Certification Bundle, [Control Chart | Jira Software Cloud]

Thecomponent configuration of the project shows that each component has a different default assignee. The default assignee is the user who will be automatically assigned to an issue when that component is selected.

The image shows that the default assignee for the Signoff component is Project admin. Therefore, if Dave creates an issue and selects Signoff as the component, the issue will be assigned to Project admin.

The other options are not correct because:

If UX is selected, the issue will not be assigned to admin, but to Unassigned. The image shows that the default assignee for the UX component is Unassigned, which means that no user will be automatically assigned to an issue with that component.

If Login and Signoff are selected, the issue will not be assigned to Project admin, but to Project lead. The image shows that the default assignee for multiple components is Project lead, which means that if more than one component is selected, the issue will be assigned to Project lead.

If Test is selected, the issue will not be assigned to Project lead, but to Unassigned. The image shows that the default assignee for the Test component is Unassigned, which means that no user will be automatically assigned to an issue with that component.

The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how toconfigure fields in Jira, see Configuring fields and screens. References: Configuring fields and screens

The two actions that are reflected as scope change are dragging an estimated story from the backlog to the sprint and modifying the estimate value on a committed story. Scope change is a measure of how much work was added or removed from a sprint after it started. It is calculated by comparing the total story points committed at the start of the sprint and the total story points completed at the end of the sprint. If you add or remove issues from a sprint, or change their estimates, you are changing the scope of the sprint. The other actions mentioned in the question do not affect the scope of the sprint, as they do not change the amount of work planned or done in the sprint. References: Viewing the Velocity Chart, Scope change

The team can use the Release link to remove issues as needed from the Done column. This will create a version in the project that contains all the issues that were removed, and the team can use the version report to see the details of each clean-up. Excluding issues in Done status from the board filter or via a sub-filter will not remove them from the Done column, but only hide them from view. Excluding issues where Resolution != EMPTY from the board filter will also hide issues from other columns that have a resolution set, which is not desired. References: [Releasing a version], [Managing Jira Projects Data Center and Server: Certification Bundle]

The board filter query that meets these requirements is (project = BERT AND type not in subTasklssueTypesO) OR (project = ERNIE AND issuetype Epic). This query will show all issue types from project BERT except sub-tasks, as well as only epics from project ERNIE. It will not show issues from any other projects, as it uses the OR operator to combine two conditions that specify the project names. The other queries do not meet all the requirements, as they either include sub-tasks from project BERT, exclude epics from project ERNIE, or show issues from other projects. References: Configuring filters, Advanced searching - fields reference