Download Managing Jira Projects for Data Center and Server Certification.ACP-610.VCEplus.2023-11-23.41q.tqb

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.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, [Control Chart | Jira Software Cloud]

The best way to meet the team's requirement is to use the currentUser() JQL function in the filter. This function returns the current user who is viewing the gadget, and can be used to filter issues by assignee. For example, if the filter is ''project = ABC and assignee = currentUser()'', then each person who views the gadget will see counts of only their assigned issues by status. This way, you do not need to reconfigure the dashboard viewers or modify the Assignable User permission, which are global settings that affect all users. You also do not need to replace it with the ''Assigned to Me'' gadget, which does not show counts by status. Configuring the ''Who can view this filter'' setting does not affect the results of the filter, but only its visibility.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, [Advanced searching - functions reference | Jira Software Cloud]

A Sprint Report is the best report to provide a single comprehensive list of issues that were completed in the last sprint. A Sprint Report shows the scope, status, and completion date of each sprint. It also displays a breakdown of the completed, incomplete, and added issues in the sprint. The team can see the story points associated with each completed issue, as well as the issue type of each completed issue. They can also see the description of each issue that has not been completed by clicking on the issue key or summary. A Sprint Report also helps to track the team's performance and identify any scope changes during the sprint.Reference:Managing Jira Projects Data Center and Server: Certification Bundle, [Sprint Report | Jira Software Cloud]

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 two functions that are needed to use in the JQL query to find all issues that were not completed in some past sprint, and that are now part of an active sprint are closedSprints() and openSprints(). The closedSprints() function returns all issues that are assigned to a completed sprint. The openSprints() function returns all issues that are assigned to an incomplete sprint. By combining these two functions with the NOT operator, we can filter out the issues that belong to both a completed sprint and an incomplete sprint, and only get the issues that were not completed in some past sprint, and that are now part of an active sprint. For example, the JQL query could be:project = XYZ AND issuekey NOT IN (closedSprints() AND openSprints())This query will return all issues in project XYZ that are not in both a closed sprint and an open sprint, meaning they are either in a closed sprint only or an open sprint only. Since we are looking for issues that are now part of an active sprint, we can assume they are in an open sprint only.Reference:Advanced search reference - JQL functions,Modifying closedSprints() to return previous two Sprints,JQL - Explanation of what closedSprints() does

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.Reference:Configuring filters, Advanced searching - fields reference

The solution that meets this requirement is to update the board filter and add: AND (labels != daily.business OR labels IS EMPTY). This will exclude issues that have the label daily_business from the board filter, which determines which issues are displayed on the board. It will also include issues that have no labels at all, as some issues in your project may not have labels. The other solutions do not meet this requirement, as they either do not exclude issues with daily_business label, or exclude issues with no labels.Reference:Configuring filters, Advanced searching - operators reference

The reason why your team completed more story points than they committed in their last sprint is that someone increased the story point value on an issue mid-sprint. This will increase the total story points completed at the end of the sprint, but not affect the total story points committed at the start of the sprint. Therefore, it will result in a positive scope change. The other reasons mentioned in the question do not explain why your team completed more story points than they committed, as they either do not affect story points at all, or affect both committed and completed story points equally.Reference: Viewing the Velocity Chart, Scope change